From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10628 invoked by alias); 3 Jan 2011 16:12:10 -0000 Received: (qmail 10617 invoked by uid 22791); 3 Jan 2011 16:12:09 -0000 X-SWARE-Spam-Status: No, hits=-2.9 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 03 Jan 2011 16:12:06 +0000 From: "joseph at codesourcery dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/47145] [4.6 Regression] cross-compilation fails with "cannot check for file existence when cross compiling" X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: joseph at codesourcery dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 4.6.0 X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Date: Mon, 03 Jan 2011 16:12:00 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2011-01/txt/msg00148.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47145 --- Comment #6 from joseph at codesourcery dot com 2011-01-03 16:11:45 UTC --- On Mon, 3 Jan 2011, ktietz at gcc dot gnu.org wrote: > The issue here is AC_CHECK_FILE, which is documented to not work for > cross-compiling scenario. By replacing this to test -f, it should working for > native and cross-compile. There were also comments that the path is sometimes wrong. Using test -f should fix the immediate regression - but it would be better not to hardcode paths at all. Presumably the issue is that some particular stylesheets are needed *in the path searched by the tools being tested for*, which may depend on how those tools were configured and may not be in /usr at all. So it would be better to have a feature test - run the tools (if found) on a suitable document to see if they can find the required stylesheets. Perhaps the libstdc++ maintainers could comment on what the actual feature required is for which a path test is being used as a bad proxy?