| 1 |
On May 30, 2017 10:09:14 AM GMT+02:00, Kristian Fiskerstrand <k_f@g.o> wrote: |
| 2 |
>On 05/30/2017 12:05 AM, Andreas K. Huettel wrote: |
| 3 |
>> -- So all packages that a) use gcc-4 or gcc-5, and b) do not in the |
| 4 |
>ebuild |
| 5 |
>> "manually" add something like -std=c++11 or -std=c++14 or -std=gnu14 |
| 6 |
>will fail |
| 7 |
>> to *build*. |
| 8 |
> |
| 9 |
>This isn't really different from [Qt 5.7 requirements] and is |
| 10 |
>fundamentally an upstream bug if not checked for during configure and |
| 11 |
>automake using e.g [ax_cxx_compile_stdcxx_11]. |
| 12 |
> |
| 13 |
>References: |
| 14 |
>[Qt 5.7 requirements] |
| 15 |
>https://bugs.gentoo.org/589412 |
| 16 |
> |
| 17 |
>[ax_cxx_compile_stdcxx_11] |
| 18 |
>https://www.gnu.org/software/autoconf-archive/ax_cxx_compile_stdcxx_11.html |
| 19 |
> |
| 20 |
>-- |
| 21 |
>Kristian Fiskerstrand |
| 22 |
>OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net |
| 23 |
>fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3 |
| 24 |
|
| 25 |
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... |
| 26 |
-- |
| 27 |
Sent from my Android device with K-9 Mail. Please excuse my brevity. |
Archives