Changes in configure for Octave 4.0.1?

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

Changes in configure for Octave 4.0.1?

José Luis García Pallero
Hello:

I've tried to compile the last Octave 4.0.1 sources and I've obtained
some errors in the configure step. I use Debian Sid.

First of all, the shared Lapack library from the repositories
apparently doesn't work. I obtain the error

checking for cheev_... no
checking for cheev_ in -llapack... no
checking for cheev_ in -llapack_rs6k... no
configure: error: BLAS and LAPACK libraries are required

so I need to configure with the option
--with-lapack=/usr/lib/liblapack.a, i.e., with the static library (I
obtain the same error with --with-lapack=/usr/lib/liblapack.so)

I obtain also

configure: WARNING: qrupdate not found.  The QR & Cholesky updating
functions will be slow.
configure: WARNING: CHOLMOD library not found.  This will result in
some lack of functionality for sparse matrices.
configure: WARNING: UMFPACK not found.  This will result in some lack
of functionality for sparse matrices.
configure: WARNING: ARPACK not found.  The eigs function will be disabled.

but all these libraries are inatalled from the Debian repositories in
/usr/lib/x86_64-linux-gnu/ instead of /usr/lib/. I didn't remember my
last Octave building, but I though it runs

Thanks

--
*****************************************
José Luis García Pallero
[hidden email]
(o<
/ / \
V_/_
Use Debian GNU/Linux and enjoy!
*****************************************

Reply | Threaded
Open this post in threaded view
|

Re: Changes in configure for Octave 4.0.1?

Mike Miller-4
On Sun, Mar 27, 2016 at 14:47:27 +0200, José Luis García Pallero wrote:

> Hello:
>
> I've tried to compile the last Octave 4.0.1 sources and I've obtained
> some errors in the configure step. I use Debian Sid.
>
> First of all, the shared Lapack library from the repositories
> apparently doesn't work. I obtain the error
>
> checking for cheev_... no
> checking for cheev_ in -llapack... no
> checking for cheev_ in -llapack_rs6k... no
> configure: error: BLAS and LAPACK libraries are required
>
> so I need to configure with the option
> --with-lapack=/usr/lib/liblapack.a, i.e., with the static library (I
> obtain the same error with --with-lapack=/usr/lib/liblapack.so)
>
> I obtain also
>
> configure: WARNING: qrupdate not found.  The QR & Cholesky updating
> functions will be slow.
> configure: WARNING: CHOLMOD library not found.  This will result in
> some lack of functionality for sparse matrices.
> configure: WARNING: UMFPACK not found.  This will result in some lack
> of functionality for sparse matrices.
> configure: WARNING: ARPACK not found.  The eigs function will be disabled.
>
> but all these libraries are inatalled from the Debian repositories in
> /usr/lib/x86_64-linux-gnu/ instead of /usr/lib/. I didn't remember my
> last Octave building, but I though it runs

No problems on my Debian stretch. And no problems here:

  https://buildd.debian.org/status/package.php?p=octave&suite=sid

Might be worth looking into config.log to see why it fails to use these
libraries.

--
mike

Reply | Threaded
Open this post in threaded view
|

Re: Changes in configure for Octave 4.0.1?

José Luis García Pallero
2016-03-27 18:30 GMT+02:00 Mike Miller <[hidden email]>:

> On Sun, Mar 27, 2016 at 14:47:27 +0200, José Luis García Pallero wrote:
>> Hello:
>>
>> I've tried to compile the last Octave 4.0.1 sources and I've obtained
>> some errors in the configure step. I use Debian Sid.
>>
>> First of all, the shared Lapack library from the repositories
>> apparently doesn't work. I obtain the error
>>
>> checking for cheev_... no
>> checking for cheev_ in -llapack... no
>> checking for cheev_ in -llapack_rs6k... no
>> configure: error: BLAS and LAPACK libraries are required
>>
>> so I need to configure with the option
>> --with-lapack=/usr/lib/liblapack.a, i.e., with the static library (I
>> obtain the same error with --with-lapack=/usr/lib/liblapack.so)
>>
>> I obtain also
>>
>> configure: WARNING: qrupdate not found.  The QR & Cholesky updating
>> functions will be slow.
>> configure: WARNING: CHOLMOD library not found.  This will result in
>> some lack of functionality for sparse matrices.
>> configure: WARNING: UMFPACK not found.  This will result in some lack
>> of functionality for sparse matrices.
>> configure: WARNING: ARPACK not found.  The eigs function will be disabled.
>>
>> but all these libraries are inatalled from the Debian repositories in
>> /usr/lib/x86_64-linux-gnu/ instead of /usr/lib/. I didn't remember my
>> last Octave building, but I though it runs
>
> No problems on my Debian stretch. And no problems here:
>
>   https://buildd.debian.org/status/package.php?p=octave&suite=sid
>
> Might be worth looking into config.log to see why it fails to use these
> libraries.
Well, I've investigated a little bit and I've found the problem, but I
can't explain why the configure doesn't work. Yesterday I installed
julia, which has as a dependency in Debian Sid the package (among
others) libopenblas-base. This package makes their BLAS and Lapack
libraries as default, as it can be seen using

update-alternatives --config libblas.so.3
Existen 2 opciones para la alternativa libblas.so.3 (que provee
/usr/lib/libblas.so.3).

  Selección   Ruta                                 Prioridad  Estado
------------------------------------------------------------
* 0            /usr/lib/openblas-base/libblas.so.3   40        modo automático
  1            /usr/lib/libblas/libblas.so.3         10        modo manual
  2            /usr/lib/openblas-base/libblas.so.3   40        modo manual

and

update-alternatives --config liblapack.so.3
Existen 2 opciones para la alternativa liblapack.so.3 (que provee
/usr/lib/liblapack.so.3).

  Selección   Ruta                                   Prioridad  Estado
------------------------------------------------------------
* 0            /usr/lib/openblas-base/liblapack.so.3   40        modo automático
  1            /usr/lib/lapack/liblapack.so.3          10        modo manual
  2            /usr/lib/openblas-base/liblapack.so.3   40        modo manual

Using these BLAS and Lapack the Octave configure step fails (I attach
the condig.log file). If I select as default the
/usr/lib/libblas/libblas.so.3 and /usr/lib/lapack/liblapack.so.3
libraries, configure works without problems. But the default
/usr/lib/libblas/libblas.so.3 is the reference unoptimized BLAS
version and I want to use an optimized one. Before continue, I select
again as default the /usr/lib/openblas-base/libblas.so.3 and
/usr/lib/openblas-base/liblapack.so.3 as it was set by apt-get

I have also an OpenBLAS compiled by myself and I added it in the
configure step a --with-blas=/opt/openblas/lib/libopenblas.so. Then,
the configure breaks due to

checking for cheev_... no
checking for cheev_ in -llapack... no
checking for cheev_ in -llapack_rs6k... no
configure: error: BLAS and LAPACK libraries are required

so my OpenBLAS works and I suppose CHEEV is not present in the Debian
libopenblas-base Lapack implementation. Then, I select the Lapack
library manually in configure by passing
--with-blas=/opt/openblas/lib/libopenblas.so
--with-lapack=/usr/lib/lapack/liblapack.so. But the error is the same
as before:

checking for cheev_... no
checking for cheev_ in -llapack... no
checking for cheev_ in -llapack_rs6k... no
configure: error: BLAS and LAPACK libraries are required

so I don't know if configure select the passed
/usr/lib/lapack/liblapack.so (which is the same as I selected before
as default via update-alternatives) in order to do its internal check
for CHEEV. But surprisingly, if I use
--with-lapack=/usr/lib/lapack/liblapack.a, i.e., the Lapack static
library, the configure finds CHEEV, but at the end emit the warnings

configure: WARNING: qrupdate not found.  The QR & Cholesky updating
functions will be slow.
configure: WARNING: CHOLMOD library not found.  This will result in
some lack of functionality for sparse matrices.
configure: WARNING: UMFPACK not found.  This will result in some lack
of functionality for sparse matrices.
configure: WARNING: ARPACK not found.  The eigs function will be disabled.

which don't appear selecting the reference BLAS and Lapack via
update-alternatives. I've compiled also by myself the reference
Lapack, but as only the static library is generated I obtain the same
warnings regarding qrupdate, CHOLMOD, UMFPACK and ARPACK. But why this
warnings only appear when I use the liblapack.a?

Anyone has problems compiling Octave when the openblas-base from
Debian is present?

Thanks

>
> --
> mike



--
*****************************************
José Luis García Pallero
[hidden email]
(o<
/ / \
V_/_
Use Debian GNU/Linux and enjoy!
*****************************************

config.log (373K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Changes in configure for Octave 4.0.1?

Mike Miller-4
On Sun, Mar 27, 2016 at 20:53:10 +0200, José Luis García Pallero wrote:
> Well, I've investigated a little bit and I've found the problem, but I
> can't explain why the configure doesn't work. Yesterday I installed
> julia, which has as a dependency in Debian Sid the package (among
> others) libopenblas-base. This package makes their BLAS and Lapack
> libraries as default, as it can be seen using

I also have libopenblas-base installed and configured as the default
libblas.so.3.

Do you also have libopenblas-dev installed and configured to provide
libblas.so?

> Anyone has problems compiling Octave when the openblas-base from
> Debian is present?

FWIW, I always build with --with-blas=blas. This builds Octave against
the libblas.so symlink (which is the reference BLAS on my system), but
at runtime it uses the configured libblas.so.3 which is OpenBLAS.

I have not yet tried building with libopenblas-dev installed, but I will
try if I get a chance.

The exact error message from config.log is often more useful than just
what configure puts out on stdout.

--
mike

Reply | Threaded
Open this post in threaded view
|

Re: Changes in configure for Octave 4.0.1?

José Luis García Pallero
2016-03-28 8:26 GMT+02:00 Mike Miller <[hidden email]>:

> On Sun, Mar 27, 2016 at 20:53:10 +0200, José Luis García Pallero wrote:
>> Well, I've investigated a little bit and I've found the problem, but I
>> can't explain why the configure doesn't work. Yesterday I installed
>> julia, which has as a dependency in Debian Sid the package (among
>> others) libopenblas-base. This package makes their BLAS and Lapack
>> libraries as default, as it can be seen using
>
> I also have libopenblas-base installed and configured as the default
> libblas.so.3.
>
> Do you also have libopenblas-dev installed and configured to provide
> libblas.so?
>
>> Anyone has problems compiling Octave when the openblas-base from
>> Debian is present?
>
> FWIW, I always build with --with-blas=blas. This builds Octave against
> the libblas.so symlink (which is the reference BLAS on my system), but
> at runtime it uses the configured libblas.so.3 which is OpenBLAS.
>
> I have not yet tried building with libopenblas-dev installed, but I will
> try if I get a chance.
>
> The exact error message from config.log is often more useful than just
> what configure puts out on stdout.
Thank you for your answer. I attached the config.log in my previous message.

I'll try to explain my new compilation attempt:

I have these relevant packages installed:

libblas-common
libblas3
libblas-dev
libblapack3
liblapack-dev
liblapack-pic
liblapacke
liblapacke-dev
libopenblas-base
libopenblas-dev
libarpack2
libarpack2-dev

The update-alternatives shows that thedefault BLAS and Lapack in
/usr/lib are linked to the libraries provided by the openblas packages
and I've checked it inspecting the links via ls

If I execute ./configure --prefix=/opt/octave/ CFLAGS=-O3 CXXFLAGS=-O3
FFLAGS=-O3 --with-hdf5-includedir=/usr/include/hdf5/serial
--with-hdf5-libdir=/usr/lib/x86_64-linux-gnu/hdf5/serial the configure
works but prints this warning:

configure: WARNING: ARPACK library found, but does not seem to work
properly -- disabling eigs function

I attach the config.log file to this message, but I would like to
comment a couple of things:

The detected BLAS library is

BLAS libraries:              -lopenblas

as libopenblas-dev installs libopenblas.so (and .a) in /usr/lib
inaddition to the libblas and liblapack in /usr/lib/openblas (managed
later by umpate alternatives)

The configure script doesn't print anything about Lapack:

LAPACK libraries:

but any error about is issued, so I understand Lapack is detected

Thanks

>
> --
> mike



--
*****************************************
José Luis García Pallero
[hidden email]
(o<
/ / \
V_/_
Use Debian GNU/Linux and enjoy!
*****************************************

config.log.tar.gz (146K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Changes in configure for Octave 4.0.1?

Mike Miller-4
On Mon, Mar 28, 2016 at 13:33:48 +0200, José Luis García Pallero wrote:
> Thank you for your answer. I attached the config.log in my previous message.

Thanks, I missed that, looked at both config.logs now.

> I'll try to explain my new compilation attempt:
>
> I have these relevant packages installed:
>
> libblas-common
> libblas3
> libblas-dev
> libblapack3
> liblapack-dev
> liblapack-pic
> liblapacke
> liblapacke-dev
> libopenblas-base
> libopenblas-dev
> libarpack2
> libarpack2-dev
>
> The update-alternatives shows that thedefault BLAS and Lapack in
> /usr/lib are linked to the libraries provided by the openblas packages
> and I've checked it inspecting the links via ls

I now have the same configuration as you.

> If I execute ./configure --prefix=/opt/octave/ CFLAGS=-O3 CXXFLAGS=-O3
> FFLAGS=-O3 --with-hdf5-includedir=/usr/include/hdf5/serial
> --with-hdf5-libdir=/usr/lib/x86_64-linux-gnu/hdf5/serial the configure
> works but prints this warning:
>
> configure: WARNING: ARPACK library found, but does not seem to work
> properly -- disabling eigs function
>
> I attach the config.log file to this message, but I would like to
> comment a couple of things:
>
> The detected BLAS library is
>
> BLAS libraries:              -lopenblas
>
> as libopenblas-dev installs libopenblas.so (and .a) in /usr/lib
> inaddition to the libblas and liblapack in /usr/lib/openblas (managed
> later by umpate alternatives)
>
> The configure script doesn't print anything about Lapack:
>
> LAPACK libraries:
>
> but any error about is issued, so I understand Lapack is detected

I have now installed libopenblas-dev and run configure and I don't see
any errors with ARPACK here. So I'm not sure why you are seeing that.
The relevant error message in your config.log (both prior and latest)
is:

./conftest: symbol lookup error: /usr/lib/libblas.so.3: undefined symbol: gotoblas

but if you check /usr/lib/libblas.so.3 it should have a dependency on
libopenblas.so.0 where the gotoblas symbol comes from. You said you also
compiled OpenBLAS from source, do you happen to have LD_LIBARY_PATH or
ld.so.conf pointing to the self-built libraries in /opt/openblas/lib?

If not, if the linker is finding /usr/lib/libopenblas.so.0, then it
should have that symbol and that error should not appear.

--
mike

Reply | Threaded
Open this post in threaded view
|

Re: Changes in configure for Octave 4.0.1?

José Luis García Pallero
2016-03-28 17:31 GMT+02:00 Mike Miller <[hidden email]>:

> On Mon, Mar 28, 2016 at 13:33:48 +0200, José Luis García Pallero wrote:
>> Thank you for your answer. I attached the config.log in my previous message.
>
> Thanks, I missed that, looked at both config.logs now.
>
>> I'll try to explain my new compilation attempt:
>>
>> I have these relevant packages installed:
>>
>> libblas-common
>> libblas3
>> libblas-dev
>> libblapack3
>> liblapack-dev
>> liblapack-pic
>> liblapacke
>> liblapacke-dev
>> libopenblas-base
>> libopenblas-dev
>> libarpack2
>> libarpack2-dev
>>
>> The update-alternatives shows that thedefault BLAS and Lapack in
>> /usr/lib are linked to the libraries provided by the openblas packages
>> and I've checked it inspecting the links via ls
>
> I now have the same configuration as you.
>
>> If I execute ./configure --prefix=/opt/octave/ CFLAGS=-O3 CXXFLAGS=-O3
>> FFLAGS=-O3 --with-hdf5-includedir=/usr/include/hdf5/serial
>> --with-hdf5-libdir=/usr/lib/x86_64-linux-gnu/hdf5/serial the configure
>> works but prints this warning:
>>
>> configure: WARNING: ARPACK library found, but does not seem to work
>> properly -- disabling eigs function
>>
>> I attach the config.log file to this message, but I would like to
>> comment a couple of things:
>>
>> The detected BLAS library is
>>
>> BLAS libraries:              -lopenblas
>>
>> as libopenblas-dev installs libopenblas.so (and .a) in /usr/lib
>> inaddition to the libblas and liblapack in /usr/lib/openblas (managed
>> later by umpate alternatives)
>>
>> The configure script doesn't print anything about Lapack:
>>
>> LAPACK libraries:
>>
>> but any error about is issued, so I understand Lapack is detected
>
> I have now installed libopenblas-dev and run configure and I don't see
> any errors with ARPACK here. So I'm not sure why you are seeing that.
> The relevant error message in your config.log (both prior and latest)
> is:
>
> ./conftest: symbol lookup error: /usr/lib/libblas.so.3: undefined symbol: gotoblas
>
> but if you check /usr/lib/libblas.so.3 it should have a dependency on
> libopenblas.so.0 where the gotoblas symbol comes from. You said you also
> compiled OpenBLAS from source, do you happen to have LD_LIBARY_PATH or
> ld.so.conf pointing to the self-built libraries in /opt/openblas/lib?
Yes, you are right, I've defined the LD_LIBRARY_PATH for my OpenBLAS.
If I undefine it, the Octave configure works properly. But I still
have some questions about the configure internals. I'll try to ask
using examples:

1. If I uninstall the Debian openblas, maintain the reference BLAS and
Lapack and use my own OpenBLAS (only BLAS) via LD_LIBRARY_PATH the
configure script works without problems. The script detects -lopenblas
as BLAS because I've put the /opt/openblas/lib/ in LD_LIBRARY_PATH at
the begining and the system detects libopenblas.so before the
reference /usr/lib/libblas.so

2. If I install the Debian openblas, maintain the reference BLAS and
Lapack and turn off my own OpenBLAS, again the configure script works

3. If I install the Debian openblas, maintain the reference BLAS and
Lapack and maintain my own OpenBLAS via LD_LIBRARY_PATH come the
problems.

First, if I execute

./configure --prefix=/opt/octave/

I obtain an error about cheev_ doesn't found. In this case, the used
openblas is my own library and Lapack is the system one (-llapack from
the Debian openblas)

Second, if I execute

./configure --prefix=/opt/octave/
--with-blas=/opt/openblas/lib/libopenblas.so
--with-lapack=/usr/lib/lapack/liblapack.so

i.e., I select explicitly my own OpenBLAS and the system reference
Lapack stored in /usr/lib/lapack/liblapack.so, I obtain an
//usr/lib/libblas.so.3: undefined reference to `gotoblas' (I attach
the config.log_myopenblas). But the same configuration didn't produce
errors (this is the same configuration as in example 1 because here I
select explicitly the libraries involved in that example)

Third, if I execute

./configure --prefix=/opt/octave/
--with-blas=/usr/lib/openblas-base/libblas.so
--with-lapack=/usr/lib/openblas-base/liblapack.so

i.e., I select explicitly the Debian OpenBLAS, I obtain again (I
attach config.log_debianopenblas) the error about the undfined
reference of gotoblas in /usr/lib/openblas-base/libblas.so

Finally, if I execute

./configure --prefix=/opt/octave/ --with-blas=/usr/lib/libopenblas.so
--with-lapack=/usr/lib/libopenblas.so

i.e. another way to select explicitly the Debian OpenBLAS, because in
addition to /usr/lib/openblas-base/libblas.so and
/usr/lib/openblas-base/liblapack.so the library
/usr/lib/libopenblas.so is also installed, which contains BLAS and
Lapack. In this case the configure works but with the warning WARNING:
ARPACK library found, but does not seem to work properly -- disabling
eigs function (I attach config.log_arpack)

So the configuration works if I disable my OpenBLAS, but I don't
understand the behavior when both mine and the Debian one coexists and
I select explicitly one of them in the configure process

Thanks

>
> If not, if the linker is finding /usr/lib/libopenblas.so.0, then it
> should have that symbol and that error should not appear.
>
> --
> mike



--
*****************************************
José Luis García Pallero
[hidden email]
(o<
/ / \
V_/_
Use Debian GNU/Linux and enjoy!
*****************************************

config.log_myopenblas.tar.gz (54K) Download Attachment
config.log_debianopenblas.tar.gz (56K) Download Attachment
config.log_arpack.tar.gz (146K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Changes in configure for Octave 4.0.1?

Mike Miller-4
On Mon, Mar 28, 2016 at 21:11:00 +0200, José Luis García Pallero wrote:

> Yes, you are right, I've defined the LD_LIBRARY_PATH for my OpenBLAS.
> If I undefine it, the Octave configure works properly. But I still
> have some questions about the configure internals. I'll try to ask
> using examples:
>
> 1. If I uninstall the Debian openblas, maintain the reference BLAS and
> Lapack and use my own OpenBLAS (only BLAS) via LD_LIBRARY_PATH the
> configure script works without problems. The script detects -lopenblas
> as BLAS because I've put the /opt/openblas/lib/ in LD_LIBRARY_PATH at
> the begining and the system detects libopenblas.so before the
> reference /usr/lib/libblas.so
>
> 2. If I install the Debian openblas, maintain the reference BLAS and
> Lapack and turn off my own OpenBLAS, again the configure script works
>
> 3. If I install the Debian openblas, maintain the reference BLAS and
> Lapack and maintain my own OpenBLAS via LD_LIBRARY_PATH come the
> problems.
>
> First, if I execute
>
> ./configure --prefix=/opt/octave/
>
> I obtain an error about cheev_ doesn't found. In this case, the used
> openblas is my own library and Lapack is the system one (-llapack from
> the Debian openblas)
>
> Second, if I execute
>
> ./configure --prefix=/opt/octave/
> --with-blas=/opt/openblas/lib/libopenblas.so
> --with-lapack=/usr/lib/lapack/liblapack.so
>
> i.e., I select explicitly my own OpenBLAS and the system reference
> Lapack stored in /usr/lib/lapack/liblapack.so, I obtain an
> //usr/lib/libblas.so.3: undefined reference to `gotoblas' (I attach
> the config.log_myopenblas). But the same configuration didn't produce
> errors (this is the same configuration as in example 1 because here I
> select explicitly the libraries involved in that example)
>
> Third, if I execute
>
> ./configure --prefix=/opt/octave/
> --with-blas=/usr/lib/openblas-base/libblas.so
> --with-lapack=/usr/lib/openblas-base/liblapack.so
>
> i.e., I select explicitly the Debian OpenBLAS, I obtain again (I
> attach config.log_debianopenblas) the error about the undfined
> reference of gotoblas in /usr/lib/openblas-base/libblas.so
>
> Finally, if I execute
>
> ./configure --prefix=/opt/octave/ --with-blas=/usr/lib/libopenblas.so
> --with-lapack=/usr/lib/libopenblas.so
>
> i.e. another way to select explicitly the Debian OpenBLAS, because in
> addition to /usr/lib/openblas-base/libblas.so and
> /usr/lib/openblas-base/liblapack.so the library
> /usr/lib/libopenblas.so is also installed, which contains BLAS and
> Lapack. In this case the configure works but with the warning WARNING:
> ARPACK library found, but does not seem to work properly -- disabling
> eigs function (I attach config.log_arpack)
>
> So the configuration works if I disable my OpenBLAS, but I don't
> understand the behavior when both mine and the Debian one coexists and
> I select explicitly one of them in the configure process

I have never built or installed OpenBLAS myself except from the Debian
packages, so I don't understand much about this either.

But the problems all seem to arise when you use Debian's OpenBLAS
compatibility wrapper for libblas.so.3 with your own self-compiled
OpenBLAS.

I'm guessing something in the build process needs a library called
"libblas.so.3" and if the one in /usr/lib is the first one found, that's
Debian's OpenBLAS wrapper, which in turn depends on libopenblas.so.0.

Does your /opt/openblas build have a libblas.so.3 library? If so, can
you arrange for it to be used instead of /usr/lib/libblas.so.3? If not,
why not, is it needed, and if so how do you build it for your OpenBLAS?
And why does the Debian one not work with your libopenblas.so.0?

I would guess if you were building *everything* from scratch, you could
simply link everything against libopenblas.so.0 and it would just work.
But since you have other libraries installed from Debian that are built
against libblas.so.3, that shim library is needed to make OpenBLAS work
as a drop-in replacement.

That's as much as I know, I hope it helps, let us know if you figure
something out.

--
mike

Reply | Threaded
Open this post in threaded view
|

Re: Changes in configure for Octave 4.0.1?

Dmitri A. Sergatskov
In reply to this post by José Luis García Pallero


On Mon, Mar 28, 2016 at 2:11 PM, José Luis García Pallero <[hidden email]> wrote:

Second, if I execute

./configure --prefix=/opt/octave/
--with-blas=/opt/openblas/lib/libopenblas.so
--with-lapack=/usr/lib/lapack/liblapack.so



​I think you suppose to do

./configure ​--with-blas="-L/opt/openblas/lib -lopenbls"  --with-lapack="-L/usr/lib/lapack -llapack"

Dmitri.
--