Hi. Short story: objprelink is known to cause KHTML (used by Konqueror to render web pages) to dump core and segfault. Long story: Not only does objprelink cause problems, but the proper solution is already upstream - in glibc. glibc does actual prelinking, as of release 2.2.5, and so objprelink is not only unnecessary, but also possibly counterproductive. Please remove objprelink from the compilation process for KDE on x86.
A grep -R prelink * in /usr/portage turns up lots of references, but excluding those that are in either dev-util/objprelink and commented out of profiles/default-*, we have:<br><br> app-editors/quanta/quanta-2.0_pre2-r1.ebuild: kde-objprelink-patch<br> distfiles/kde-admin-acinclude.patch: patches to include objprelink<br><br> As far as the first one goes, a quick ebuild ... unpack shows that it calls an obsolete kde eclass function, which turns up with:<br><Br> /usr/sbin/ebuild.sh: kde-objprelink-patch: command not found<br><br> Also note that the Quanta ebuild isn't up to date. As far as the KDE Admin package goes, I'm pretty sure the patch is probably out of date and just cruft leftover on my system.<br><br> All in all, the current Gentoo portage tree is fairly clean of objprelink. See the -dev mailing list for more information; this was discussed there a while ago, and I think they moved away from objprelink. Objprelink doesn't even compile with a modern portage tree. See bug 1776.
The quanta ebuild mentioned is an old one, there's a 2.0.1 ebuild that's ok. I'll remove the old ebuild from cvs. No other kde ebuild uses or tries to use objprelink afaik. The objprelink use flag is deprecated and doesn't affect anything anymore. We certainly don't have it in kdebase (konqueror). Did you actually expirience objprelink-related problems or is it just a general warning? I'll remove the objprelink from cvs entirely, it's of no use to anyone anymore and only brings up bug reports.
