1 |
On Tuesday, 18 September 2018 16:31:23 CEST Guilherme Amadio wrote: |
2 |
> On Mon, Sep 17, 2018 at 10:24:48AM -0700, Matt Turner wrote: |
3 |
> > I don't understand what a potential solution would be. |
4 |
> > |
5 |
> > The various projects use -std=c++XXX because that's what their code |
6 |
> > requires. -std=c++XXX can't generally be changed. If a dependent |
7 |
> > project is incompatible that's no different than any other case of |
8 |
> > incompatible dependencies in Gentoo. |
9 |
> > |
10 |
> > I think -std=c++XXX discussions before happened because gcc changed |
11 |
> > the C++ ABI with -std=c++11. I don't think that's particularly |
12 |
> > relevant here, since as far as I know different -std=c++XXX values |
13 |
> > don't change the ABI with current gcc. |
14 |
> > |
15 |
> > So I guess my understanding is that there isn't a problem different |
16 |
> > than existing incompatible dependencies, but maybe I have |
17 |
> > misunderstood you. |
18 |
> |
19 |
> My concern is with, say, package foo that depends on both bar and baz, |
20 |
> and bar and baz support from C++11 to C++17, but must be compiled with |
21 |
> the same version of the standard so that foo can link against both of |
22 |
> them without having a broken ABI. I think that depending on bar[c++14], |
23 |
> or having a similar mechanism to Python to handle "same version of the |
24 |
> standard" with ${CXXSTD_REQUIRED_USE} or similar in an eclass would be |
25 |
> nice. |
26 |
|
27 |
Maybe add a CXXABI USE_EXPAND variable and then handle this case similar to |
28 |
python-single-r1.eclass packages with CXXABI_COMPAT and CXXABI_USEDEP? |