This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: fixincludes
- From: Richard Guenther <richard dot guenther at gmail dot com>
- To: Franz Fehringer <fehrin at t-online dot de>
- Cc: gcc at gcc dot gnu dot org
- Date: Sat, 23 Jan 2010 17:39:27 +0100
- Subject: Re: fixincludes
- References: <4B5B2531.2090202@t-online.de>
On Sat, Jan 23, 2010 at 5:34 PM, Franz Fehringer <fehrin@t-online.de> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi all,
>
> I have two hopefully not too dull questions about the gcc fixincludes
> mechanism:
> 1) When after the initial fixinclude run (parts of) new software is
> installed into /usr/include, the fixincludes run has to be repeated (at
> least in principle), is this true?
As we generally only fixinclude pieces of the C runtime and the C
runtime is required to build GCC this is not true. fixincludes may of
course match in random header files as well, but that is not
intended in general.
> 2) IIRC several years ago there were plans to abandon fixincludes and to
> do the header fixing in realtime on every gcc run, what happened to the
> pertaining efforts?
That would surely be slow.
Richard.