Re: C++11 now default?

[John W. Eaton]

On 02/23/2016 08:34 AM, Ben Abbott wrote:
> > On Feb 23, 2016, at 7:57 AM, Ben Abbott <address@hidden> wrote:
> >
> > > On Feb 22, 2016, at 7:48 PM, John W. Eaton <address@hidden> wrote:
> > >
> > > On 02/22/2016 04:15 PM, Mike Miller wrote:
> > > > On Mon, Feb 22, 2016 at 16:04:50 -0500, John W. Eaton wrote:
> > > > > I'm beginning to think we should make the c++11 test optional using
> > > > > something like --enable-c++11 and have it disabled by default.
> > > >
> > > > As long as this would not prevent it from being enabled by default with
> > > > gcc 6. With gcc 6, the options -std=gnu11 and -std=gnu++14 are enabled
> > > > by default. I would think Octave should not set or do anything to undo
> > > > that.
> > >
> > > Right, I was thinking of only adding these kinds of options if requested, but 
> > > not trying to disable them if they are the default behavior (without requiring 
> > > special options).
> > >
> > > But then we still have to figure out how to make Octave build properly for the 
> > > old and new standards.
> > >
> > > jwe
> >
> > After adding "-std=gnu++0x -std=gnu11 -std=gnu++14” to CXXFLAGS, I’m able to 
> > build.
> >
> > I'll experiment to see which of those did the trick.
> >
> > Ben
>
> Adding "-std=gnu11 -std=gnu++14” to CXXFLAGS is sufficient for me.

What are CC and CXX set to if you just run the configure script without 
setting any special value for them?

Also, what arguments are you passing to configure and what environment 
variables do you have set that might affect configure?

jwe