| 1 |
On 12/02/2015 08:38 AM, Anthony G. Basile wrote: |
| 2 |
> On 12/2/15 2:06 AM, Michał Górny wrote: |
| 3 |
>> So you're saying we should write a whole eclass to do: |
| 4 |
>> |
| 5 |
>> append-cppflags -std=c++11 |
| 6 |
>> |
| 7 |
>> ? |
| 8 |
>> |
| 9 |
> I think you mean append-cxxflags. Anyhow, I had an off list discussion |
| 10 |
> with David Klaftenegger about the semantic difference between c++11 and |
| 11 |
> 98 with respect to their atomics and I'm convinced that a global |
| 12 |
> -std=c++11 could get us into trouble on packages that make use of |
| 13 |
> threading. So drop my idea of global c++11 and you'll have to catch |
| 14 |
> these on a per package basis. |
| 15 |
> |
| 16 |
Could we use something along the lines of a use_expand'ed variable? |
| 17 |
|
| 18 |
CXX_ABI="03" |
| 19 |
|
| 20 |
==> DEPEND="dev-libs/boost[cxx_abi_03]" |
| 21 |
|
| 22 |
Would need some CFLAGS injection, but like this any C++ packages can be |
| 23 |
forced to 'same' ABI in a more reasonable fashion, and it wouldn't |
| 24 |
require global overrides. |
Archives