help-octave
[Top][All Lists]
Advanced

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

Octave 3.0.0: configure doesn't find the Suitesparse Libraries


From: John W. Eaton
Subject: Octave 3.0.0: configure doesn't find the Suitesparse Libraries
Date: Thu, 21 Feb 2008 14:12:32 -0500

On 21-Feb-2008, Jan Ruebel wrote:

| I am trying to configure octave3.0.0 with the latest SuiteSparse package (v. 
| 3.1, including UMFPACK, CHOLMOD etc). So far I've compiled SuitesSparse 
| succesfully. I placed links to the resulting *.a and *.h files in /usr/lib/ 
| and usr/include/  (I also tried /usr/local/lib and /usr/local/include) and 
| ran ./configure in the octave3.0.0 directory.
| However it seems that configure doesn't find the suitesparse libraries:
| 
| configure: WARNING: UMFPACK not found.  This will result in some lack of 
| functionality for sparse matrices.
| configure: WARNING: COLAMD not found. This will result in some lack of 
| functionality for sparse matrices.
| configure: WARNING: CCOLAMD not found. This will result in some lack of 
| functionality for sparse matrices.
| configure: WARNING: CHOLMOD not found. This will result in some lack of 
| functionality for sparse matrices.
| configure: WARNING: CXSparse not found. This will result in some lack of 
| functionality for sparse matrices.
| 
| A subsequent "Make" works and octave compiles succesfully and works.
| But I cannot use the UMFPACK features...
| 
| Is there a default path where ./configure checks for these libraries and 
| headers?
| How can I tell configure where to look?
| 
| I'm using gcc 3.3.4 on a SuSE 9.2 system.

The configure script just uses the compiler to find libraries.  You
should not need to put links in /usr/lib or /usr/include.  Instead,
use CPPFLAGS to tell your compiler where to search for header files
and LDFLAGS to tell the linker where to find libraries.  For example


  ./configure CPPFLAGS=-I/usr/local/include LDFLAGS=-L/usr/local/lib ...

If this doesn't work, and the libraries and header files are
installed, then you need to look in the config.log file to find out
why the tests are failing.

jwe


reply via email to

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