Re: MIPS port and fixincludes

[Geoff Keating <geoffk at cygnus dot com>]

Zack Weinberg <zack@wolery.cumb.org> writes:

> On Tue, Jan 18, 2000 at 01:24:29PM -0500, Gavin Romig-Koch wrote:
> > 
> > Well, I agree this is a minor issue, at least until we break
> > something :-).  
> > 
> > I think fixincludes should do as little as resonably possible
> > (for some definition of reasonable).
> 
> I'm looking through the machine_name fixes applied on this machine
> (bleeding edge linux distribution) and all of them are unnecessary,
> or at least questionable.  Examples:
> 
> --- /usr/include/./gc/gc.h      Fri Oct 29 15:39:58 1999
> --- /usr/include/./linux/a.out.h        Sun Dec 26 10:44:59 1999
...

> I'm half tempted to say we should discard this fix entirely and say
> that if your vendor provides broken headers, -ansi may not work, sorry.

If you include "linux/a.out.h", using glibc, and you use -ansi, you
should not be surprised if your program does not work, because
"linux/a.out.h" is not an ANSI header.  It's like trying to use
fdopen() with -ansi: it will not work, because fdopen() will not be
defined if you ask for C standard conformance.

So this fix really only needs to be applied to the small number of
standard C headers.

-- 
- Geoffrey Keating <geoffk@cygnus.com>