KDE was built when objprelink was in vogue, haven't upgraded yet. However, this behaviour seems non-related... Excerpt: [...] creating libtool loading cache ./config.cache checking for libtool... $(SHELL) $(top_builddir)/libtool checking whether NLS is requested... yes checking for msgfmt... /usr/bin/msgfmt checking for gmsgfmt... /usr/bin/msgfmt checking for xgettext... /usr/bin/xgettext checking for rpath... yes checking for KDE... configure: error: in the prefix, you've chosen, are no KDE headers installed. This will fail. So, check this please and use another prefix! !!! ERROR: The ebuild did not complete successfully. !!! Function kde_src_compile, Line -4, Exitcode 1 !!! (no error message) !!! emerge aborting on /usr/portage/dev-util/kdbg/kdbg-1.2.2.ebuild . Same result for kdbg-1.2.1. /usr/include has kde headers. $ ls /var/db/pkg/kde-base/ kde-2.2.2/ kdebase-2.2.2/ kdemultimedia-2.2.2/ kdeutils-2.2.2/ kde-env-2.2.2/ kdebindings-2.2.2/ kdenetwork-2.2.2/ kdoc-2.2.2/ kdeaddons-2.2.2/ kdegames-2.2.2/ kdepim-2.2.2/ kdeadmin-2.2.2/ kdegraphics-2.2.2/ kdesdk-2.2.2/ kdeartwork-2.2.2/ kdelibs-2.2.2/ kdetoys-2.2.2/ Rgds, Gontran
Please emerge kdelibs-2.2.2-r1 and unmerge kdelibs-2.2.2, that should help. I'm going to add this corrected dep to kde.eclass.Please tell me if that works.PS. objprelink doesn't matter - you can mix and match packages built with and without it.
Upgrading kde libs 2.2.2 to -r1 did the trick -- kdb ebuild humming along right now. Thx!
OK then, I'm closing this.
