[sr #110286] Make it possible to request a specific (non-latest) version of a language standard

Jörn Heusipp <[email protected]> Thu, 17 Oct 2024 02:47:48 -0400 (EDT)

Newsgroups	gmane.comp.sysutils.autoconf.bugs
Message-ID	<[email protected]>

Follow-up Comment #6, sr #110286 (group autoconf):

[comment #5 comment #5:]
> As far as I know the original bug (#110879, which led to the Ixion issue for
example) has been fixed in bleeding-edge Autoconf on Savannah.

Ah that's great. I did not monitor Autoconf commit history (as I would not
understand most things in there anyway).
Looks like
<https://git.savannah.gnu.org/cgit/autoconf.git/commit/?id=056518b94ecd487bcbefdb69046b3f52c4168222>
should solve #110879. Thank you for that.

> However, nobody has yet volunteered to implement the feature request "Make
it possible to request a specific version of a language standard". If you can
volunteer or find a volunteer, please do so.

Well, it's still somewhat questionable whether anything needs to be done at
all for C++. autoconf-archive ax_cxx_compile_stdcxx.m4 exists and has been
used for this since ages. I strongly suggest that, if anything would be
implemented, it should consider some kind of forward/backward compatibility
with ax_cxx_compile_stdcxx.m4.

The C situation is a little bit different and more convoluted with AC_PROG_CC,
AC_PROG_CC_STDC, and AC_PROG_CC_C99, as far as I can tell.

> I suppose we could generate a new Autoconf version now, to fix this bug in a
release, and implement the feature request later.

That sounds like a good idea, as the previous situation obviously has caused
some trouble for multiple projects.

_______________________________________________________

Reply to this item at:

<https://savannah.gnu.org/support/?110286>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/

signature.asc (application/pgp-signature, 228 B)