On Tuesday, 18 September 2018 16:31:23 CEST Guilherme Amadio wrote:
> On Mon, Sep 17, 2018 at 10:24:48AM -0700, Matt Turner wrote:
> > I don't understand what a potential solution would be.
> >
> > The various projects use -std=c++XXX because that's what their code
> > requires. -std=c++XXX can't
On Mon, Sep 17, 2018 at 10:24:48AM -0700, Matt Turner wrote:
> I don't understand what a potential solution would be.
>
> The various projects use -std=c++XXX because that's what their code
> requires. -std=c++XXX can't generally be changed. If a dependent
> project is incompatible that's no diffe
On Tue, Sep 18, 2018 at 08:46:46AM -0400, Richard Yao wrote:
>
> > On Sep 17, 2018, at 12:40 PM, Vadim A. Misbakh-Soloviov
> > wrote:
> >
> > I'd prefer to wait another replies on the list for the main theme of this e-
> > mail, but this problem also affects C (so, as **c**flags and C standards
> On Sep 17, 2018, at 12:40 PM, Vadim A. Misbakh-Soloviov
> wrote:
>
> I'd prefer to wait another replies on the list for the main theme of this e-
> mail, but this problem also affects C (so, as **c**flags and C standards), so
> solution shoudn't be c++ specific, imho.
You would think that,
On 9/17/18 at 5:24 PM user Matt Turner wrote:
> I don't understand what a potential solution would be.
>
> The various projects use -std=c++XXX because that's what their code
> requires. -std=c++XXX can't generally be changed. If a dependent
> project is incompatible that's no different than any o
I don't understand what a potential solution would be.
The various projects use -std=c++XXX because that's what their code
requires. -std=c++XXX can't generally be changed. If a dependent
project is incompatible that's no different than any other case of
incompatible dependencies in Gentoo.
I thi
I'd prefer to wait another replies on the list for the main theme of this e-
mail, but this problem also affects C (so, as **c**flags and C standards), so
solution shoudn't be c++ specific, imho.
