help-octave
[Top][All Lists]
Advanced

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

Re: Octave and the new Mountain Lion Operating System


From: Ben Abbott
Subject: Re: Octave and the new Mountain Lion Operating System
Date: Sun, 05 Aug 2012 10:35:58 -0400

On Aug 5, 2012, at 10:33 AM, Ben Abbott wrote:

> On Aug 4, 2012, at 11:13 PM, pete karousos wrote:
> 
>> Actually,
>> 
>> Looking a little closer I think the definition of SuiteSparse_tic and 
>> SuiteSparse_toc were wrapped inside #ifdef SUITESPARSE_TIMER_ENABLED and 
>> SUITESPARSE_TIMER_ENABLED is defined in SuiteSparse_config.h but it is only 
>> defined if NTIMER is not defined. That would explain the undefined symbols. 
>> When building for OS X though NTIMER is defined. I believe the real fix is 
>> to not define NTIMER if the operating system is OS X and to provide the 
>> definition of SuiteSparse_time the way I did if the operating system is OS X.
>> 
>> On Sat, Aug 4, 2012 at 10:02 PM, Ben Abbott <address@hidden> wrote:
>> 
>> On Aug 4, 2012, at 4:04 PM, pete karousos wrote:
>> 
>>> I am running SuiteSparse 4.0.2. It was the SuiteSparse code I had to change 
>>> not the Octave code. Once I got SuiteSpace to build everything was fine. I 
>>> built everything against octave-3.6.2.
>> 
>> I tried SuiteSparse 4.0.0 (from MacPorts) and am seeing the error below.  
>> What change did you make to SuiteSparse?
>> 
>> 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)
>> 
>> Ben
> 
> I've been successful in resoling the problem by including -lSuiteSparse in 
> the UMFPACK_LIBS variable.  Either ...
> 
>       ./configure UMFPACK_LIBS="-lumfpack -lSuiteSparse"
> 
> ... or ...
> 
>       export UMFPACK_LIBS="-lumfpack -lSuiteSparse"
>       ./configure ...
> 
> ... should work.  What I've done so far was to edit liboctave/Makefile and 
> add "-lSuiteSparse" to the UMFPACK_LIBS variable definition.  After that 
> octave built without incident and "make check" returned no new failures.  
> I've started a fresh build starting to configure to check that everything 
> works as expected.  If it does, I'll file a bug report (configure should 
> check if -lSuiteSparse needs to be added to UMFPACK_LIBS). 
> 
> 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.

Ben



reply via email to

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