Hi , was anyone seen the following issue ? After an update from autoconf 2.71 to 2.72 on macOS (x86_6$9 , the C++ flag detection changed in an unexpected way . It is an OpenJDK11 build .
Previously with (autoconf 2.71) we had : checking for /jenkins/workspace/devkit-xcode-13.1/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang++ option to enable C++11 features... none needed now (2.72) checking for /jenkins/workspace/devkit-xcode-13.1/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang++ option to enable C++11 features... -std=gnu++11 the new option -std=gnu++11 leads to : error: C++11 was disabled in PCH file but is currently enabled Should we simply disable PCH ? Or is there a good and reliable way to get rid of the unwanted option ? Thanks, Matthias
