From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21652 invoked by alias); 25 May 2012 14:24:16 -0000 Received: (qmail 21643 invoked by uid 22791); 25 May 2012 14:24:14 -0000 X-SWARE-Spam-Status: No, hits=1.8 required=5.0 tests=AWL,BAYES_00,BOTNET,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_NO,RCVD_IN_HOSTKARMA_YE,TW_XG,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from vms173015pub.verizon.net (HELO vms173015pub.verizon.net) (206.46.173.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 25 May 2012 14:24:02 +0000 Received: from [10.97.38.128] ([unknown] [151.188.105.156]) by vms173015.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0M4L00D851BIZVP2@vms173015.mailsrvcs.net> for gcc-help@gcc.gnu.org; Fri, 25 May 2012 09:23:43 -0500 (CDT) Message-id: <4FBF95EE.4020401@verizon.net> Date: Fri, 25 May 2012 14:24:00 -0000 From: rbmj User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120329 Thunderbird/11.0.1 MIME-version: 1.0 To: gcc-help@gcc.gnu.org Subject: Re: Why is fixincludes not doing anything? References: <4FBD15EB.6090105@verizon.net> <4FBD266F.7080807@verizon.net> <4FBF762C.4020604@verizon.net> In-reply-to: Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org X-SW-Source: 2012-05/txt/msg00206.txt.bz2 On 05/25/2012 09:59 AM, Ian Lance Taylor wrote: > rbmj writes: > >> Refine my question: anyone know why fixincludes does not appear to be >> doing *anything*? I can't seem to find any fixed headers anywhere in >> GCC's build tree. And the compile keeps failing... > In your specific case, I don't know. But it is possible for a target to > disable fixincludes by setting STMP_FIXINC in a config/CPU/t-XXX file. > Or, since this is a cross-compiler, GCC may simply be confused about > where to find the header files that it is supposed to fix. Normally > those header files will be found in the directory printed by gcc > -print-sysroot-headers-suffix. What does that print for you? Did you > configure GCC with the right --with-sysroot option? Maybe that's the error: ./gcc/xgcc -print-sysroot-headers-suffix xgcc: fatal error: not configured with sysroot headers suffix xgcc is the compiler in question right? . is the build directory. I believe xgcc is the compiler that compiles all of the cross targets (lib*). My configure call was: ../gcc-4.7.0/configure --prefix=/usr --target=powerpc-wrs-vxworks --with-gnu-as --with-gnu-ld --with-headers=../gccdist/WindRiver/vxworks-6.3/target/h --disable-shared --disable-libssp --disable-multilib --with-float=hard --enable-languages=c,c++ --enable-threads=vxworks --without-gconv --disable-libgomp --disable-nls --disable-libmudflap --with-cpu-PPC603 I don't use --with-sysroot; I use --with-headers. So do I need to use a different configuration? And how can I achieve the same effect using --with-sysroot as I did with --with-headers if that *is* the issue. Thanks! Robert Mason