From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24431 invoked by alias); 23 May 2003 15:29:50 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 24326 invoked from network); 23 May 2003 15:29:50 -0000 Received: from unknown (HELO caip.rutgers.edu) (128.6.236.10) by sources.redhat.com with SMTP; 23 May 2003 15:29:50 -0000 Received: (from ghazi@localhost) by caip.rutgers.edu (8.9.3/8.9.3) id LAA21736; Fri, 23 May 2003 11:29:38 -0400 (EDT) Date: Fri, 23 May 2003 15:30:00 -0000 From: "Kaveh R. Ghazi" Message-Id: <200305231529.LAA21736@caip.rutgers.edu> To: dj@redhat.com Subject: Re: failure building gcc-3.3 (broken libiberty/vsprintf.c or build?) Cc: crossgcc@sources.redhat.com, gcc-patches@gcc.gnu.org, gcc@gcc.gnu.org, peter@baradas.org References: <20030520053204.ADDB298982@baradas.org> <200305201609.h4KG9jR20778@greed.delorie.com> <200305202059.QAA18111@caip.rutgers.edu> <200305202138.h4KLccd26075@greed.delorie.com> X-SW-Source: 2003-05/txt/msg02094.txt.bz2 > From: DJ Delorie > > > FWIW, it appears to be fixed on mainline. We can backport vsprintf.c > > to 3.3.1 if you think it's worth fixing. Here's the diff: > > If 3.3 complains about varargs, we should backport it. Done. (I did "make vsprintf.o" before and after the patch and verified it fixed the problem.) -- Kaveh R. Ghazi ghazi@caip.rutgers.edu