I'm trying to update k3b, it compile correctly, but $ ebuild /usr/portage/app-cdr/k3b/k3b-0.12.14.ebuild install break when it gets to: $ /bin/sh ../libtool --silent --mode=install /bin/install -c -p libk3b.la /var/tmp/portage/k3b-0.12.14/image//usr/lib/libk3b.la which issue: $ powerpc-unknown-linux-gnu-g++ -shared -nostdlib -mtune=G4 -mcpu=G4 -maltivec -mabi=altivec -Wl,--no-undefined -Wl,--allow-shlib-undefined -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts -Wall -W -Wpointer-arith -DNDEBUG -DNO_DEBUG -O2 -O2 -pipe -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common /usr/lib/gcc/powerpc-unknown-linux-gnu/3.4.5/../../../crti.o /usr/lib/gcc/powerpc-unknown-linux-gnu/3.4.5/crtbeginS.o .libs/dummy.o -Wl,--whole-archive core/.libs/libk3bcore.a cddb/.libs/libcddb.a projects/.libs/libk3bproject.a plugin/.libs/libk3bplugin.a tools/.libs/libk3btools.a jobs/.libs/libjobs.a -Wl,--no-whole-archive -Wl,--rpath -Wl,/usr/kde/3.4/lib -Wl,--rpath -Wl,/usr/qt/3/lib -Wl,--rpath -Wl,/usr/lib/gcc/powerpc-unknown-linux-gnu/3.4.5 -Wl,--rpath -Wl,/usr/lib -L/usr/lib/gcc/powerpc-unknown-linux-gnu/3.4.5 -L/usr/kde/3.4/lib -L/usr/qt/3/lib -L/usr/lib -L/usr/powerpc-unknown-linux-gnu/bin -L/usr/powerpc-unknown-linux-gnu/lib -L/usr/lib/gcc/powerpc-unknown-linux-gnu/../../../powerpc-unknown-linux-gnu/lib -L/usr/X11R6/lib -L/var/tmp/portage/k3b-0.12.14/image//usr/lib -lsamplerate -lk3bdevice -L/var/tmp/portage/k3b-0.12.14/image//usr/kde/3.4/lib -lkio -lkdeui -lkdesu -lkwalletclient -lkdecore -lDCOP -lresolv -lutil -lart_lgpl_2 -lidn -lkdefx -L/var/tmp/portage/k3b-0.12.14/image//usr/qt/3/lib -lqt-mt -lmng -ljpeg -lXi -lXrandr -lXcursor -lXinerama -lXft -lfontconfig -lfreetype -lexpat -ldl -lpng -lXext -lX11 -lSM -lICE -lpthread -lXrender -lz -lfam -lrpcsvc -lhal -ldbus-qt-1 -ldbus-1 -lnsl -L/var/tmp/portage/k3b-0.12.14/image//usr/lib/gcc/powerpc-unknown-linux-gnu/3.4.5 -L/usr/lib/gcc/powerpc-unknown-linux-gnu/3.4.5/../../../../powerpc-unknown-linux-gnu/lib -L/usr/lib/gcc/powerpc-unknown-linux-gnu/3.4.5/../../.. -lstdc++ -lm -lc -lgcc_s /usr/lib/gcc/powerpc-unknown-linux-gnu/3.4.5/crtsavres.o /usr/lib/gcc/powerpc-unknown-linux-gnu/3.4.5/crtendS.o /usr/lib/gcc/powerpc-unknown-linux-gnu/3.4.5/../../../crtn.o -Wl,-soname -Wl,libk3b.so.2 -o .libs/libk3b.so.2.0.0 With these errors: core/.libs/libk3bcore.a(k3bcore.o): In function `K3bCore::init()': k3bcore.cpp:(.text+0x1b4): undefined reference to `K3bDevice::DeviceManager::scanBus()' core/.libs/libk3bcore.a(k3bcore.o): In function `K3bCore::readSettings(KConfig*)': k3bcore.cpp:(.text+0x238): undefined reference to `K3bDevice::DeviceManager::readConfig(KConfig*)' core/.libs/libk3bcore.a(k3bcore.o): In function `K3bCore::saveSettings(KConfig*)': k3bcore.cpp:(.text+0x348): undefined reference to `K3bDevice::DeviceManager::saveConfig(KConfig*)' core/.libs/libk3bcore.a(k3bcore.o): In function `K3bCore::K3bCore(QObject*, char const*)': k3bcore.cpp:(.text+0xbd4): undefined reference to `K3bDevice::DeviceManager::DeviceManager(QObject*, char const*)' core/.libs/libk3bcore.a(k3bcore.o): In function `K3bCore::K3bCore(QObject*, char const*)': ... It seem to be related to the -L/usr/lib beiing in front of the -L/var/tmp/portage/k3b-0.12.14/image//usr/lib. So the linker link against the old version of k3bdevice. I tryed running the link command by manually and it link, when the -L../image//usr/lib is in front of the -L/usr/lib. The problem is how to fix this so the ebuild will issue the link in the right order ? Perhaps libtool is the problem so here's the relevant part of my emerge --info: System uname: 2.6.15-gentoo-r7 ppc 7447A, altivec supported Gentoo Base System version 1.6.14 dev-lang/python: 2.3.5, 2.4.2 sys-apps/sandbox: 1.2.10 sys-devel/autoconf: 2.13, 2.59-r7 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-r4
Can you tell me which patches are being applied by elibtoolize before ./configure runs?
*** This bug has been marked as a duplicate of 131523 ***
