Summary: | gcc 3.3.4 ebuild fails with libtool: link: `/usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.4/libstdc++.la' is not a valid libtool archive | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | jake <jake> |
Component: | New packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | VERIFIED DUPLICATE | ||
Severity: | normal | CC: | ppc64, toolchain |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
jake
2005-04-16 12:19:18 UTC
gcc-3.3.4 is not in portage - emerge sync would be handy. :-) Don't listen to Jakub. Please run: fix_libtool_files.sh 3.3.4 It's not gcc that's failing. A package has hardcoded the path to the libstdc++ library in its .la files. These files needs to be fixed with the above command. Sorry. Really did not figure out what the actual problem is. :/ I just hit this with 3.4.1 -> 3.4.3 as have some other ppc64 folks. Seems like a curious problem that the average bear might easily run into and we should program defensively so the unsuspecting won't trip over it. I'm going to cc the toolchain herd to see if they have any opinions / observatoins on this. Perhaps I'm being stupid and missed something obvious that should have been done in the ppc64 profile or ... well who knows ... thus why we turn to wise sages of arcane lore. you may also have to run: fix_libtool_files.sh --oldarch i386-pc-linux-gnu` *** This bug has been marked as a duplicate of 84324 *** all quiet time to stick a fork in it |