Am Donnerstag, den 17.08.2006, 09:59 +1000 schrieb John Dalton: > After this fresh reinstall, symptoms are still present as before: > $ mkoctfile -v uitest.cc > g++ -c -fPIC -I/usr/include/octave-2.9.7 > -I/usr/include/octave-2.9.7/octave -m32 uitest.cc -o uitest.o > /usr/bin/g++ -shared -Wl,-Bsymbolic -o uitest.oct uitest.o > -L/usr/lib/octave-2.9.7 -loctinterp -loctave -lcruft -m32 -llapack-3 > -lblas-3 -lfftw3 -lreadline -lncurses -ldl -lhdf5 -lz -lm > -L/usr/lib/gcc/x86_64-linux-gnu/4.1.2 > -L/usr/lib/gcc/x86_64-linux-gnu/4.1.2/../../../../lib64 -L/lib/../lib64 > -L/usr/lib/../lib64 -lhdf5 -lz -lgfortranbegin -lgfortran -lm -lgcc_s > /usr/bin/ld: skipping incompatible /usr/lib/octave-2.9.7/liboctinterp.so > when searching for -loctinterp > /usr/bin/ld: cannot find -loctinterp > collect2: ld returned 1 exit status
There's something weird going on here. mkoctfile from the Debian package calls g++ with its full path. Additionally, we don't pass the "-m32" flag to the compiler. For comparision, the output in my chroot: # mkoctfile -v uitest.cc /usr/bin/g++ -c -fPIC -I/usr/include/octave-2.9.7 -I/usr/include/octave-2.9.7/octave -O2 uitest.cc -o uitest.o /usr/bin/g++ -shared -Wl,-Bsymbolic -o uitest.oct uitest.o -L/usr/lib/octave-2.9.7 -loctinterp -loctave -lcruft -s -llapack-3 -lblas-3 -lfftw3 -lreadline -lncurses -ldl -lhdf5 -lz -lm -L/usr/lib/gcc/x86_64-linux-gnu/4.1.2 -L/usr/lib/gcc/x86_64-linux-gnu/4.1.2/../../../../lib64 -L/lib/../lib64 -L/usr/lib/../lib64 -lhdf5 -lz -lgfortranbegin -lgfortran -lm -lgcc_s Is it possible that you have a local installation of Octave coming in the way (i.e., that mkoctfile is not /usr/bin/mkoctfile)? Or that you have a mixed 32/64 bit environment? Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]