[Pkg-octave-devel] definitions of pathdef not taken into path

[Thomas Weber]

Hi, 

we are currently hitting a bug in Debian[1] with Octave 3.0.1. At startup,
octave complains about not finding cellfun(). This is due to the
lib-path (/usr/lib/octave/3.0.1/oct/x86_64-pc-linux-gnu) not being added
to the loadpath, so none of Octave's .oct files can be found by the
interpreter. 

$ octave --norc
...

octave:1> pathdef
ans =
/usr/lib/octave/3.0.1/oct/x86_64-pc-linux-gnu:/usr/share/octave/3.0.1/m:/usr/share/octave/3.0.1/m/optimization:...

octave:2> path
/usr/share/octave/3.0.1/m ... 
(no library path here, only subdirectories of the /u/s/o/3.0.1/m/ path)

The biggest problem is that this seems to be a Heisen-bug: I can
reproduce it, Rafael cannot. If you start Octave at the root directory
('/'), it works; if you start it in an empty sub-directory, it doesn't.
If I install Octaviz, the lib-path is added to the loadpath at startup
(and Octaviz does nothing to any configuration file, it just drops its
.oct files in a subdirectory).
Some users reported that they see this on one machine, but not on
another. However, 3.0.0 had a leading double colon at the beginning of
pathdef, so I suspect that rev 4ff9611147ba might be responsible.

[1] http://bugs.debian.org/477556

	Thomas