This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Convert 3.2 sources to ISO C90
- From: Stan Shebs <shebs at apple dot com>
- To: law at redhat dot com
- Cc: Daniel Jacobowitz <drow at mvista dot com>, "David S. Miller" <davem at redhat dot com>, robertlipe at usa dot net, gcc at gcc dot gnu dot org
- Date: Wed, 05 Jun 2002 22:48:09 -0700
- Subject: Re: Convert 3.2 sources to ISO C90
- Organization: Apple Computer, Inc.
- References: <6723.1023340921@porcupine.cygnus.com>
law@redhat.com wrote:
>
> In message <20020606045720.GA13668@nevyn.them.org>, Daniel Jacobowitz writes:
> > Conveniently, I believe Geoff contributed the basis of code to run
> > fixincludes at install rather than build time last week... Packaging it
> > up appropriately should just be the matter of an hour or two.
> Yup. What's even better is the ability to run fixincludes *after* installation
> of the compiler. Cygnus/Red Hat has had hacks to do this for a long time
> as it didn't make any sense (and was a legal minefield) to distribute
> fixed header files as part of our releases.
>
> For example, let's say you built & installed GCC. Then you installed some
> patch from your vendor which twiddled the include files -- you want to
> get those newly twiddled include files re-scanned and fixed.
>
> This means that fixincludes would actually be part of the installed set of
> programs so that it could be run later. Or re-run if the install directory
> is copied from one system to another.
So it sounds like this would take away one of your concerns about
making HP binaries available to people who need something to get
started with? People will be able to use 3.1 now to get started,
and then build 3.2 binaries with install-time fixincludes in the
future.
Stan