Skip to content

Require and select a working C++17 mode in Autoconf builds - #265

Merged
zayenz merged 1 commit into
mainfrom
feature/6.5.0-autoconf-cxx17
Oct 22, 2026
Merged

zayenz merged 1 commit into
mainfrom
feature/6.5.0-autoconf-cxx17

Conversation

@zayenz

@zayenz zayenz commented Oct 22, 2026

Copy link
Copy Markdown
Member

Autoconf previously checked obsolete compiler minimum versions and treated the C++17 flag as optional. Replace those checks with a required compile probe for C++17 language and standard-library support.

Keep a capable default or user-selected newer standard. Otherwise, select C++17 using the compiler's appropriate flag; report a clear configure error if neither mode works. Keep the C++ standard flag out of CFLAGS. Regenerate configure with the repository's Autoconf 2.72 tooling.

Validation with Apple Clang: an initial C++14 selection gains C++17, an explicit C++20 selection is preserved, and a compiler shim restricted to C++14 is rejected with the expected diagnostic. Source tidiness and generated-source freshness checks passed. Native MSVC validation was not available locally.

@zayenz
zayenz merged commit bdcef33 into main Oct 22, 2026
16 checks passed
@zayenz
zayenz deleted the feature/6.5.0-autoconf-cxx17 branch October 22, 2026 12:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant