Summary: | Gentoo Linux GCC Upgrade Guide: procedure lacks a step (libstdc++-v3) | ||
---|---|---|---|
Product: | [OLD] Docs-user | Reporter: | Christian Andreetta (RETIRED) <satya> |
Component: | Other | Assignee: | Docs Team <docs-team> |
Status: | RESOLVED INVALID | ||
Severity: | critical | CC: | gcc-porting |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://www.gentoo.org/doc/en/gcc-upgrading.xml | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Christian Andreetta (RETIRED)
![]() If you still have gcc-3.3 installed, you don't need libstdc++ _at all_. I guess a call to ldconfig should be thrown in there to update the cache. If you follow the directions, python should not be linked to libstdc++.so.5, but ld.so.cache won't be updated after libstdc++-v3 is merged, so there _could_ be some breakage I guess. Portage should call env_update() at the end of every merge() or unmerge(), at least that's what I've read from the sources. env_update() should call `ldconfig` if needed. Anyway, feel free to reopen if you reproduce it. Reproduced, but it was due to an error. The old hardware system I tested with had the old toolchain compiled with a i386 CHOST (stage3-2005-r1), and the new gcc with a i586 mcpu. Then, after a gcc-config swith, the ldconfig in env-update caused the loss of the i386 libraries location. |