Summary: | emerge gcc (gcc 3.3.2) installed GCC but failed to update library paths in ld.so.conf | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jonathan Jaloszynski <gentoo> |
Component: | [OLD] GCC Porting | Assignee: | Please assign to toolchain <gcc-porting> |
Status: | RESOLVED DUPLICATE | ||
Severity: | critical | CC: | David.Huff, heldhelm |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Jonathan Jaloszynski
2004-01-29 14:55:54 UTC
This same problem happened to me on all my frontline servers. The /etc/ld.so.conf file had the old libstc* path before the new one so when env-update/ldconfig ran the old information was used and is incorrect. This bug currently could hit all systems that are setup to do daily updates via "emerge -DU world" My solution was to remove the depricated path from /etc/ld.so.conf and run ldconfig. Same here, but on my box simply running ldconfig solved it, since the (in /etc/ld.so.conf) still existing path /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.3 was no longer existant (thanks to autoclean). I think the problem is that env-update sorts the lines of /etc/ld.so.conf alphabetically (ending up with the old version in front of the new one), since in /etc/env.d/05gcc LDPATH has both paths (/foo/3.3.2:/foo/3.2.3) in the right order. |