Re: A question about OCTAVE_BINDIR

[John W. Eaton]

On 11/16/2013 11:33 AM, Julien Bect wrote:
> On 16/11/2013 15:58, Mike Miller wrote:
> > On Sat, Nov 16, 2013 at 14:37:57 +0100, Julien Bect wrote:
> > > >If I start Octave after a fresh build (with run-octave) and try to
> > > build a
> > > >MEX-file, I get the following error :
> > > >
> > > >     error: mkoctfile: unable to find the mkoctfile command, Octave
> > > >installation is incomplete
> > Expected behavior, the mex, mkoctfile, and pkg install commands all
> > require you to have done a "make install" of Octave before using them.
>
> Are you sure about that ? Because in run-octave I can see :
>
>      OCTAVE_BINDIR="$builddir/src"
>
> Doesn't it mean that octave_config_info ("bindir") should return
>
>      /media/data/sources/octave/core/src
>
> (this is what getenv ('OCTAVE_BINDIR') returns) ?
>
> Otherwise, what is the point of this line in run-octave ?

Mike is right, it's not expected that Octave is fully functional when 
running in the build directory tree.

If you want to work on fixing that, then great, but I don't really 
consider it a bug.

If you want everything to work properly, run make install first.  For 
testing, you can always use the --prefix option when you configure 
Octave so that it will install to a non-system directory.

jwe