help-octave
[Top][All Lists]
Advanced

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

Re: Fwd: Please release RC1 to octave/unstable PPA --- umfpack_zi_get_de


From: Mike Miller
Subject: Re: Fwd: Please release RC1 to octave/unstable PPA --- umfpack_zi_get_determinant not found!
Date: Wed, 11 Dec 2013 09:38:00 -0500
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20131103 Icedove/17.0.10

On Wed, 11 Dec 2013 15:14:06 +0100, Kjetil brinchmann Halvorsen wrote:
> On Wed, Dec 11, 2013 at 3:07 PM, Mike Miller <address@hidden> wrote:
>> On Wed, 11 Dec 2013 14:55:45 +0100, Kjetil brinchmann Halvorsen wrote:
>>> Yes. Now I have removed suitesparse_metis_dev and installed (again)
>>> suitesparse_dev
>>>
>>> This is what happens (first I did make clean & hg pull & hg update 
>>> &./bootstrap
>>> then
>>> ./configure
>>>
>>> Output:
>>>
>>> configure: WARNING: UMFPACK not found.  This will result in some lack
>>> of functionality for sparse matrices.
>>>
>>> and higher up in the output I find this lines, explaining why UMFPACK
>>> is not found:
>>>
>>> checking suitesparse/umfpack.h usability... yes
>>> checking suitesparse/umfpack.h presence... yes
>>> checking for suitesparse/umfpack.h... yes
>>> checking for umfpack_zi_get_determinant in -lumfpack... no
>>> configure: WARNING: UMFPACK not found.  This will result in some lack
>>> of functionality for sparse matrices.
>>>
>>> so it is                            umfpack_zi_get_determinant
>>>
>>> which is not found
>>
>> So can you please send the config.log from that configure run to
>> determine why that is? This is a file created by configure, not just the
>> output you see on the screen. The umfpack library surely does contain
>> that symbol, the log may help explain why configure is failing to detect
>> it properly.
> 
> Here comes config.log as attachment.

Which shows exactly your problem, which I am unable to reproduce on
Debian or Ubuntu.

> /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/libumfpack.so: undefined 
> reference to `cholmod_l_free_factor'
> /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/libumfpack.so: undefined 
> reference to `cholmod_l_transpose'
> /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/libumfpack.so: undefined 
> reference to `cholmod_analyze'
> /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/libumfpack.so: undefined 
> reference to `cholmod_l_start'
> /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/libumfpack.so: undefined 
> reference to `cholmod_l_analyze'
> /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/libumfpack.so: undefined 
> reference to `cholmod_l_free_sparse'
> /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/libumfpack.so: undefined 
> reference to `cholmod_finish'
> /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/libumfpack.so: undefined 
> reference to `cholmod_l_print_common'
> /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/libumfpack.so: undefined 
> reference to `cholmod_free_sparse'
> /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/libumfpack.so: undefined 
> reference to `cholmod_start'
> /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/libumfpack.so: undefined 
> reference to `cholmod_free_factor'
> /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/libumfpack.so: undefined 
> reference to `cholmod_transpose'
> /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/libumfpack.so: undefined 
> reference to `cholmod_l_finish'
> /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/libumfpack.so: undefined 
> reference to `cholmod_print_common'
> collect2: error: ld returned 1 exit status

Does compiling the following test program fail for you?

$ cat > conftest.c <<EOF
char umfpack_zi_get_determinant ();
int main ()
{
  return umfpack_zi_get_determinant ();
}
EOF
$ gcc -o conftest conftest.c -lumfpack

If this fails with the same errors as above, then you have a different
umfpack library than I do, check your apt sources, clean up your PPAs.

If this succeeds, then try adding libraries from the config.log version
of this compilation test until you figure out what it is that makes this
fail on your system.

-- 
mike


reply via email to

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