Date:	Thu, 20 Jul 2000 13:09:10 +0200
Message-Id:	<200007201109.NAA14755@loewis.home.cs.tu-berlin.de>
From:	"Martin v. Loewis" <martin AT loewis DOT home DOT cs DOT tu-berlin DOT de>
To:	eliz AT is DOT elta DOT co DOT il
CC:	mrs AT windriver DOT com, djgpp-workers AT delorie DOT com, gcc AT gcc DOT gnu DOT org
In-reply-to:	<200007200641.CAA09330@indy.delorie.com> (message from Eli
	Zaretskii on Thu, 20 Jul 2000 02:41:28 -0400 (EDT))
Subject:	Re: GCC headers and DJGPP port
References:	<200007192135 DOT OAA01278 AT kankakee DOT wrs DOT com> <200007200641 DOT CAA09330 AT indy DOT delorie DOT com>
User-Agent:	SEMI/1.13.3 (Komaiko) FLIM/1.12.5 (Hirahata) Emacs/20.4 (i586-pc-linux-gnu) MULE/4.0 (HANANOEN)
MIME-Version:	1.0 (generated by SEMI 1.13.3 - "Komaiko")
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

> The problem that triggered this thread is that GCC installs its own
> versions of some of those headers, which conflict with our system
> headers.

Let me take this from a different angle: Why exactly do these cause
conflicts? What exactly is the conflict? Please be as specific as
possible, e.g. providing a code example that works with only your
headers installled and breaks when ours are present (also indicate the
nature of breakage).

> In other words, we would like to make the DJGPP library development
> as independent from GCC development as possible, so that there would
> be no immediate need to release a new library version every time a new
> version of GCC is released, and no need for the users to download a
> new GCC version each time a new library release is out.

The best way to achieve this is to have gcc use the gcc-supplied
headers. Their exact contents is mandated by the ISO C standard, so
there is no need for you to change anything about it in the next ten
years. Just rely on gcc providing them, and be done.

Regards,
Martin

- Raw text -