Comment 27 for bug 1488079

(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.