Re: Compile error in latest repository tip

[Daniel J Sebald]

On 03/03/2016 03:22 PM, Mike Miller wrote:
> On Thu, Mar 03, 2016 at 15:05:50 -0600, Daniel J Sebald wrote:
> > That option apparently fails:
> >
> > configure:6623: gcc -std=gnu11 -c -g -O2  conftest.c>&5
> > cc1: error: unrecognized command line option "-std=gnu11"
> > configure:6623: $? = 1
> > configure: failed program was:
> > | /* confdefs.h */
> > | #define PACKAGE_NAME "GNU Octave"
> > | #define PACKAGE_TARNAME "octave"
> > | #define PACKAGE_VERSION "4.1.0+"
> > | #define PACKAGE_STRING "GNU Octave 4.1.0+"
> > | #define PACKAGE_BUGREPORT "http://octave.org/bugs.html";
>
> There are a few sets of options that are tried, some of them will fail.
>
> Anyway, I remember now that when I build with gcc 4.4 the test does fail
> so I have to build with CXX="g++ -std=gnu++0x". Try setting that in your
> environment or on the configure command line and see if you can build
> (you may run into bug #47212).

That configuration option seems to make compilation proceed, thanks. 
Would it be possible to make "gnu++0x" be assigned to -std as part of 
the configure process?  -std=gnu11 is being tested, so if that fails it 
shouldn't be difficult to test if -std=gnu++0x fails as a fallback.

I don't get an error for Faddeeva, but a warning:

  F77    liboctave/cruft/dassl/liboctave_cruft_libcruft_la-ddawts.lo
  CXX    liboctave/cruft/Faddeeva/liboctave_cruft_libcruft_la-Faddeeva.lo
/home/sebald/octave/octave/octave/liboctave/cruft/Faddeeva/Faddeeva.cc: 
In function 'cmplx Faddeeva::w(cmplx, double)':
/home/sebald/octave/octave/octave/liboctave/cruft/Faddeeva/Faddeeva.cc:690:17: 
warning: use of old-style cast
/home/sebald/octave/octave/octave/liboctave/cruft/Faddeeva/Faddeeva.cc:691:14: 
warning: use of old-style cast
/home/sebald/octave/octave/octave/liboctave/cruft/Faddeeva/Faddeeva.cc:828:19: 
warning: use of old-style cast
  F77    liboctave/cruft/fftpack/liboctave_cruft_libcruft_la-cfftb.lo

Documentation fails due to improper generation of images (I typically 
disable documentation), but the executable runs.

Dan