Re: [Patch] configure: Also check C++11 (flags) for ${build} compiler not only for ${host}

On Thu, 20 Aug 2020, Tobias Burnus wrote: > Thanks for the first review; new version attached. Thanks, this version is OK for GCC (but the GCC version will need updating if autoconf-archive ends up with a different version of these changes). -- Joseph S. Myers jos...@codesourcery.com

Re: [Patch] configure: Also check C++11 (flags) for ${build} compiler not only for ${host}

On 8/20/20 7:12 PM, Joseph Myers wrote: It appears you're requiring _FOR_BUILD here and considering other suffixes invalid, which would prevent any other use, e.g. _FOR_TARGET. Actually, the main reason I required _FOR_BUILD was that I couldn't find m4_ifnblank and then gave up ... Now having

Re: [Patch] configure: Also check C++11 (flags) for ${build} compiler not only for ${host}

On Thu, 13 Aug 2020, Tobias Burnus wrote: > diff --git a/config/ax_cxx_compile_stdcxx.m4 b/config/ax_cxx_compile_stdcxx.m4 > index 9413da624d2..0cd515fc65b 100644 > --- a/config/ax_cxx_compile_stdcxx.m4 > +++ b/config/ax_cxx_compile_stdcxx.m4 > @@ -25,6 +25,10 @@ > # regardless, after defining

[Patch] configure: Also check C++11 (flags) for ${build} compiler not only for ${host}

Here, the ${host} compiler was newer, supporting C++11 by default while the ${build} compiler required -std=c++11. Hence, the build failed. OK? Tobias - Mentor Graphics (Deutschland) GmbH, Arnulfstraße 201, 80634 München / Germany Registergericht München HRB 106955,