spurious load_path warnings when octave is started at Unix root directory

[John W. Eaton]

On 10-Sep-2008, Alexander Mamonov wrote:

| Bug report for Octave 3.0.2 configured for i486-pc-linux-gnu
| 
| Description:
| -----------
| 
| When Octave is started in Unix root directory, warnings from the
| load_path appear whenever the
| current directory is changed. On my machine the warning is
| warning: load_path:
| ./usr/lib/octave/site/oct/api-v32/i486-pc-linux-gnu: No such file or
| directory
| 
| If I type the path command, then the path
| ./usr/lib/octave/site/oct/api-v32/i486-pc-linux-gnu
| is indeed displayed as a relative path, unlike all other paths, which
| are displayed as absolute paths.
| 
| If Octave is started in any other directory, then no warnings appear,
| and in the output of the path command
| the path /usr/lib/octave/site/oct/api-v32/i486-pc-linux-gnu is
| displayed correctly as the absolute path.
| 
| Repeat-By:
| ---------
| 
| Start octave in unix root directory. Go to any other directory, for example
| cd home
| As a result the warning will appear
| warning: load_path:
| ./usr/lib/octave/site/oct/api-v32/i486-pc-linux-gnu: No such file or
| directory

I'm unable to reproduce this problem.  What do you mean by "Unix root
directory"?  Do you mean / or your home directory or something else?

What happens if you start Octave with --norc?

jwe