I have a system running amd64 stable and using gcc 4.6.4 as the default compiler for compatibility with some older custom packages (still available in stable portage); it also has 4.9.3 installed for packages that require it. On this system, dev-libs/icu-57.1 fails to configure: checking if we have a C++ compiler... no configure: error: C++ compiler x86_64-pc-linux-gnu-g++ does not work or no compiler found !!! Please attach the following file when seeking support: !!! /var/tmp/portage/dev-libs/icu-57.1/work/icu/source-abi_x86_64.amd64/config.log * ERROR: dev-libs/icu-57.1::gentoo failed (configure phase): * econf failed Relevant bit from config.log: configure:5868: checking if we have a C++ compiler configure:5881: x86_64-pc-linux-gnu-g++ -c -O2 -pipe -march=native -mtune=native -mno-fma4 -mno-fma -std=c++11 conftest.cpp >&5 cc1plus: error: unrecognized command line option '-std=c++11' configure:5881: $? = 1 I can obviously work around this by adding an env entry for this package, but normally packages will test for the presence of a C++11 compiler in the pretend phase. If going forward, a C++11 compiler is required to be the system default, then I can probably work with that, but it should likely be documented somewhere (perhaps in a news item).
It seems rather silly to add a pkg_pretend check to every package that needs c++11. This is becoming quite common. If this were my package, this would be a WONTFIX.
(In reply to Mike Gilbert from comment #1) > It seems rather silly to add a pkg_pretend check to every package that needs > c++11. This is becoming quite common. > > If this were my package, this would be a WONTFIX. Ack. Especially since new boost also requires c++11.
