Summary: | kdemultimedia-3.2.2-r1 ebuild fails | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Chase <chase> |
Component: | New packages | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED INVALID | ||
Severity: | major | CC: | frits.devos, gurqur |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Chase
2004-05-16 16:50:55 UTC
You've got some *.la file in /usr/lib that contains a reference to the "bad" file in question. It's not a kde problem, but you can fix it by grepping in that directory for the offending i386 line. Doing the sym link I mentioned fixed the problem. After the link is created the 'emerge --update --deep world' completes. But you're right there appear to be some bad references. Does this mean there's something wrong with the ebuilds for libaspell and libtag or just that the wrong binaries where included in the i686 GRP or stage 3 tarball? Is there a way to tell which ebuild these files belong to like with rpm? Running 'grep i386 *la' in /usr/lib outputs: libaspell.la:dependency_libs=' -L/usr/i386-pc-linux-gnu/lib -L/usr/i386-pc-linux-gnu/bin -L/usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.2 -L/usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.2/../../../../i386-pc-linux-gnu/lib -lgpm /usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.2/libstdc++.la -lm -lc -lgcc_s' libpspell.la:dependency_libs=' -L/usr/i386-pc-linux-gnu/bin -L/usr/i386-pc-linux-gnu/lib -L/usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.2 -L/usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.2/../../../../i386-pc-linux-gnu/lib /usr/lib/libaspell.la -lgpm /usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.2/libstdc++.la -lm -lc -lgcc_s' libtag.la:dependency_libs=' -lstdc++ -L/usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.2 -L/usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.2/../../../../i386-pc-linux-gnu/lib -L/usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.2/../../.. -L/usr/i386-pc-linux-gnu/bin -L/usr/i386-pc-linux-gnu/lib /usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.2/libstdc++.la -lm -lc -lgcc_s' libtag_c.la:dependency_libs=' /usr/lib/libtag.la -lstdc++ -L/usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.2 -L/usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.2/../../../../i386-pc-linux-gnu/lib -L/usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.2/../../.. -L/usr/i386-pc-linux-gnu/bin -L/usr/i386-pc-linux-gnu/lib /usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.2/libstdc++.la -lm -lc -lgcc_s' looks to be that bad binaries were installed on the lived, but i can't be certain. you haven't re-emerged those packages since, have you? I found this on the forums. It looks more correct the " ln-s ...." [url=http://forums.gentoo.org/viewtopic.php?t=174957&start=0&postdays=0&postorder=asc&highlight=usr+lib+gcclib+i386pclinuxgnu+3+3+2+libstdc+la]Emergin' GNOME 2.6 - facing the hell... [/url] "I had the same problem (dealing with the "missing" libstdc++.la), when compiling a different program. You need to run this command: fix_libtool_files.sh 'gcc -dumpversion' --oldarch i386-pc-linux-gnu This should fix the problem if gcc is looking in /usr/lib/gcc-lib/i386/xxxxx for the file it needs. For some reason, gcc is looking for the file in the wrong directory." the comments tell how to fix the problem. *** Bug 75274 has been marked as a duplicate of this bug. *** |