[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: A question about OCTAVE_BINDIR

From: John W. Eaton
Subject: Re: A question about OCTAVE_BINDIR
Date: Sat, 16 Nov 2013 12:23:02 -0500
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20131005 Icedove/17.0.9

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 :


Doesn't it mean that octave_config_info ("bindir") should return


(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.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]