From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 1387E388A02B; Tue, 24 May 2022 16:35:34 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 1387E388A02B From: "iains at gcc dot 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: bootstrap X-Bugzilla-Version: 12.0 X-Bugzilla-Keywords: build, diagnostic X-Bugzilla-Severity: normal X-Bugzilla-Who: iains at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: egallager at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 May 2022 16:35:34 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D102665 --- Comment #5 from Iain Sandoe --- (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 havi= ng to manipulate many such options but, rather, that if we reach that situatio= n, 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=20 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 co= uld, 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.=