public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug other/54586] New: Help diagnosing error: Link tests are not allowed after GCC_NO_EXECUTABLES
@ 2012-09-14 23:57 baker at usgs dot gov
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
0 siblings, 2 replies; 3+ messages in thread
From: baker at usgs dot gov @ 2012-09-14 23:57 UTC (permalink / raw)
To: gcc-bugs
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug bootstrap/54586] Help diagnosing error: Link tests are not allowed after GCC_NO_EXECUTABLES
2012-09-14 23:57 [Bug other/54586] New: Help diagnosing error: Link tests are not allowed after GCC_NO_EXECUTABLES baker at usgs dot gov
@ 2021-12-30 10:50 ` redi at gcc dot gnu.org
2021-12-30 10:52 ` redi at gcc dot gnu.org
1 sibling, 0 replies; 3+ messages in thread
From: redi at gcc dot gnu.org @ 2021-12-30 10:50 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54586
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Last reconfirmed| |2021-12-30
Status|UNCONFIRMED |NEW
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Confirmed.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug bootstrap/54586] Help diagnosing error: Link tests are not allowed after GCC_NO_EXECUTABLES
2012-09-14 23:57 [Bug other/54586] New: Help diagnosing error: Link tests are not allowed after GCC_NO_EXECUTABLES baker at usgs dot gov
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
1 sibling, 0 replies; 3+ messages in thread
From: redi at gcc dot gnu.org @ 2021-12-30 10:52 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54586
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
The difficulty is that every case where configure sets gcc_no_link is generated
from the same file: ../config/no-executables.m4
So adding something in there doesn't actually give you any context.
Each configure.ac (or .m4 file it uses) needs to add some context when using
the GCC_NO_EXECUTABLES macro.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2021-12-30 10:52 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-09-14 23:57 [Bug other/54586] New: Help diagnosing error: Link tests are not allowed after GCC_NO_EXECUTABLES baker at usgs dot gov
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
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).