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: Peter Barada <peter at baradas dot org>
To: pbarada at mail dot wm dot sps dot mot dot com
Cc: randy dot rude at gdcanada dot com, kai dot ruottu at luukku dot com, gcc at gcc dot gnu dot org,crossgcc at sources dot redhat dot com
Date: Wed, 21 May 2003 23:07:56 -0400 (EDT)
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>

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

That worked, but I still get the ubiquitous failure rgarding div_t
undeclared.  See:

http://gcc.gnu.org/ml/gcc/2003-04/msg01321.html
http://gcc.gnu.org/ml/gcc/2002-06/msg01602.html

For more information on this well-observed failure.  If I remove
obj/gcc/include/stdlib.h and stat up the build, gcc-3.3 completes.

Has anyone else seen this for other cross targets, and does *anyone*
have an idea how to best get past this?

Thanx in advance!

-- 
Peter Barada
peter@baradas.org

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

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]