Date: Mon, 26 Apr 1999 16:47:27 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Andris Pavenis <pavenis AT lanet DOT lv>
cc: djgpp-workers AT delorie DOT com
Subject: Re: v2.03: wrapping up
In-Reply-To: <B0000084866@stargate.astr.lu.lv>
Message-ID: <Pine.SUN.3.91.990426164338.6979C-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Mon, 26 Apr 1999, Andris Pavenis wrote:

> 	Slackware-3.6	- egcs-1.0.3
> 	Slackware-4.0 beta2 - egcs-1.1.2
> 	Suse-6.0 - even worse - egcs snapshot from January
> 	RedHat-5.2 - egcs-1.0.3
> 	Debian-2.1 - egcs-1.1

I know; that's why I asked the question.  Cygwin and Mingw32 also use
EGCS, AFAIK.  It seems that GCC 2.8.1 is all but dead and not actively
maintained anymore.  I think we need to decide whether we switch to EGCS,
and if so, begin to use primarily it for everything, including compiling
the binaries uploaded to SimTel.NET. 

Does EGCS require to rebuild libc.a with it, or the stock distribution is 
good enough?

> They usually have also gcc-2.7.2.3 binary (C only)

Which reminds me to ask: how many people here still use GCC 2.7.x for 
DJGPP-related work?