public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/102665] New: ELF-specific configure flags should be rejected on non-ELF platforms
Date: Sat, 09 Oct 2021 16:17:46 +0000 [thread overview]
Message-ID: <bug-102665-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102665
Bug ID: 102665
Summary: ELF-specific configure flags should be rejected on
non-ELF platforms
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Keywords: build
Severity: normal
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: egallager at gcc dot gnu.org
Target Milestone: ---
Specifically, --enable-gnu-unique-object and --enable-secureplt are
ELF-specific configure flags, and yet are accepted anyways by the top-level
configure script on non-ELF platforms with no complaint. The help string for
--enable-gnu-unique-object at least mentions that it's ELF-specific, but the
one for --enable-secureplt doesn't, so that's another thing that could be
updated.
next reply other threads:[~2021-10-09 16:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-09 16:17 egallager at gcc dot gnu.org [this message]
2021-10-09 16:19 ` [Bug other/102665] " egallager at gcc dot gnu.org
2021-10-17 20:16 ` [Bug bootstrap/102665] " egallager at gcc dot gnu.org
2022-05-24 14:51 ` egallager at gcc dot gnu.org
2022-05-24 16:17 ` egallager at gcc dot gnu.org
2022-05-24 16:35 ` iains at gcc dot gnu.org
2023-08-25 13:18 ` egallager at gcc dot gnu.org
2023-09-10 16:04 ` egallager 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-102665-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).