Date: Wed, 13 Jun 2001 15:43:55 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: JT Williams <jeffw AT darwin DOT sfbr DOT org>
cc: djgpp-workers AT delorie DOT com
Subject: Re: GCC-3.0 related problem with src/libc/stubs/stubXXXX.S
In-Reply-To: <20010613073937.B25847@kendall.sfbr.org>
Message-ID: <Pine.SUN.3.91.1010613153949.17867F-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 Wed, 13 Jun 2001, JT Williams wrote:

> This thread (and others posted by Andris) lead me to wonder if
> djdev 2.04 should be built using gcc 2.95.3 and released ASAP,
> and djdev built with gcc 3.x be postponed for 2.05?

AFAIK, GCC 3.0 is slated to be released in a matter of days (I think I 
heard June 14 or something).  We have no practical way to release DJGPP 
v2.04 in one day, no matter how hard did we try ;-)

But that is not a grave problem, IMHO: the library build can require an 
older compiler if we so decide, because building a library is not 
something an average user is expected to do.  For example, v2.03 could 
only be built with GCC 2.8.1 or older, even though 2.9x was already 
available.