This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: failure building gcc-3.3 (broken libiberty/vsprintf.c or build?)

From: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>
To: dj at redhat dot com
Cc: crossgcc at sources dot redhat dot com, gcc-patches at gcc dot gnu dot org, gcc at gcc dot gnu dot org, peter at baradas dot org
Date: Fri, 23 May 2003 11:29:38 -0400 (EDT)
Subject: Re: failure building gcc-3.3 (broken libiberty/vsprintf.c or build?)
References: <20030520053204.ADDB298982@baradas.org> <200305201609.h4KG9jR20778@greed.delorie.com> <200305202059.QAA18111@caip.rutgers.edu> <200305202138.h4KLccd26075@greed.delorie.com>

 > From: DJ Delorie <dj@redhat.com>
 > 
 > > 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

Follow-Ups:
- Re: failure building gcc-3.3 (broken libiberty/vsprintf.c or build?)
  - From: Joe Buck

References:
- failure building gcc-3.3 (broken libiberty/vsprintf.c or build?)
  - From: Peter Barada
- Re: failure building gcc-3.3 (broken libiberty/vsprintf.c or build?)
  - From: DJ Delorie
- Re: failure building gcc-3.3 (broken libiberty/vsprintf.c or build?)
  - From: Kaveh R. Ghazi
- Re: failure building gcc-3.3 (broken libiberty/vsprintf.c or build?)
  - From: DJ Delorie

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]