Date: Thu, 20 Jul 2000 20:40:58 -0400
Message-Id: <200007210040.UAA01896@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: mrs AT windriver DOT com
CC: djgpp-workers AT delorie DOT com, gcc AT gcc DOT gnu DOT org
In-reply-to: <200007210016.RAA06898@kankakee.wrs.com> (message from Mike Stump
	on Thu, 20 Jul 2000 17:16:17 -0700 (PDT))
Subject: Re: GCC headers and DJGPP port
References:  <200007210016 DOT RAA06898 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
Precedence: bulk


> Actually, about the only way to avoid that, is taking a more active
> role in gcc, testing snapshots, reporting new problems that crop up,
> submitting fixes that arise.

I believe we're doing this.  The problem is that djgpp releases
are so infrequent (one per year or two)

> In this case, a fixincludes chunk is the standard way to correct this
> problem (until such time as a new release of the library comes out to
> solve it).

I recall that at the time, using fixincludes under DOS simply wasn't
an option.  Perhaps this new fixincludes will show more promise for
us.