From: Joe Buck <jbuck AT racerx DOT synopsys DOT com>
Message-Id: <200007191524.IAA29726@racerx.synopsys.com>
Subject: Re: GCC headers and DJGPP port
To: lauras AT softhome DOT net (Laurynas Biveinis)
Date: Wed, 19 Jul 2000 08:24:23 -0700 (PDT)
Cc: djgpp-workers AT delorie DOT com, eliz AT is DOT elta DOT co DOT il,
        martin AT loewis DOT home DOT cs DOT tu-berlin DOT de, gcc AT gcc DOT gnu DOT org
In-Reply-To: <39759515.DE714E32@softhome.net> from "Laurynas Biveinis" at Jul 19, 2000 01:46:29 PM
X-Mailer: ELM [version 2.5 PL2]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


> Mike Stump wrote:
> > Well, I reviewed stddef.h, as it is one of the culprits.  After
> > reading it, I came to the conclusion that we can probably eject it
> > from the compiler safely.  It does seem like there is little reason to
> > have it in the compiler, better to be apart of newlib, of glibc, and
> > then all the complexity of it, and the heartache it causes, goes
> > away, permanently.
> 
> I like this idea. Any objections?

Wouldn't it break the SunOS4 port, or other ports where we're
bootstrapping from an ancient K&R environment and the C library
is highly nonstandard?

(I suppose stddef.h could be omitted only on the platforms where it
causes problems.)