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: kai dot ruottu at luukku dot com
Cc: pbarada at mail dot wm dot sps dot mot dot com, randy dot rude at gdcanada dot com,gcc at gcc dot gnu dot org, crossgcc at sources dot redhat dot com
Date: Thu, 22 May 2003 09:27:17 -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> <20030522030756.AB20298B6D@baradas.org> <3ECCB76D.5060409@luukku.com>

>> Has anyone else seen this for other cross targets, and does *anyone*
>> have an idea how to best get past this?
>
>  Maybe we should bomb the GCC-developers with bug reports about the
>misuse of the '$prefix/$target/sys-include' now...  During the last
>years I have now and then try to report this, but with no response
>at all...
>
>  The current workaround I now use is to symlink all those checked
>headers: 'stdlib.h', 'unistd.h', 'string.h' and 'limits.h' into
>'$prefix/$target/sys-include' from '$prefix/$target/include', so
>that they will not be replaced with stubs during the GCC-build.

Is that after you build/install newlib?  I looked after building
bootstrap, and $prefix/include is empty, and
$prefix/$target/sys-include doesn't contain any header files.

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

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

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