Ian Lance Taylor wrote:
> So the question is why, before his change, those *-elf targets didn't
> have an explicit fixproto=no, and I'm sure the answer is simply
> laziness and/or lack of knowledge. fixproto is more or less a no-op
> when run on modern header files, so it's not like anybody would
Mark Mitchell <[EMAIL PROTECTED]> writes:
> Hmm. A lot of the *-elf targets have use_fixproto=yes in config.gcc,
> which somewhat surpises me; I'd have thought newlib didn't require that.
Nathanael changed the default here:
2003-09-30 Nathanael Nerode <[EMAIL PROTECTED]>
* config.gcc
Paul Brook wrote:
> This suggests two options on what's supposed to happen:
> (a) fix-header should actually be compiled for the "host" environment. If
> host==build we run it, otherwise we just install it and let the user run it
> on the build system.
I think this is the right option, though,
I'm having problems building a canadian cross to a target that uses fixproto
(m68k-elf). There seems to be some inconsistency in how fix-headers is
build/run.
In gcc/Makefile.in we have the following comments:
# gen-protos and fix-header are compiled with CC_FOR_BUILD, but they are only
# used
