public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "baker at usgs dot gov" <gcc-bugzilla@gcc.gnu.org>
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	[thread overview]
Message-ID: <bug-54586-4@http.gcc.gnu.org/bugzilla/> (raw)

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.


             reply	other threads:[~2012-09-14 23:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-14 23:57 baker at usgs dot gov [this message]
2021-12-30 10:50 ` [Bug bootstrap/54586] " redi at gcc dot gnu.org
2021-12-30 10:52 ` redi at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-54586-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).