Talk:HOWTO gcc4
From Gentoo Linux Wiki
Is bug 105020 a problem here?
---
Hmmm... isn't
#emerge -e system && emerge -e world
somewhat redundant since "world" is a superset of "system". I can see that the explicit compilation of gcc and glibc are needed so gcc-config can select the proper version, but after that -e world should surely suffice?
>> In order to "properly" rebuild your system you actually need to do --
emerge -e system; emerge -e system; emerge -e world; emerge -e world
- REASONING*
When you build a newer compiler with an older one, its considered "dirty" in that it was built on a (presumably) flawed base, so you "need" to rebuild everything with the newer version. The second -e {system|world} ensures that all compile-time options are built using the clean system, /against/ clean versions; this holds true when you're doing the -e worlds. There is however a script called emwrap.sh which is designed to significantly cut down on redundant builds that wont benefit from the additional compiles.
This methodology however, is generally only "required" when doing significant toolchain upgrades (such as this). See also:
http://forums.gentoo.org/viewtopic-t-282474-highlight-emwrap.html
[edit] How exactly do we "fix any problems"?
After we are told to "qlist -o $(qlist -ICv) | scanelf -Bs__guard -qf - -F%F#s | xargs qfile", we are told to "fix any problems".
So how do we do that exactly?
For instance in my case the above command outputs
sys-libs/glibc (/lib/ld-2.4.so)<br>
sys-libs/glibc (/lib/libc-2.4.so) <br>
sys-libs/glibc (/usr/sbin/nscd) <br>
This tells me that something is wrong, and that it is something to do with __guard, whatever that is, but beyond that I'm in the dark. Ireneshusband 21:01, 27 July 2006 (UTC)
