[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ARPACK sources removed from Octave
From: |
Rik |
Subject: |
Re: ARPACK sources removed from Octave |
Date: |
Wed, 04 Jan 2012 09:56:46 -0800 |
On 01/03/2012 05:18 PM, John W. Eaton wrote:
> On 26-Dec-2011, Rik wrote:
>
> | I reduced the work you did in bug #31479 to a simple test case that could
> | be run by configure to verify the installed ARPACK library. I'm attaching
> | the file as you can probably insert it more easily into configure.ac.
> |
> | When I run
> | g++ -o arpack_libtest -llapack -lblas -larpack arpack_libtest.cc
> | ./arpack_libtest
> |
> | I get a segfault. This is built against a problem version of ARPACK that
> | is shipped with Ubuntu 10.04 (2.1+parpack96.dfsg-2build1).
> |
> | If I build against the fixed version of ARPACK in libcruft it works
> |
> | g++ -o arpack_libtest -L/usr/local/lib/octave/3.4.3 -llapack -lblas -lcruft
> | arpack_libtest.cc
> | setenv LD_LIBRARY_PATH /usr/local/lib/octave/3.4.3/
> | ./arpack_libtest
>
> Thanks for looking at this problem. I converted your C++ program to
> Fortran and checked in the following changeset to add the test to the
> configure script and remove the arpack sources from Octave.
>
> http://hg.savannah.gnu.org/hgweb/octave/rev/834df9f10963
>
> Could you check to make sure that this test still fails when you run
> it with the old version of ARPACK that has the bug?
>
> jwe
>
Alas, the new test does not fail with a bad ARPACK library. Is there a
reason to have the test written in Fortran and not C++? The C++ version
was already debugged, but if we really want the configure test in Fortran
we can continue.
I wrapped your test code with "program main" / "end program main" to make
it a stand-alone program. The file is attached.
I compile with
gfortran -o fortran_libtest arpack_libtest.f -llapack -lblas -larpack
and then run
./fortan_libtest
which returns to the shell prompt normally.
--Rik
arpack_libtest.f
Description: Text Data