development version does not compile
Bertrand Roessli
bertrand.roessli at psi.ch
Fri Feb 13 10:09:12 CST 2009
broessli at broessli-laptop:~$ gnuplot --version
gnuplot 4.2 patchlevel 4
broessli at broessli-laptop:~$
I do not think I have regexp installed
Source directory: .
Installation prefix: /usr/local
C compiler: gcc -mieee-fp -Wall -W -Wshadow -g -O2
C++ compiler: g++ -mieee-fp -Wall -W -Wshadow
-Wold-style-cast -g -O2
Fortran compiler: gfortran -O -mieee-fp
Fortran libraries: -L/usr/lib/gcc/i486-linux-gnu/4.3.2
-L/usr/lib/gcc/i486-linux-gnu/4.3.2/../../../../lib -L/lib/../lib
-L/usr/lib/../lib -L/usr/lib/gcc/i486-linux-gnu/4.3.2/../../.. -lz
-lgfortranbegin -lgfortran -lm
BLAS libraries: -llapack -lblas
FFTW libraries: -lfftw3 -lfftw3f
GLPK libraries: -lglpk
UMFPACK libraries: -lumfpack
AMD libraries: -lamd
CAMD libraries: -lcamd
COLAMD libraries: -lcolamd
CCOLAMD libraries: -lccolamd
CHOLMOD libraries: -lcholmod
CXSPARSE libraries: -lcxsparse
ARPACK libraries:
QRUPDATE libraries:
HDF5 libraries:
CURL libraries:
REGEX libraries:
QHULL libraries:
OPENGL libraries:
FLTK backend libs:
X11 include flags:
X11 libraries: -lX11
LIBS: -lreadline -lncurses -ldl -lblas -lz -lm
Default pager: less
gnuplot: gnuplot
Magick config:
On Fri, 2009-02-13 at 10:59 -0500, John W. Eaton wrote:
> On 13-Feb-2009, Bertrand Roessli wrote:
>
> | I had 4.2.3 and installed 4.2.4, but got the same error.
> | I commented out the lines in the m-file and everything compiled
> | smoothly.
>
> OK, so if you are using 4.2.4, then you should be seeing
>
> 4.2 patchlevel 4
>
> as the output from the shell command "gnuplot --version", correct?
>
> If so, then I think we've determined that the problem is that the PCRE
> library handles the regexp in __gnuplot_version__ correctly, but other
> regexp libraries do not.
>
> Do you have the PCRE regexp library installed? Did configure find it?
>
> Maybe we should change __gnuplot_version__ do the version extraction
> without regexp, to avoid this problem. Additionally, perhaps we
> should require PCRE for regexps, so that there is some consistency in
> the behavior of Octave's regexp functions.
>
> jwe
More information about the Help-octave
mailing list