From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5623 invoked by alias); 25 May 2012 14:00:09 -0000 Received: (qmail 5598 invoked by uid 22791); 25 May 2012 14:00:07 -0000 X-SWARE-Spam-Status: No, hits=-4.5 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,KHOP_RCVD_TRUST,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail-pb0-f47.google.com (HELO mail-pb0-f47.google.com) (209.85.160.47) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 25 May 2012 13:59:54 +0000 Received: by pbbrq2 with SMTP id rq2so1738743pbb.20 for ; Fri, 25 May 2012 06:59:54 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-type:x-gm-message-state; bh=l399LtobxnHXmuZLsQb778QYWb8Q9l5IjJp81hUaBBQ=; b=BurTu+a0o+5b+pqHLiejEBgVaxHY7o3n4N9UTPaYf4ODjh5vn0Uv3Px6aVUMGirsUx L05H5mqmc40LBvOAIHqgy6xqNuVUGzlkl2r9n9fHnvrx2Buy88SJMXF6hi4Z1oTcHiZR PIaCbwOWvUpQqytUsF22qWTpUfiYt26+rLx9thleTVUrFIHwGyhbPQllAcO1K+9fE506 0ZnRlZ8SHqxSmL4ZDZjTPIn9AS5WnlEAKmm/9QRQZ9i5gWFPRFqup1JNDqCtJwTXwJTU By4E8gFL/fFoDpVRRkd8NxNrkO3QbaNW9nQMafcNNwJ8+rvV39usJeKOTIpv0Z3GsF22 /nQg== Received: by 10.68.132.166 with SMTP id ov6mr33689159pbb.24.1337954394397; Fri, 25 May 2012 06:59:54 -0700 (PDT) Received: by 10.68.132.166 with SMTP id ov6mr33689116pbb.24.1337954394148; Fri, 25 May 2012 06:59:54 -0700 (PDT) Received: from coign.google.com ([65.50.217.182]) by mx.google.com with ESMTPS id x1sm9138180pbp.50.2012.05.25.06.59.53 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 25 May 2012 06:59:53 -0700 (PDT) From: Ian Lance Taylor To: rbmj Cc: gcc-help@gcc.gnu.org Subject: Re: Why is fixincludes not doing anything? (was: Re: Fixincludes permanence & questions on cross compilers) References: <4FBD15EB.6090105@verizon.net> <4FBD266F.7080807@verizon.net> <4FBF762C.4020604@verizon.net> Date: Fri, 25 May 2012 14:00:00 -0000 In-Reply-To: <4FBF762C.4020604@verizon.net> (rbmj@verizon.net's message of "Fri, 25 May 2012 08:08:12 -0400") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Gm-Message-State: ALoCoQllejnAbRVz/Jwui7tRMo+UEz67o1GIpcuRc2w6RqYu7r1Uox1y8dlS4pdTm4OzvEZ6WJ0FZGKYIjnr+HqrNnDq8e+BZHmHQZOYzKBuxk5XykSVCwfXru59QGwKlivhOg725kGw1HC1mC7WqUfRuDurcecMakFjqo/2r3GgiFNogy+KlAc= 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/msg00203.txt.bz2 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? Ian