On Sat, Jan 26, 2013 at 9:52 AM, Jérémy Lal wrote:
On 24 October 2012 08:17, Mike Miller mtmil...@ieee.org wrote:
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.
Ah, this is probably not the
On 24 October 2012 08:17, Mike Miller mtmil...@ieee.org wrote:
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.
Ah, this is probably not the greatest idea ever. I'm not sure how to
fix it.
Processing control commands:
severity -1 serious
Bug #691311 [octave] error: feval: function `unimplemented' not found
Severity set to 'serious' from 'normal'
tags -1 + confirmed
Bug #691311 [octave] error: feval: function `unimplemented' not found
Added tag(s) confirmed.
--
691311: http
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
On 24 October 2012 08:17, Mike Miller mtmil...@ieee.org wrote:
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.
Ah, this is probably not the greatest idea ever. I'm not sure how to
fix it.
5 matches
Mail list logo
