Date:	Fri, 21 Jul 2000 03:52:39 -0400 (EDT)
Message-Id:	<200007210752.DAA10681@indy.delorie.com>
From:	Eli Zaretskii <eliz AT delorie DOT com>
To:	mrs AT windriver DOT com
CC:	djgpp-workers AT delorie DOT com, gcc AT gcc DOT gnu DOT org,
	martin AT loewis DOT home DOT cs DOT tu-berlin DOT de
In-reply-to:	<200007202144.OAA02024@kankakee.wrs.com> (message from Mike Stump
	on Thu, 20 Jul 2000 14:44:39 -0700 (PDT))
Subject:	Re: GCC headers and DJGPP port
References:	<200007202144 DOT OAA02024 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: Thu, 20 Jul 2000 14:44:39 -0700 (PDT)
> 
> > > > Could you tell what other headers do we need to consider?
> > > 
> > > I'd rather tell you how to find the compiler include directories
> > > (touch t.c && gcc -v t.c), and how to run ls (dir).
> 
> > The question was about future GCC releases, for which I cannot
> > simply look in my include directories.
> 
> Don't worry about that future.  It will come and you can't stop it.
> Good, bad or indifferent.  What we can worry about it what is most
> likely to be in the next release.

The next release *is* one of what I called ``future releases''.  That
is what I was talking about; I'm sorry if that was unclear.  Please
understand that English is not my first language; I don't always catch
such fine nuances.

> This can be answered by looking in the compiler's include
> directory, just as I said.

I cannot look into the include directory of the next compiler release:
I don't have the CVS tree on my machine, as I'm not one of the
maintainers of the DJGPP port of GCC; and I don't know enough about
GCC internals to efficiently look for the information anyway.  If I
could look at the headers instead of asking, I would, believe me.

- Raw text -