> It expects things to be installed in your library path. If you've > installed it elsewhere, you can set the LD_LIBRARY_PATH or LIBRARY_PATH > environment variables to point to where you've installed it.
That (along with renaming the library to libarpack.a; the default is libarpack_$(PLAT).a) fixed this problem, but ran into a new one: ~$ LIBRARY_PATH=/home/palmer/windocs/Work/ARPACK octave GNU Octave, version 3.0.1 Copyright (C) 2008 John W. Eaton and others. This is free software; see the source code for copying conditions. There is ABSOLUTELY NO WARRANTY; not even for MERCHANTIBILITY or FITNESS FOR A PARTICULAR PURPOSE. For details, type `warranty'. Octave was configured for "x86_64-pc-linux-gnu". Additional information about Octave is available at http://www.octave.org. Please contribute if you find this software useful. For more information, visit http://www.octave.org/help-wanted.html Report bugs to <[EMAIL PROTECTED]> (but first, please read http://www.octave.org/bugs.html to learn how to write a helpful report). For information about changes from previous versions, type `news'. octave:1> cd windocs/Work octave:2> pkg install arpack-1.0.6.tar.gz /usr/bin/ld: /home/palmer/windocs/Work/ARPACK/libarpack.a(dgemv.o): relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC /home/palmer/windocs/Work/ARPACK/libarpack.a: could not read symbols: Bad value collect2: ld returned 1 exit status make: *** [eigs.oct] Error 1 error: 'make' returned the following error: make: Entering directory `/tmp/oct-e31ni6/arpack-1.0.6/src' mkoctfile -DHAVE_OCTAVE_30 -v -DHAVE_CONFIG_H -DHAVE_ARPACK eigs.cc -larpack g++ -c -fPIC -I/usr/include/octave-3.0.1 -I/usr/include/octave-3.0.1/octave -O2 -g -DHAVE_OCTAVE_30 -DHAVE_CONFIG_H -DHAVE_ARPACK eigs.cc -o eigs.o g++ -shared -Wl,-Bsymbolic -o eigs.oct eigs.o -larpack -L/usr/lib/octave-3.0.1 -loctinterp -loctave -lcruft -llapackgf-3 -lblas-3gf -lfftw3 -lreadline -lncurses -ldl -lhdf5 -lz -lm -L/usr/lib/gcc/x86_64-linux-gnu/4.3.1 -L/usr/lib/gcc/x86_64-linux-gnu/4.3.1/../../../../lib -L/lib/../lib -L/usr/lib/../lib -L/usr/lib/gcc/x86_64-linux-gnu/4.3.1/../../.. -lhdf5 -lz -lgfortranbegin -lgfortran -lm make: Leaving directory `/tmp/oct-e31ni6/arpack-1.0.6/src' error: called from `pkg:configure_make' in file /usr/share/octave/3.0.1/m/pkg/pkg.m near line 1245, column 2 octave:2> I tried recompiling ARPACK with FFLAGS = -O -fPIC in ARmake.inc, but this error still occurred. > IIRC, I recently read somewhere that licensing problem of arpack has > been resolved so it may be back in "main" again. The current license of ARPACK is found at http://www.caam.rice.edu/software/ARPACK/RiceBSD.txt#LICENSE, and does remove the notification requirement. I agree that making this a default part of Octave, or at least providing a more user-friendly way to install it (I've already had to edit ARmake.inc to get ARPACK to compile at all: the supplied ones appear to be written for various proprietary Unixes, and fail to run in Linux), would be a good idea if legally possible. I did not file an Ubuntu bug myself because it was not clear whether the bug was in Ubuntu's octave3.0-headers or the Arpack package itself (which I obtained from your site because it doesn't have an Ubuntu package, possibly because of its nonfree status as most of the other OctaveForge packages are available in Ubuntu). ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Octave-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/octave-dev
