From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30136 invoked by alias); 22 May 2003 13:27:21 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 30075 invoked from network); 22 May 2003 13:27:20 -0000 Received: from unknown (HELO baradas.org) (66.166.225.55) by sources.redhat.com with SMTP; 22 May 2003 13:27:20 -0000 Received: by baradas.org (Postfix, from userid 500) id E6CA898982; Thu, 22 May 2003 09:27:17 -0400 (EDT) From: Peter Barada To: kai.ruottu@luukku.com Cc: pbarada@mail.wm.sps.mot.com, randy.rude@gdcanada.com, gcc@gcc.gnu.org, crossgcc@sources.redhat.com In-reply-to: <3ECCB76D.5060409@luukku.com> (message from Kai Ruottu on Thu, 22 May 2003 14:41:33 +0300) 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> Message-Id: <20030522132717.E6CA898982@baradas.org> Date: Thu, 22 May 2003 13:33:00 -0000 X-SW-Source: 2003-05/txt/msg02004.txt.bz2 >> 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