Date: Wed, 22 May 2002 08:51:24 +0300 (WET)
From: Andris Pavenis <pavenis AT lanet DOT lv>
X-Sender: pavenis AT ieva06
To: Andrew Cottrell <acottrel AT ihug DOT com DOT au>
Cc: djgpp-workers AT delorie DOT com
Subject: Re: GCC 3.1 & CVS LIBC failure
In-Reply-To: <002801c20126$ab7bd680$0102a8c0@acceleron>
Message-ID: <Pine.A41.4.05.10205220845350.19322-100000@ieva06>
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, 22 May 2002, Andrew Cottrell wrote:

> All,
> 
> I thought I should update to GCC 3.1 seeing how yesterday it was available
> from the v2gnu directory on Simtel. I have not gotten to the bottom of this
> yet, but so far GCC 3.1 gives the following error when building the CVS
> LIBC. I did a CVS LIBC refresh yesterday afternoon (now morning in OZ) to
> ensure I had the latest files.

I only tried to build CVS libc with gcc-3.1 prerelease a rather long time
ago. Related patches were not checked in. So making libc compatible with
GCC-3.1 is the next task to do. Eli is perhaps right about need to use
va_list and related definitions instead 'char **' or something
similar.  

Andris