On Wed, Oct 24, 2012 at 4:32 AM, Sébastien Villemot wrote: > It appears that octave 3.6.2 does not work with liboctave1 3.6.3, and > conversely octave 3.6.3 does not work with liboctave1 3.6.2.
I took a look at this and the problem is simply that the load path contains Octave's version number. No soname incompatibility. And unless something is changed, this will continue to be the case between different upstream versions of octave and liboctaveX. The octave package provides the directories, and liboctinterp.so.1 has a compiled-in set of paths with its version number that it attempts to load. You can see these paths with: $ strings /usr/lib/x86_64-linux-gnu/liboctinterp.so.1 | grep /3.6../ If I print the default path from a working 3.6.3: $ octave -qf --eval "disp(path)" then downgrade liboctave1/sid and set that full string to be the path in the interpreter: $ octave -qf octave:1> ls error: feval: function `unimplemented' not found octave:1> path (full_path_here); octave:2> ls no more error. -- mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
