octave_config -p [EXEC_]PREFIX

[Javier Fernandez]

Hi,

Should I use PREFIX or EXEC_PREFIX?

I have just noticed that the command
octave-config -p PREFIX
which I used in startup runcommands (to get something such as 
/home/user/octave-2.1.73 for instance) now returns the empty string. 
There is an easy workaround, using EXEC_PREFIX (which returns something 
like /home/user/octave-2.9.10) instead of PREFIX.

Perhaps the meaning of those variables is inherited from ./configure?
--------------------------
Installation directories:
  --prefix=PREFIX         install architecture-independent files in PREFIX
                          [/usr/local]
  --exec-prefix=EPREFIX   install architecture-dependent files in EPREFIX
                          [PREFIX]
--------------------------
I have never done a multi-architecture octave installation, please bear 
with me if this is a silly question.

I've been comparing the scripts for both versions, and perhaps PREFIX 
would return the same previous value if a different name was chosen for 
the intermediate variable used in the newly added code at lines 45 and on
--------------------------
if [ -n "$OCTAVE_HOME"]
[...]
fi
PREFIX="$OCTAVE_HOME"
--------------------------

Particularly, I used the variable to generate/store/locate the Doxygen 
documentation, such as in
--------------------------
export OCTAVE=`$octave_config --print EXEC_PREFIX`
...
export OCT_DOX=$OCTAVE/include/html/index.html
--------------------------
Such files should go in architecture-independent subdirs? Anyways, as 
long as EXEC_PREFIX works, I can use it. I think most people will make 
single-architecture octave builds, and with equal PREFIX and EXEC_PREFIX 
dirs. Is that right?

-javier