public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dimitar at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libquadmath/111928] New: Build broken for baremetal targets after r14-4825-g6a6d3817afa02b Date: Mon, 23 Oct 2023 07:34:48 +0000 [thread overview] Message-ID: <bug-111928-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111928 Bug ID: 111928 Summary: Build broken for baremetal targets after r14-4825-g6a6d3817afa02b Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libquadmath Assignee: unassigned at gcc dot gnu.org Reporter: dimitar at gcc dot gnu.org Target Milestone: --- Following configure error is observed for pru-unknown-elf, arm-none-eabi, and probably other baremetal targets: Checking multilib configuration for libquadmath... mkdir -p -- pru/libquadmath Configuring in pru/libquadmath .... checking for cos in -lm... configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES. make[1]: *** [Makefile:13877: configure-target-libquadmath] Error 1 Issue probably started with r14-4825-g6a6d3817afa02b
next reply other threads:[~2023-10-23 7:34 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-23 7:34 dimitar at gcc dot gnu.org [this message] 2023-10-23 9:34 ` [Bug libquadmath/111928] [14 Regression] " rguenth at gcc dot gnu.org 2023-10-23 10:37 ` iains at gcc dot gnu.org 2023-10-23 10:59 ` dimitar at gcc dot gnu.org 2023-10-23 11:01 ` iains at gcc dot gnu.org 2023-10-23 11:03 ` dimitar at gcc dot gnu.org 2023-10-23 11:04 ` dimitar at gcc dot gnu.org 2023-10-23 11:06 ` iains at gcc dot gnu.org 2023-10-23 13:14 ` cvs-commit at gcc dot gnu.org 2023-10-23 13:20 ` iains at gcc dot gnu.org 2023-10-24 5:56 ` dimitar 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-111928-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: linkBe 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).