This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
RE: fixincludes & other OS deps
- To: Bruce Korb <bkorb at veritas dot com>
- Subject: RE: fixincludes & other OS deps
- From: Brian Ford <ford at vss dot fsi dot com>
- Date: Mon, 25 Jun 2001 11:36:58 -0500 (CDT)
- cc: gcc <gcc at gcc dot gnu dot org>
On Mon, 25 Jun 2001, Bruce Korb wrote:
> Hi Brian,
>
> > Is there any way to re-run fixincludes after, say,
> > an OS patch or upgrade without bootstrapping a new compiler?
>
> I am glad you happened to write about this. :-)
>
I thought you might be after reading the archives on this topic.
> I would be more than happy to guide you through the process
> of making an installable fixincludes. It is possible that
> it may have to be a slightly different binary from the one
> used during the build, but we can probably avoid that, too.
>
I would think that avoiding this would be very desirable.
> First, propose some interfaces describing how this installable
> version would work. You will likely have to feed it some
> output from 'config.guess', tell it where to find headers
> [if not /usr/include], and where the result is to be installed.
> Much of this is now done via environment variables. Much too
> kludgey for something to be installed. Once there is general
> agreement on that, as I said, I would be happy to guide you
> through the implementation.
>
Ok, I'll show my ignorance and purpose a very simple interface.
When the installed version is executed, it removes all includes
that were formally "fixed" (I understand this might be a tough problem
to determine exactly which files these are), it then "fixes" the current
set of system includes (their locations defined by the original
configure), and writes these "fixed" includes into the appropriate gcc-lib
include directory.
Show me the swiss cheese behind this simple proposal.
--
Brian Ford
Software Engineer
Vital Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax: 314-551-8444