|
From: | Martin Helm |
Subject: | Re: SuiteSparse problems |
Date: | Thu, 09 Aug 2012 23:47:03 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120713 Thunderbird/14.0 |
Am 09.08.2012 23:32, schrieb Ben Abbott:
That does not help here since nothing with that name or even a similar one exists to link against (I naively tried of course before I looked deeper). Seems i have to find out if there is some build problem here with the rpm's coming from the prerelease repository which leads to something which is missing. (openSUSE 12.2 is not yet released, I am testing release candidates at the moment). I was not really sure what a dylib translates to in the Linux world, I'ld guess I should have an equivalent .so file here if I interpret that right? I think I will simply build the whole suitesparse stack locally here at the weekend to see if that is a simple packaging error or something more fundamental. Just wanted to know if someone with a Linux distro which ships suitesparse version 4 ran already across it and found an easy solution or workaround.On Aug 9, 2012, at 4:43 PM, Martin Helm <address@hidden> wrote: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
[Prev in Thread] | Current Thread | [Next in Thread] |