Re: possible mkoctfile bug on 4.2.0

[Marco Atzeri]

On 16/01/2017 15:43, John W. Eaton wrote:
> On 01/16/2017 08:36 AM, Marco Atzeri wrote:
> > On 16/01/2017 12:25, Marco Atzeri wrote:
> > > Trying to build control package with octave-4.2.0 on cygwin I noticed
> > > that the CXX setting seems to not be preserved:
> > >
> > > $ mkoctfile -p CXX
> > > g++ -std=gnu++11
> > >
> > > while "-std=gnu++11" seems disappear on invocation by Makefile
> >
> > Not a bug. mkoctfile propagates previous settings of CXX
> >
> >  $ CXX="g++" mkoctfile -p CXX
> > g++
> >
> >  $ mkoctfile -p CXX
> > g++ -std=gnu++11
>
> Are you saying that the Makefile in the control package sets CXX to
> something that leaves out the -std=gnu++11 option?  Maybe that option
> should be handled differently?  I don't know what the best solution is.
>
> jwe

Hi John,
I solved it as soon I noticed that mkoctfile honors the ambient value.
The build system was setting CXX, so removing the definition was fine.

May be "mkoctfile --help" should mention it ?


Thanks
Marco