>From https://gcc.gnu.org/onlinedocs/gcc-11.2.0/gcc/C-Dialect-Options.html, gnu++2a equals gnu++2a, so it's fine to change the default o gnu++2a.
On Mon, Oct 2, 2023 at 6:43 AM Nathan Hartman <hartman.nat...@gmail.com> wrote: > Hi all, > > Commit d6453cfc3cd4771a5221528cab3056660be4b1e3 (PR # 8244) changes > the default CXX_STANDARD for libxx to gnu++20 to make llvm libcxx > 15.0.7 happy. > > Unfortunately this makes GCC versions < 10.3 fail with something like: > > arm-none-eabi-g++: error: unrecognized command line option > '-std=gnu++20'; did you mean '-std=gnu++2a'? > > And (as you can see in the PR discussions) on some host OSes > (including mine) it isn't convenient to install a newer GCC. > > In commit 4e93f93f303a85e04bdd7e4da22df028c0f76de3, the documentation > is updated to tell us that we need to update GCC to 10.3. > > The ---help--- for Kconfig CXX_STANDARD lists possible values: > gnu++98/c++98, gnu++11/c++11, gnu++14/c++14, gnu++17/c++17 and > gnu++20/c++20. Is it possible to add gnu++2a to that list, so that > people with old(er) host OSes (like me) can continue? > > Thanks, > Nathan >
