default path to oct files

[John W. Eaton]

On 10-Jul-2008, JF Cardoso wrote:

| John W. Eaton wrote:
| > On 10-Jul-2008, JF Cardoso wrote:
| > 
| > | 
| > | John W. Eaton wrote:
| > | > 
| > | > Does the /usr/local/libexec/octave/site/oct/api-v32/i686-pc-linux-gnu
| > | > directory exist on your system?
| > | 
| > | Yes it does, but maybe it has been created not at octave install time
| > | but when I installed my own oct files there: this is done via a
| > | Makefile with the following relevant lines:
| > 
| > OK, so once the directory exists, isn't it added to the load path
| > automatically?  Or do you need to add it with addpath?
| 
| It is not added automatically.  I need a specific addpath command.
| This is only with 3.0.1, not with 3.0.0 :
| 
| $ octave-3.0.1 --no-init-file --eval "path ; " | grep libexec
| /usr/local/libexec/octave/3.0.1/oct/i686-pc-linux-gnu
| 
| $ octave-3.0.0 --no-init-file --eval "path ; " | grep libexec
| /usr/local/libexec/octave/site/oct/api-v32/i686-pc-linux-gnu
| /usr/local/libexec/octave/3.0.0/oct/i686-pc-linux-gnu
| 
| 
| > On my system, with the current sources, Octave will add the
| > directory to the path automatically if it exists.  I don't need to
| > use addpath.
| 
| I would happily try with the current sources but the hg version does
| not compile for me at this time.  However, this is another story.

It works for me with the Debian Octave 3.0.1 package.  If it is a
problem for you, then perhaps you can debug it?

jwe