This is the mail archive of the
mailing list for the GCC project.
Re: Fix various cross-fixinclude problems
- From: "Aaron W. LaFramboise" <aaronavay62 at aaronwl dot com>
- To: Geoffrey Keating <gkeating at apple dot com>
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Fri, 12 Nov 2004 20:06:40 -0600
- Subject: Re: Fix various cross-fixinclude problems
- References: <20041112191507.9D2601E8E192@geoffk5.apple.com>
Geoffrey Keating wrote:
> - Makes sure that fixinclude/ is built on all targets. Even if the
> target doesn't want to fix any headers, fixinclude/ should still be
> built, to make sure that the dummy fixincludes can be installed
> (and give a consistent set of installed programs).
Is there value in installing fixincludes even if it is unused? Is there
something other than GCC than uses it?
There was some discussion of this a month or so ago, and no-one
mentioned at the time that fixincludes should always be built.
I'm not sure that fixincludes builds correctly on all of those
platforms, which I think is why it was disabled. (It does build now on
*-mingw32, though, which was my primary concern.)
Aaron W. LaFramboise