ldy-gentoo ~ # emerge --info Portage 2.0.54 (default-linux/x86/2006.0, gcc-3.4.5, glibc-2.3.5-r2, 2.6.15-gentoo-r1 i686) ================================================================= System uname: 2.6.15-gentoo-r1 i686 Intel(R) Pentium(R) M processor 2.00GHz Gentoo Base System version 1.6.14 dev-lang/python: 2.3.5-r2, 2.4.2 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.16.1 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-Os -march=pentium-m -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-Os -march=pentium-m -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="ftp://dsse.con.can.ibm.com/gentoo http://gentoo.oreganstate.edu http://gentoo.139pay.com" LINGUAS="zh_CN" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://twmlinux.raleigh.ibm.com/gentoo-portage" USE="x86 X alsa apache2 apm audiofile avi berkdb bitmap-fonts bzip2 cdr cjk crypt cscope cups curl dvd eds emboss encode esd expat fam foomaticdb fortran gdbm gif gpm gstreamer gtk2 idn imlib jpeg kde lcms libg++ libwww mad mikmod mng motif mp3 mpeg ncurses nls nptl ogg opengl oss pam pcre pdflib perl png python qt quicktime readline sdl spell ssl tcltk tcpd tiff truetype truetype-fonts type1-fonts udev vorbis xml xml2 xv xvid zlib linguas_zh_CN userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, MAKEOPTS, PORTDIR_OVERLAY When I "emerge kscope", It failed with can not find libkate. Then I emerge kate kscope, all passed and both kate and kscope have been installed.
Please provide the whole error message and reopen this bug, because I can't see it linking to anything but libkatepartinterfaces and libktexteditor that are both provided by kdelibs.
Here is my /etc/ld.so.conf ldy-gentoo ~ # cat /etc/ld.so.conf # ld.so.conf autogenerated by env-update; make all changes to # contents of /etc/env.d directory /usr/local/lib /usr/lib/opengl/xorg-x11/lib /usr/i686-pc-linux-gnu/lib /usr/lib/gcc/i686-pc-linux-gnu/3.4.5 /usr/lib/gcc/i686-pc-linux-gnu/3.4.4 /usr/lib/nspr /usr/lib/mozilla-firefox /usr/lib /usr/lib/openmotif-2.2 /usr/qt/3/lib /usr/kde/3.4/lib /usr/lib/nss /usr/lib/libstdc++-v3/ And error messgae: /bin/sh ../libtool --silent --tag=CXX --mode=link i686-pc-linux-gnu-g++ -Wnon-virtual-dtor -Wno-long-long -Wundef -Wall -pedantic -W -Wpointer-arith -Wwrite-strings -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts -DNDEBUG -DNO_DEBUG -O2 -Os -march=pentium-m -pipe -Wformat-security -Wmissing-format-attribute -fno-exceptions -fno-check-new -fno-common -o kscope -R /usr/kde/3.4/lib -R /usr/qt/3/lib -R /usr/lib -R /usr/kde/3.4/lib -L/usr/lib -L/usr/qt/3/lib -L/usr/kde/3.4/lib -L/usr/kde/3.4/lib main.o kscope.o calltreedlg.o cscopefrontend.o ctagsfrontend.o ctagslist.o dirscanner.o editormanager.o editorpage.o editortabs.o filelist.o frontend.o kscopeconfig.o kscopepixmaps.o newprojectdlg.o openprojectdlg.o prefcolor.o preferencesdlg.o preffrontend.o progressdlg.o projectfilesdlg.o projectmanager.o querypage.o querywidget.o scanprogressdlg.o searchlist.o cscopemsgdlg.o preffont.o prefopt.o fileview.o historypage.o symboldlg.o calltreemanager.o queryresultsmenu.o symbolcompletion.o tabwidget.o shellfrontend.o searchresultsdlg.o calltreelayout.o newprojectlayout.o openprojectlayout.o prefcolorlayout.o preffrontendlayout.o projectfileslayout.o scanprogresslayout.o cscopemsglayout.o querywidgetlayout.o preffontlayout.o prefoptlayout.o fileviewlayout.o symbollayout.o autocompletionlayout.o searchresultslayout.o preffrontend.moc.o frontend.moc.o prefcolor.moc.o querypage.moc.o historypage.moc.o calltreedlg.moc.o newprojectdlg.moc.o kscopeconfig.moc.o progressdlg.moc.o fileview.moc.o ctagsfrontend.moc.o scanprogressdlg.moc.o symboldlg.moc.o openprojectdlg.moc.o preffont.moc.o projectmanager.moc.o searchlist.moc.o prefopt.moc.o editorpage.moc.o filelist.moc.o calltreemanager.moc.o kscope.moc.o projectfilesdlg.moc.o cscopefrontend.moc.o querywidget.moc.o editormanager.moc.o editortabs.moc.o preferencesdlg.moc.o ctagslist.moc.o -lkateinterfaces -lktexteditor -lkdeui /usr/lib/gcc/i686-pc-linux-gnu/3.4.5/../../../../i686-pc-linux-gnu/bin/ld: cannot find -lkateinterfaces collect2: ld returned 1 exit status make[2]: *** [kscope] Error 1 make[2]: Leaving directory `/var/tmp/portage/kscope-1.2.0/work/kscope-1.2.0/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/kscope-1.2.0/work/kscope-1.2.0' make: *** [all] Error 2 !!! ERROR: dev-util/kscope-1.2.0 failed. !!! Function kde_src_compile, Line 224, Exitcode 2 !!! died running emake, kde_src_compile:make !!! If you need support, post the topmost build error, NOT this status message.
Hrmm I'm wondering if this might be because of KDE 3.4 vs KDE 3.5 :/ Can you check what provides libkateinterfaces.la for safety?
There is none such file at my box ldy-gentoo / # find . -name "libkateinterfaces.la" -ls ldy-gentoo / # pwd / ldy-gentoo / # equery l kde [ Searching for package 'kde' in all categories among: ] * installed packages [I--] [ ] kde-base/kde-env-3-r4 (0) [I--] [ ] kde-base/kde-i18n-3.4.3 (3.4) [I--] [ ] kde-base/kdebase-data-3.4.3 (3.4) [I--] [ ] kde-base/kdebase-kioslaves-3.4.3 (3.4) [I--] [ ] kde-base/kdebase-pam-6 (0) [I--] [ ] kde-base/kdebase-startkde-3.4.3 (3.4) [I--] [ ] kde-base/kdelibs-3.4.3-r1 (3.4) [I--] [ ] kde-base/kdepim-kresources-3.4.3 (3.4) [I--] [ ] kde-base/kdesktop-3.4.3 (3.4) [I--] [ ] kde-base/kdesu-3.4.1 (3.4) [I--] [ ] kde-base/libkdenetwork-3.4.1 (3.4) [I--] [ ] kde-base/libkdepim-3.4.3 (3.4)
(In reply to comment #3) > Hrmm I'm wondering if this might be because of KDE 3.4 vs KDE 3.5 :/ No, it doesn't. This has been "fixed" 9 months ago (Bug 94734), unfortunately only the bug has been marked as fixed, but none of the ebuilds was changed it seems.
(In reply to comment #5) > No, it doesn't. This has been "fixed" 9 months ago (Bug 94734), unfortunately > only the bug has been marked as fixed, but none of the ebuilds was changed it > seems. Not exactly. Fixed locally, but managed not to commit... *sigh*