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