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: Randy Rude <randy dot rude at gdcanada dot com>
To: Peter Barada <pbarada at mail dot wm dot sps dot mot dot com>
Cc: peter at baradas dot org, gcc at gcc dot gnu dot org, crossgcc at sources dot redhat dot com
Date: 21 May 2003 10:55:38 -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>

On Wed, 2003-05-21 at 09:09, Peter Barada wrote:
> 
> >This looks familiar.  Try applying the hashtab.c portion of this patch:
> >http://gcc.gnu.org/ml/gcc-patches/2003-04/msg00726.html
> 
> Cool, I'll try it and see what happens.
> 
> I'm wondering why you didn't file a PR back in April against gcc-3.3
> that stated that m68k-elf won't build?  At least that way someone
> would have *seen* that its broken and hopefully would've applied your
> patch(or created a better one).  I'm also wondering how many newlib
> targets are affected by this bug?

I have to plead ignorance of the process.  I sent this patch to both you
and gcc-patches.  I assumed that would trigger someone into filing a
PR.  Apparently I assumed incorrectly?

	Randy

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: 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

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