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 bootstrap/102665] ELF-specific configure flags should be rejected on non-ELF platforms
Date: Tue, 24 May 2022 16:35:34 +0000	[thread overview]
Message-ID: <bug-102665-4-wgQXi8NDPw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102665-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102665

--- Comment #5 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Eric Gallager from comment #4)
> Hm, looking in gcc/configure.ac (where these are defined), it looks like
> there's a bunch of other flags that this bug could apply to, too...

Note that I would try to clarify:

It is my understanding that the purpose of configure is to isolate the end user
from having to know about all the nasty little nooks and crannies of their
target.  As such it is not a "maintainer preference" to avoid end user having
to manipulate many such options but, rather, that if we reach that situation,
then the configure script is not doing its job and needs work.

As far as I understand things the right behaviour of configure is to choose a 
correct default value for each option based on the target.  The way that the
options work it is usually possible to ignore one for a specific target if it
does not apply at all.

Therefore:

1. making sure defaults are correct is valuable

2. perhaps just ignoring ELF-specific options (for Darwin)is useful (you could,
even diagnose that the option has been ignored if the user attempts to set it).

3. As you have noted, there are quite likely more options that
could/should/maybe already are ignored for Darwin.

  parent reply	other threads:[~2022-05-24 16:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-09 16:17 [Bug other/102665] New: " egallager at gcc dot gnu.org
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 [this message]
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-wgQXi8NDPw@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).