Comment 31 for bug 1488079

(In reply to Bernardo Costa from comment #18)
> (In reply to Vincent Le Ligeour from comment #15)
> > (In reply to Martin von Gagern from comment #11)
> >
> > Works for me on ~amd64
>
> Also works here, also ~amd64.
>
> Shouldn't the ebuild be modified to include the -std in some way? I realize
> it could be a hard choice between c++11 or gnu++11, but (if possible) the
> ebuild could warn if no "env" is found for setting an appropriate std, and
> force the user to make the choice, rather than failing with a 10000+ line
> error log.

No, it is the build system's task to request a compiler with {c,gnu}++11 features and enable them by adding the appropriate -std= flags. The user should not be required to include -std= in their global CXXFLAGS, which might wreck havoc with packages implicitly relying on being compiled in C++98 mode.