octave-maintainers
[Top][All Lists]
Advanced

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

Re: SuiteSparse problems


From: Ben Abbott
Subject: Re: SuiteSparse problems
Date: Thu, 09 Aug 2012 17:32:18 -0400

On Aug 9, 2012, at 4:43 PM, Martin Helm <address@hidden> wrote:

> Am 06.08.2012 23:55, schrieb Ben Abbott:
>> On Aug 5, 2012, at 10:45 AM, Ben Abbott wrote:
>> 
>>> On Aug 5, 2012, at 10:25 AM, Ben Abbott wrote:
>>> 
>>>> On Aug 4, 2012, at 10:55 PM, Ben Abbott wrote:
>>>> 
>>>>> On Aug 4, 2012, at 10:25 PM, Ben Abbott wrote:
>>>>> 
>>>>>> On Jul 31, 2012, at 7:37 PM, Ed Meyer wrote:
>>>>>> 
>>>>>>> On Mon, Jul 30, 2012 at 9:48 PM, Robinson, Melvin D <address@hidden> 
>>>>>>> wrote:
>>>>>>> Hello,
>>>>>>> 
>>>>>>> Tried to build Octave from sources with the latest version of 
>>>>>>> SuiteSparse.  It seems that the symbol SuiteSparse_time has been 
>>>>>>> deprecated.  Here is the error message I receive
>>>>>>> 
>>>>>>> Undefined symbols for architecture x86_64:
>>>>>>> "_SuiteSparse_time", referenced from:
>>>>>>>   _umfpack_tic in libumfpack.a(umfpack_gn_tictoc.o)
>>>>>>>   _umfpack_toc in libumfpack.a(umfpack_gn_tictoc.o)
>>>>>>> ld: symbol(s) not found for architecture x86_64
>>>>>>> collect2: ld returned 1 exit status
>>>>>>> make[3]: *** [liboctave.la] Error 1
>>>>>>> make[2]: *** [all] Error 2
>>>>>>> make[1]: *** [all-recursive] Error 1
>>>>>>> make: *** [all] Error 2
>>>>>>> butterfly:octave melrobin$ port list SuiteSparse
>>>>>>> SuiteSparse                    @4.0.0          math/SuiteSparse
>>>>>>> 
>>>>>>> Something similar happens on Fedora as well.  Backing down to 
>>>>>>> SuiteSparse 3.7.1 works.
>>>>>>> 
>>>>>>> 
>>>>>>> what version of umfpack do you have - my 5.4 calls umfpack_timer but 
>>>>>>> not SuiteSparse_time so
>>>>>>> maybe you just need a newer umfpack
>>>>>>> 
>>>>>> umfpack is part of the SuiteSparse meta-package. Correct ?
>>>>>> 
>>>>>>    http://www.cise.ufl.edu/research/sparse/SuiteSparse/
>>>>>> 
>>>>>> SuiteSparse-4.0.2 has been released. I'll try a local build to see if 
>>>>>> the problem is still present.
>>>>>> 
>>>>>> Ben
>>>>> Building Octave with SuiteSparse-4.0.2 I still encounter the errors below 
>>>>> (during the link phase for liboctave)
>>>>> 
>>>>> Undefined symbols for architecture x86_64:
>>>>> "_SuiteSparse_time", referenced from:
>>>>>    _umfpack_tic in libumfpack.a(umfpack_gn_tictoc.o)
>>>>>    _umfpack_toc in libumfpack.a(umfpack_gn_tictoc.o)
>>>>> 
>>>>> A google (link below) indicates this problem can be fixed.
>>>>> 
>>>>>    http://trac.macports.org/ticket/35176
>>>>> 
>>>>> When linking to libumfpack.a we must also link to libSuiteSparse.dylib.  
>>>>> I manually edited the Makefile for liboctave and added -lSuiteSparse to 
>>>>> the UMFPACK_LIBS variable.
>>>>> 
>>>>>    UMFPACK_LIBS = -lumfpack -lSuiteSparse
>>>>> 
>>>>> liboctave now builds for me.  I'll continue with my Octave build and 
>>>>> report back later.
>>>> My build completed, and have no new test failures (make check).
>>>> 
>>>> I haven't verified, but setting UMFPACK_LIBS and then running configure or 
>>>> passing UMFPACK_LIBS to configure should resolve this.
>>>> 
>>>>    export UMFPACK_LIBS="-lumfpack -lSuiteSparse"
>>>>    ./configure ...
>>>> 
>>>> or
>>>> 
>>>>    ./configure UMFPACK_LIBS="-lumfpack -lSuiteSparse" ...
>>>> 
>>>> Ben
>>> Setting the UMFPACK_LIBS variable did not work.  The configure script will 
>>> need to be fixed.  As a work around the liboctave Makefile may be manually 
>>> modified.
>>> 
>>> I've opened a bug report.
>>> 
>>>    https://savannah.gnu.org/bugs/?37031
>>> 
>>> Ben
>> A simple work around it to add the configure script option below
>> 
>>    --with-umfpack="-lumfpack -lSuiteSparse"
>> 
>> Ben
>> 
> Anyone has an idea how to fix that on Linux? I ran today into the same 
> problem on openSUSE 12.2 RC2, of course I can downgrade suitesparse but 
> that's not really clever since the default is 4.0.
> If not I will investigate over the weekend.

Did you try adding  --with-umfpack="-lumfpack -lSuiteSparse" as an option to 
the configure script?

Ben


reply via email to

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