<html><head></head><body><div class="gmail_quote">On May 30, 2017 10:09:14 AM GMT+02:00, Kristian Fiskerstrand <k_f@gentoo.org> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> <pre class="k9mail">On 05/30/2017 12:05 AM, Andreas K. Huettel wrote:<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> -- So all packages that a) use gcc-4 or gcc-5, and b) do not in the ebuild <br /> "manually" add something like -std=c++11 or -std=c++14 or -std=gnu14 will fail <br /> to *build*.<br /></blockquote><br />This isn't really different from [Qt 5.7 requirements] and is<br />fundamentally an upstream bug if not checked for during configure and<br />automake using e.g [ax_cxx_compile_stdcxx_11].<br /><br />References:<br />[Qt 5.7 requirements]<br /><a href="https://bugs.gentoo.org/589412">https://bugs.gentoo.org/589412</a><br /><br />[ax_cxx_compile_stdcxx_11]<br /><a href="https://www.gnu.org/software/autoconf-archive/ax_cxx_compile_stdcxx_11.html">https://www.gnu.org/software/autoconf-archive/ax_cxx_compile_stdcxx_11.html</a><br /></pre></blockquote></div><br clear="all">Well, even if it were "fixed" in all upstream packages, we'd still have to sprinkle -std=c++11 over all ebuilds. I'd rather do the inverse for things not future proof...<br> -- <br> Sent from my Android device with K-9 Mail. Please excuse my brevity.</body></html>