[Top][All Lists]

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

[Octave-bug-tracker] [bug #41296] build mkoctfile and octave-config as e

From: Mike Miller
Subject: [Octave-bug-tracker] [bug #41296] build mkoctfile and octave-config as executables on all platforms
Date: Fri, 24 Jan 2014 14:29:44 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.63 Safari/537.36

Follow-up Comment #15, bug #41296 (project octave):

Rik: only when running from inside of Octave, but these can be run from Forge
package configure scripts or Makefiles.

Thanks for cleaning that substitution code up. Here are the differences
between the old and new that I see now with this change. These are probably
good changes, just noting the slight differences now in case it does affect

$ mkoctfile-old -p OCTAVE_HOME
# empty string
$ ./src/mkoctfile -p OCTAVE_HOME
$ export OCTAVE_HOME=/foo
$ octave-config-old -p PREFIX
$ ./src/octave-config -p PREFIX

So in other words, octave-config now keeps PREFIX to the compiled-in
directory, it used to substitute OCTAVE_HOME into the PREFIX variable as well.
And mkoctfile now prints the value of PREFIX when OCTAVE_HOME is requested but
it is not in the environment.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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