ftp.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp-workers/2002/05/17/10:23:22

X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f
Date: Fri, 17 May 2002 10:23:20 -0400
Message-Id: <200205171423.g4HENK406652@envy.delorie.com>
X-Authentication-Warning: envy.delorie.com: dj set sender to dj AT delorie DOT com using -f
From: DJ Delorie <dj AT delorie DOT com>
To: pavenis AT lanet DOT lv
CC: djgpp-workers AT delorie DOT com
In-reply-to: <Pine.A41.4.05.10205171001030.24004-100000@ieva06> (message from
Andris Pavenis on Fri, 17 May 2002 10:07:56 +0300 (WET))
Subject: Re: gcc 3.1
References: <Pine DOT A41 DOT 4 DOT 05 DOT 10205171001030 DOT 24004-100000 AT ieva06>
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

> It works for DJGPP as far as I have tested.

My point was to build the *official* sources, and provide a status
note to the gcc web pages - they're keeping track of what builds and
what doesn't, and I'd like DJGPP to be listed on the "what builds"

I would like this to have higher priority than other gcc work, such as
ongoing patches to make porting easier, or changes to binutils.  Just
send them a note with what changes or special binutils are needed.

- Raw text -

  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019