On Tue, 2003-03-18 at 19:47, el lodger wrote: > gst-plugins-0.6.0-r4 > Why is it looking for /usr/kde/3 when I use 3.1? > In other parts of the build it uses /usr/kde/3.1/lib/libartsc.so. > > /bin/sh ../../libtool --mode=link g++ -march=pentium3 -O2 -pipe -o > libgstwincodec.la -rpath /usr/lib/gstreamer-0.6 -module -avoid-version > libgstwincodec_la-gstwindec.lo libgstwincodec_la-gstwincodec.lo > libgstwincodec_la-gstwinenc.lo -Wl,-rpath,/usr/lib -laviplay -lstdc++ > mkdir .libs > grep: /usr/kde/3/lib/libartsc.la: No such file or directory > sed: can't read /usr/kde/3/lib/libartsc.la: No such file or directory > libtool: link: `/usr/kde/3/lib/libartsc.la' is not a valid libtool > archive > make[3]: *** [libgstwincodec.la] Error 1 > make[3]: Leaving directory > `/home/tmp/portage/gst-plugins-0.6.0-r4/work/gst-plugins-0.6.0/ext/avif > ile' > make[2]: *** [all-recursive] Error 1 > make[2]: Leaving directory > `/home/tmp/portage/gst-plugins-0.6.0-r4/work/gst-plugins-0.6.0/ext' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory > `/home/tmp/portage/gst-plugins-0.6.0-r4/work/gst-plugins-0.6.0' > make: *** [all] Error 2 > > !!! ERROR: media-libs/gst-plugins-0.6.0-r4 failed. > !!! Function src_compile, Line 153, Exitcode 2 > !!! (no error message)
Had this happen as well. I did a # grep -r "kde/3/" /usr/lib and got the phone book. Apparently libtool embeds the KDE path in the .la files it creates. When we upgraded to KDE 3.1 and unmerged KDE 3.0, it left invalid paths in a lot of the archives. My solution was to use qpkg -v -f <package> to find the packages that the files belonged to, and recompile each of those packages. This isn't easily scriptable as far as I know. If, for example, package bar depends on package foo, and you try to recompile bar before foo, it will either fail to compile or it will compile, but will still leave invalid paths in the .la files. When you look at the output from grep, you should see the linking information, such that a .la file for package bar might say "-lfoo -lX11", etc, which can help you track down dependencies without digging through the ebuilds (you can see that foo is linked to so you should compile foo first). You should work at it until grep comes up clean. This fixed problems upgrading gst-plugins and avifile for me. I really don't know that much about all this so maybe someone here can point out a better way. Hope this helps. -- [EMAIL PROTECTED] mailing list
