From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6687 invoked by alias); 14 Sep 2012 23:57:22 -0000 Received: (qmail 6679 invoked by uid 22791); 14 Sep 2012 23:57:21 -0000 X-SWARE-Spam-Status: No, hits=-3.6 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; Fri, 14 Sep 2012 23:57:08 +0000 From: "baker at usgs dot gov" To: gcc-bugs@gcc.gnu.org Subject: [Bug other/54586] New: Help diagnosing error: Link tests are not allowed after GCC_NO_EXECUTABLES Date: Fri, 14 Sep 2012 23:57:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: other X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: baker at usgs dot gov X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 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: 2012-09/txt/msg01143.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54586 Bug #: 54586 Summary: Help diagnosing error: Link tests are not allowed after GCC_NO_EXECUTABLES Classification: Unclassified Product: gcc Version: 4.7.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: other AssignedTo: unassigned@gcc.gnu.org ReportedBy: baker@usgs.gov This is not a bug report, but a feature request. I have been struggling with building GCC cross compilers. When I unexpectedly encounter error: Link tests are not allowed after GCC_NO_EXECUTABLES, what I really need to do is find out which previous configure step broke and set gcc_no_link=yes. The "Link tests..." error is a consequence of the true error, which is not identified as having set gcc_no_link=yes. I have taken to hand editing configure files when this happens and inserting my own diagnostic output when either gcc_no_link=no or gcc_no_link=yes is executed, e.g., in libiberty/configure: # FIXME: Cleanup? if { { eval echo "\"\$as_me\":${as_lineno-$LINENO}: \"$ac_link\""; } >&5 (eval $ac_link) 2>&5 ac_status=$? $as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5 test $ac_status = 0; }; then : $as_echo "$as_me:${as_lineno-$LINENO}: ---> gcc_no_link=no" >&5 gcc_no_link=no else $as_echo "$as_me:${as_lineno-$LINENO}: ---> gcc_no_link=yes" >&5 gcc_no_link=yes fi It would be really useful if all GCC configure files would emit such a message, at least when setting gcc_no_link=yes. It would make it a lot easier to trouble shoot "Link tests..." errors.