Date: Tue, 3 Feb 1998 11:42:47 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: djgpp-workers AT delorie DOT com
Subject: Re: iostream concern
Message-ID: <Pine.SUN.3.91.980203114156.21682H-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Thu, 29 Jan 1998, Andrew Crabtree wrote:

> > How is the generated stddef.h different from ours?  Can we just make the 
> > necessary changes in our version and forget about this?
> They are not even close.  I'll have to search for how to disable it.
> Here's the stddef that gcc uses.  Its possible we could modify it 
> so that it works properly too I suppose.

No, that's not what I meant.  stddef.h which comes with gcc is a
hodge-podge of tricks which should work on all the supported platforms
that might need to bootstrap gcc with a native compiler and native
headers.  This is why that stddef.h is so complex.  But we don't have
the problem it is intended to solve, so the only thing we need to
worry about is where *our* stddef.h conflicts with what gcc build
process expects.  If there are such places, we need to fix them and
then make gcc build process use our version.