public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nikos Chantziaras <realnc@arcor.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: How does Gentoo deal with GCC's header fixes?
Date: Fri, 10 Sep 2010 02:48:02 +0300	[thread overview]
Message-ID: <i6brmk$o23$1@dough.gmane.org> (raw)
In-Reply-To: <201009092117.53236.alan.mckinnon@gmail.com>

On 09/09/2010 10:17 PM, Alan McKinnon wrote:
> Apparently, though unproven, at 18:26 on Thursday 09 September 2010, Volker
> Armin Hemmann did opine thusly:
>
>> On Thursday 09 September 2010, 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?
>>>
>>> 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.
>>>
>>> (And the only reason to re-compile an existing glibc is if the linux
>>> kernel headers change.  I always re-compile glibc when the linux kernel
>>> headers change, but I never thought about re-compiling gcc as well.
>>> Maybe I should.)
>>>
>>> Corrections are requested if I'm wrong about all of this.
>>
>> hm, I never recompile glibc after a header update.... or anything else....
>
>
> Me neither :-)
>
> I know I should, and why. But don't.

Just want to point out that this was about GCC's fixed headers, not 
glibc, which makes it off-topic and completely unrelated to the original 
topic :)




  parent reply	other threads:[~2010-09-09 23:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-08 22:10 [gentoo-user] How does Gentoo deal with GCC's header fixes? Nikos Chantziaras
2010-09-09 15:00 ` [gentoo-user] " walt
2010-09-09 15:18   ` Nikos Chantziaras
2010-09-09 16:26   ` Volker Armin Hemmann
2010-09-09 19:17     ` Alan McKinnon
2010-09-09 21:29       ` Neil Bothwick
2010-09-09 23:48       ` Nikos Chantziaras [this message]
2010-09-10  0:56         ` walt
2010-09-09 20:05     ` walt
2010-09-10  4:47       ` Volker Armin Hemmann
2010-09-10 14:39 ` [gentoo-user] " Paul Hartman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='i6brmk$o23$1@dough.gmane.org' \
    --to=realnc@arcor.de \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox