From bug-request at octave dot org Mon Mar 27 13:32:11 2006
Subject: Re: Problems after building octave-forge-2.1.73 on Mac OS X
From: "John W. Eaton" <jwe at bevo dot che dot wisc dot edu>
To: Joe Koski <jkoski11 at comcast dot net>
Cc: "bug at octave dot org" <bug@octave.org>
Date: Mon, 27 Mar 2006 14:31:53 -0500

On 27-Mar-2006, Joe Koski wrote:

| My standard practice is to "make clean" before I ./configure octave-forge.
| In this particular case, I think I actually used a fresh copy of
| octave-forge from the octave-forge-2006.03.17 tar file for the build. I also
| didn't mention that I did the entire build first with all the bells and
| whistles (vecLib, g95), and had the same problem, then cut back and rebuilt
| everything from scratch with the bare bones "./configure --enable-shared
| --disable-static" with a second build of octave-2.1.73.
| 
| I still think the //PKG_ADD is a clue.

I think that is just happening because the code that searches for
these files is adding an extra directory separator.

What is the output of

  file_in_loadpath ("dispatch.oct")

?

jwe



-------------------------------------------------------------
Octave is freely available under the terms of the GNU GPL.

Octave's home on the web:  http://www.octave.org
How to fund new projects:  http://www.octave.org/funding.html
Subscription information:  http://www.octave.org/archive.html
-------------------------------------------------------------