This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: aggressive fixincludes

To: Mark Mitchell <mark at codesourcery dot com>
Subject: Re: aggressive fixincludes
From: Michael Vance <briareos at lokigames dot com>
Date: Wed, 24 Nov 1999 11:31:11 -0800
Cc: per at bothner dot com, gcc at gcc dot gnu dot org, autogen at linuxbox dot com
References: <199911241731.JAA10342@atrus.synopsys.com> <m2emdfd960.fsf@magnus.bothner.com> <19991124105844J.mitchell@codesourcery.com>

On Wed, Nov 24, 1999 at 10:58:44AM -0800, Mark Mitchell wrote:

> I think we want to make sure fixincludes is correct.  After all, the
> whole point is to make "weird" headers OK; if that process isn't safe,
> we're not a whole lot better off than we were before.

Pardon my coming in late, but is fixincludes generating a tree of
'corrected' headers and then writing it to the system /usr/include,
etc., during a make install?

If so, is there a way to disable this?

m.

-- 
Programmer                         "I wrote a song about dental floss,
Loki Entertainment Software         but did anyone's teeth get cleaner?"
http://lokigames.com/~briareos/              - Frank Zappa, re: the PMRC

Follow-Ups:
- Re: aggressive fixincludes
  - From: Mark Mitchell

References:
- Re: aggressive fixincludes
  - From: Joe Buck
- Re: aggressive fixincludes
  - From: Per Bothner
- Re: aggressive fixincludes
  - From: Mark Mitchell

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]