This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.

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: Randy Rude <randy dot rude at gdcanada dot com>
To: DJ Delorie <dj at redhat dot com>
Cc: pbarada at mail dot wm dot sps dot mot dot com, peter at baradas dot org,kai dot ruottu at luukku dot com, gcc at gcc dot gnu dot org, crossgcc at sources dot redhat dot com
Date: 22 May 2003 08:58:15 -0600
Subject: Re: failure building gcc-3.3 (broken libiberty/vsprintf.c or build?)
References: <20030520053204.ADDB298982@baradas.org><3EC9F529.6060106@luukku.com> <20030521034551.108CE98982@baradas.org> <20030521063417.3C30B98982@baradas.org><1053527958.14557.1.camel@d1d6k111.bowman.gdcanada.com><200305211509.h4LF98K00400@hyper.wm.sps.mot.com> <200305211738.h4LHcjZ21775@greed.delorie.com>

On Wed, 2003-05-21 at 11:38, DJ Delorie wrote:
> 
> > At least that way someone would have *seen* that its broken and
> > hopefully would've applied your patch(or created a better one).
> 
> Someone did see the patch, and noted some problems with it.  *I*
> didn't see the patch because the subject didn't catch my attention.
> 
> http://gcc.gnu.org/ml/gcc-patches/2003-04/msg00738.html

As noted, I made the bad assumption that submitting the patch would
bring attention to the problem (and the workaround patch solved my
immediate issue).  I haven't had the opportunity to make the suggested
changes to the patch.

Oh well, should I now raise a PR on this (or did someone beat me to it)?

	Randy

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com

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

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: Kai Ruottu
- Re: 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: Peter Barada
- Re: failure building gcc-3.3 (broken libiberty/vsprintf.c or build?)
  - From: Randy Rude
- Re: 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

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