On 09/09/2010 06:00 PM, walt wrote:
On 09/08/2010 03:10 PM, Nikos Chantziaras wrote:
When building GCC, it will scan all headers in /usr/include and apply
fixes to them, and then copy them and use the modified versions. Now a
binary distro (AFAIK) will ship the GCC modified headers, so there's
no problem.
Gentoo on the other hand will work as intended by GCC only if the user
re-emerges GCC after every time a package is emerged that installs
headers. Obviously, no user does that.
So the question is simple; does Gentoo deal with this problem in any way?
Maybe I misunderstand your question, but AFAIK the only reason to
re-compile any
package is if the libraries it links to have changed, no?
No, mostly the main reason is when updates are available. And in Gentoo
this always means building from source.
AFAICS gcc links only to libraries installed by glibc. therefore in the
case of
recompiling gcc itself, it should need/use only the headers installed by
glibc.
Yeah, you misunderstood the question ;-) GCC applies changes to header
files in /usr/include. Lets say to ncurses.h. When you then update
ncurses, a new header is installed in /usr/include, but GCC only has the
modified version of it from the previous version:
http://gcc.gnu.org/onlinedocs/gcc-3.4.6/gcc/Fixed-Headers.html
Of course it could be me who doesn't really understand what's going on
here though.
