public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libquadmath/112963] [14 Regression] Incorrect linking of libquadmath since r14-4863
Date: Mon, 11 Dec 2023 16:40:09 +0000 [thread overview]
Message-ID: <bug-112963-4-PrksvWzSJ5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112963-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112963
--- Comment #11 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #10)
> BTW, yet another option would be to just
> LIBM=
> case $host in
> *-*-beos* | *-*-cegcc* | *-*-cygwin* | *-*-haiku* | *-*-pw32* | *-*-darwin*)
> # These system don't have libm, or don't need it
> ;;
> *)
> LIBM=-lm
> ;;
> esac
> AC_SUBST([LIBM])
> i.e. copy&paste libtool AC_CHECK_LIBM without that AC_CHECK_LIB part (and
> without *-ncr-sysv* entry which we don't support in GCC AFAIK), so something
> in between using -lm unconditionally and not using it on targets which don't
> really need it.
yes that seems a better solution - I was about to write:
Seeing your comment #7, I think that the bare metal is a red herring (it just
happened to be the reporter) - actually the issue is the unconditional
GCC_NO_EXECUTABLES, which means that the macro would fail for any build != host
case.
I suppose also that means that build != host == target for mingw or other
targets that do not use '-lm' will also be wrong - so a proper fix is needed
sometime.
next prev parent reply other threads:[~2023-12-11 16:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 15:23 [Bug libquadmath/112963] New: " jakub at gcc dot gnu.org
2023-12-11 15:23 ` [Bug libquadmath/112963] " jakub at gcc dot gnu.org
2023-12-11 15:43 ` schwab@linux-m68k.org
2023-12-11 15:44 ` iains at gcc dot gnu.org
2023-12-11 15:46 ` iains at gcc dot gnu.org
2023-12-11 15:53 ` pinskia at gcc dot gnu.org
2023-12-11 15:59 ` jakub at gcc dot gnu.org
2023-12-11 16:05 ` iains at gcc dot gnu.org
2023-12-11 16:19 ` jakub at gcc dot gnu.org
2023-12-11 16:27 ` iains at gcc dot gnu.org
2023-12-11 16:31 ` jakub at gcc dot gnu.org
2023-12-11 16:35 ` jakub at gcc dot gnu.org
2023-12-11 16:40 ` iains at gcc dot gnu.org [this message]
2023-12-11 22:48 ` iains at gcc dot gnu.org
2023-12-11 22:50 ` jakub at gcc dot gnu.org
2023-12-12 8:07 ` cvs-commit at gcc dot gnu.org
2023-12-12 8:10 ` jakub 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-112963-4-PrksvWzSJ5@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).