From: Mike Stump <mrs AT windriver DOT com>
Date: Wed, 19 Jul 2000 14:35:28 -0700 (PDT)
Message-Id: <200007192135.OAA01278@kankakee.wrs.com>
To: eliz AT is DOT elta DOT co DOT il, martin AT loewis DOT home DOT cs DOT tu-berlin DOT de
Subject: Re: GCC headers and DJGPP port
Cc: djgpp-workers AT delorie DOT com, gcc AT gcc DOT gnu DOT org
Reply-To: djgpp-workers AT delorie DOT com

> Date: Wed, 19 Jul 2000 14:25:53 -0400 (EDT)
> From: Eli Zaretskii <eliz AT delorie DOT com>
> To: martin AT loewis DOT home DOT cs DOT tu-berlin DOT de

> Yes, the actual problem is that GCC installs its headers in a way
> that cause them to be used before the system headers.  A related
> problem is that GCC uses its own versions of stddef.h, limits.h, and
> other headers instead of the system headers when GCC is built.  We
> were worried that using headers that are different from the system
> headers might produce buggy GCC binaries, due to conflicts with
> libc.a against which the native DJGPP port is linked.

Worrying isn't useful.  Verify that they are accurate and
don't cause problems and be done with it.  If there are bugs in them,
fix them, submit the patches to fix them, and be done with it.