From: Etienne G. <et...@is...> - 2002-11-02 10:08:16
|
Hello, just to say that the "not a valid shared library" error disappeared w/ 2.1.39. I'm puzzled. Cheers, Etienne On Thu, Oct 31, 2002 at 02:13:20PM +0000, Etienne Grossmann wrote: # # # Hello, # # I am having a problem w/ my octave-forge installation (from cvs) and # am asking for advice, siggestions & tips. # # I installed octave-2.1.38 from source this morning. Compilers are # (exported environment variables) CC=gcc-3.0, CXX=g++-3.0 and # F77=g77-3.0. # # make clean ; ./configure ; make # # When make failed with a problem in fsolve.cc, I "fixed" it with # # cp FIXES/kron.oct FIXES/fsolve.oct # # and then make worked. # # Then I start octave and put my octave-forge cvs tree in the search # path and check about an oct-file defined in octave-forge : # # octave:2> which leval # error: /home/etienne/prog/octave/octave-forge/octave-forge/main/optim/leval.oct is not a valid shared libr # which: `leval' is undefined # # Same for other .oct files (bitor, delaunayn, getfield ...). # # I had the same problem with gcc-2.95 (and corresponding g++ and # f77). # # Linux is Debian 3.0 # # Any ideas on what the problem is? # # Etienne # # I # # -- # Etienne Grossmann ------ http://www.isr.ist.utl.pt/~etienne # # -- Etienne Grossmann ------ http://www.isr.ist.utl.pt/~etienne |