From: "Mark E." <snowball3 AT bigfoot DOT com>
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>, djgpp-workers AT delorie DOT com
Date: Sun, 4 Jun 2000 11:32:02 -0400
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: Testers wanted: a fix for GCC header problem
Message-ID: <393A3E32.18467.70937@localhost>
References: <393959CC DOT 186D9B30 AT softhome DOT net>
In-reply-to: <Pine.SUN.3.91.1000604175351.11052H-100000@is>
X-mailer: Pegasus Mail for Win32 (v3.12c)
Reply-To: djgpp-workers AT delorie DOT com

> 
> On Sat, 3 Jun 2000, Laurynas Biveinis wrote:
> 
> > 1) limits.h - it uses #include_next. Fine with us, not very fine with GCC maintainers.
> > It is somehow wrong for embedded systems, as they say. That was the reason, why
> > #include_next wasn't adopted to other header files.
> 
> I'm afraid I don't understand their reasoning.  Does someone know more 
> about this?  Any pointers to discussions on public forums?
>

I posted these pointers a while back. Look in the djgpp-workers archive or 
search the gcc-patches archive using "freebsd user_h".
 
> > 2) float.h - problem with it are in the past now. 
> 
> How do you mean: in the past?  Does GCC install its own float.h?

Not anymore. The maintainer agreed (rather grudgingly) to allow float.h not 
to be generated.