[Pkg-julia-devel] building julia 0.3

[Viral B. Shah]

This all sounds ok. You can probably see libcholmod in the julia/usr/lib directory. You have to solve a sparse cholesky system to use it.

-viral


On Jul 23, 2014, at 10:08 AM, Ross Boylan <rossboylan at stanfordalumni.org> wrote:

> After the rebuild I launched julia (from emacs/ess).  lsof doesn't
> list libcholmod from either the system or the julia tree.  Maybe I
> need to do something that requires it to get it loaded.
> 
> Ross
> 
> On Tue, Jul 22, 2014 at 9:31 PM, Ross Boylan
> <rossboylan at stanfordalumni.org> wrote:
>> I redid the make (with the SUITESPARSE removed), but I'm not entirely
>> sure what happened.  First, I don't see a reference to a sparse
>> submodule, though something was downloaded.  Second, some libraries
>> were built, but not the julia executable.  Will it just pick the right
>> ones up dynamically?
>> 
>> /usr/local/src/julia/julia /usr/local/src/julia
>> Submodule 'deps/Rmath' () registered for path 'deps/Rmath'
>> Submodule 'deps/libuv' () registered for path 'deps/libuv'
>> Submodule 'deps/openlibm' () registered for path 'deps/openlibm'
>> Submodule 'deps/openspecfun' () registered for path 'deps/openspecfun'
>> Submodule 'doc/juliadoc' () registered for path 'doc/juliadoc'
>>  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
>>                                 Dload  Upload   Total   Spent    Left  Speed
>> 100 21.4M  100 21.4M    0     0   261k      0  0:01:24  0:01:24 --:--:--  227k
>> ar: creating libcerbla.a
>> a - xerbla.o
>> ar: creating libsuitesparseconfig.a
>> a - SuiteSparse_config.o
>> ar: creating libamd.a
>> a - amd_global.o
>> [much more]
>> ar: creating librbio.a
>> a - RBio.o
>> 
>> cholmod_version does appear on the transcript, and there are no errors
>> that I see.
>> 
>> On Tue, Jul 22, 2014 at 3:01 PM, Viral Shah <viral at mayin.org> wrote:
>>> I do not know what the versions of the dependencies in debian stable are.
>>> 
>>> cholmod_version was introduced in the last few months, and hence a newer version may be required. Try removing the USE_SYSTEM_SUITESPARSE=1 build option. I am pretty sure also that the lapack version will be too old - at least 3.4 would be good.
>> 
>> lapack is 3.4 in Wheezy, so I continued to use the system version.
>> 
>>> 
>>> -viral
>>>