Date: Mon, 3 Jun 2002 07:47:00 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: sandmann AT clio DOT rice DOT edu
cc: djgpp-workers AT delorie DOT com, rich AT phekda DOT freeserve DOT co DOT uk
Subject: Re: DJGPP CVS & gcc 3.1 [patch included]
In-Reply-To: <10206021956.AA17408@clio.rice.edu>
Message-ID: <Pine.SUN.3.91.1020603074214.19041B-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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


On Sun, 2 Jun 2002 sandmann AT clio DOT rice DOT edu wrote:

> > No, I think we should rather do something inside mkdoc.cc to avoid the
> > error.  For example, we could copy the relevant parts of stdio.h into
> > mkdoc.cc instead if including stdio.h.  Ugly, but effective and robust.
> 
> I'm already planning to provide an updated djtypes.h to fix this in the
> refresh++.

Thanks.  I guess that would be okay as well.

These dependencies on headers which come with GCC are precisely the 
nightmare we were afraid of back when we tried to talk with GCC 
maintainers.  We are lucky a refresh was in the works this time anyhow.  
In the future, we won't be so lucky, unless someone volunteers to upgrade 
djdev each time GCC gives us this kind of trouble.