Date: Sun, 29 Apr 2001 09:50:10 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: djgpp-workers AT delorie DOT com
Subject: Re: gcc-3.0 related patches for DJGPP CVS version
In-Reply-To: <200104281846.OAA01811@envy.delorie.com>
Message-ID: <Pine.SUN.3.91.1010429094950.26520G-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 Sat, 28 Apr 2001, DJ Delorie wrote:

> We could put __GO32__ in <sys/version.h> but there's still the
> problem of 2.03 users.

Yes.

I think we need to handle __GO32__ in the same cautious manner we did
with __DJGPP__.  That is, remove it from GCC only when sufficient time
passes after sys/version.h with its definition is released.  For
v2.04, I believe we don't even have a tentative release date (perhaps
we should, btw).

So I think we could add __GO32__ to sys/version.h now, but we should
reinstate it in GCC as well, for the time being.

What about `unix'--should we add it to sys/version.h as well?  I'm
fairly sure some ports rely on it being defined, and __unix__ is
almost never used in programs I've seen.