URL: <https://savannah.gnu.org/support/?111399>
Summary: Smarter compiler version check
Group: Autoconf
Submitter: None
Submitted: Tue 31 Mar 2026 12:44:50 AM UTC
Priority: 5 - Unprioritized
Severity: 3 - Normal
Status: None
Privacy: Public
Assigned to: None
Originator Email:
Open/Closed: Open
Discussion Lock: Unlocked
Operating System: None
_______________________________________________________
Follow-up Comments:
-------------------------------------------------------
Date: Tue 31 Mar 2026 12:44:50 AM UTC By: Anonymous
Be it as it may that was actually the best way to check if a compiler exists
at all, how it is
[https://gitweb.git.savannah.gnu.org/gitweb/?p=autoconf.git;a=blob;f=lib/autoconf/c.m4;h=4771b2c991e5ef78f9ed6116ffe54e92c9e7eec5;hb=HEAD#l497
done now] is pretty rough.
The configure script has to call it over and over again even if it has already
previously been successful, and it is granted to cause errors in the log file.
As you can see for example
[https://superuser.com/questions/846768/gcc-unrecognized-command-line-options-v-and-qversion-with-autoconf
here], it creates a lot of confusion to users that are trying to diagnose a
failure for their first time and take a red herring.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/support/?111399>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
