octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Libraries not found in ./configure step


From: José Luis García Pallero
Subject: Re: Libraries not found in ./configure step
Date: Wed, 27 Nov 2013 16:19:51 +0100

2013/11/27 Jordi Gutiérrez Hermoso <address@hidden>:
> On Wed, 2013-11-27 at 16:03 +0100, José Luis García Pallero wrote:
>
>> Also I obtain the warnings:
>>
>> configure: WARNING: UNEXPECTED: found nth_element working in g++
>> 4.8.2.  Has it been patched on your system?
>> configure: WARNING: qrupdate not found.  The QR & Cholesky updating
>> functions will be slow.
>> configure: WARNING: ARPACK not found.  The eigs function will be disabled.
>> configure: WARNING: JAVA_HOME environment variable not initialized.
>> Auto-detection will proceed but is unreliable.
>>
>> 1- I don't understand the warnings about the g++ compiler
>
> We know that g++ 4.8.2 has a bug, apparently on your system it
> doesn't. The configure script is just surprised that this happened.

In my system (Debian Sid), the g++ --version output is:

g++ (Debian 4.8.2-5) 4.8.2

>
>> 2- I have installed the QRUPDATE and ARPACK libraries in the standard
>> paths (/usr/lib/libqrupdate.a and /usr/lib/libarpack.a). I've tried to
>> pass the options --with-qrupdate-libdir=/usr/lib/
>> --with-arpack-libdir=/usr/lib/, but the warnings still appear
>
> You need shared versions of those libraries or to compile Octave
> statically.

I also have the shared libraries for these libraries (I've installed
the packages from Debian Sid official repos):

/usr/lib/libarpack.so and /usr/lib/libarpack.so.2 (both are symbolic
links to /usr/lib/libarpack.so.2.0.0)
/usr/lib/libqrupdate.so and /usr/lib/libqrupdate.so.1 (both are
symbolic links to /usr/lib/libqrupdate.so.1.1)

>
> You shouldn't need to compile your own versions of these libraries:
> they are already packaged for Debian.
>
>> 3- I don't understand also the warning about the JAVA_HOME
>
> Octave now uses Java. If you don't set a JAVA_HOME environment
> variable, the configure script will try to guess where Java is, but
> Java is so weird across platforms that guessing where it might be is
> impossible in general. For Debian, you're lucky enough that we happen
> to like Debian, so we know where to find its Java installation.

Why Octave needs Java? Should I only create the JAVA_HOME environment
variable? Should I assign any value?

Thanks

>
> - Jordi G. H.
>
>



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


reply via email to

[Prev in Thread] Current Thread [Next in Thread]