Date:	Thu, 20 Jul 2000 02:41:28 -0400 (EDT)
Message-Id:	<200007200641.CAA09330@indy.delorie.com>
From:	Eli Zaretskii <eliz AT delorie DOT com>
To:	mrs AT windriver DOT com
CC:	martin AT loewis DOT home DOT cs DOT tu-berlin DOT de, djgpp-workers AT delorie DOT com,
	gcc AT gcc DOT gnu DOT org
In-reply-to:	<200007192135.OAA01278@kankakee.wrs.com> (message from Mike Stump
	on Wed, 19 Jul 2000 14:35:28 -0700 (PDT))
Subject:	Re: GCC headers and DJGPP port
References:	<200007192135 DOT OAA01278 AT kankakee DOT wrs DOT com>
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

> From: Mike Stump <mrs AT windriver DOT com>
> Date: Wed, 19 Jul 2000 14:35:28 -0700 (PDT)
> 
> 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.

Sorry, I'm not sure I understand.

The DJGPP system headers are maintained by the DJGPP project.  These
headers are perfectly okay, they don't need any fixing.

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

If you mean that we should submit patches to the GCC maintainers to
fix the headers installed by GCC, then that's a maintenance burden we
would like to avoid, at least for the headers that there's no real
need for GCC to install.

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.

- Raw text -