Jump to navigation Jump to search


1,526 bytes removed, 23:08, 27 October 2019
Strip subsection in favor of MXE.
In any case, don't forget to remove any created ''alias'' entries in {{Path|~/.bashrc}}.
=== Managing your own program hierarchy (optional) ===
If you intend to compile for yourself a lot of utilities, you may use a specific "usr" hierachy into your own dir (Linux from scratch way). Go back to step 2, and configure octave as:
./configure --prefix=${HOME}/usr
The other steps (make; make install) do not change. In order to use your own hierachy, you should set a few environment variables in your .profile:
# set LD_LIBRARY_PATH if not set
(echo $LD_LIBRARY_PATH | grep -q lib) || export LD_LIBRARY_PATH="/usr/local/lib:$HOME/usr/lib:$HOME/usr/local/lib"
# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/bin" ] ; then
(echo $PATH | grep -q $HOME/usr/bin) || export PATH="$HOME/bin:$HOME/usr/bin:$HOME/usr/local/bin:$PATH"
# set MANPATH so it includes user's private bin if it exists
if [ -d "$HOME/usr/share/man" ] ; then
(echo $MANPATH | grep -q $HOME/usr/share/man) || export MANPATH="$HOME/usr/local/share/man:$HOME/usr/share/man:`manpath -q`"
if [ -d "$HOME/usr/share/info" ]; then
export INFOPATH="$INFOPATH:$HOME/usr/share/info"
if [ -d "$HOME/usr/lib/python" ]; then
(echo $PYTHONPATH | grep -q $HOME/usr/lib/python) || export PYTHONPATH="$HOME/usr/local/lib/python:$HOME/usr/lib/python"
if [ -d "$HOME/usr/lib/pkgconfig" ]; then
(echo $PKG_CONFIG_PATH | grep -q $HOME/usr/lib/pkgconfig) || export PKG_CONFIG_PATH="$HOME/usr/lib/pkgconfig"
This way, most ordinary commands like "man octave", "info octave", or launching octave itself, will first explore your own hierachy.
== See also ==
* [ <code>README</code>] and [ <code>/etc/</code>] in the development repository.
* [[MXE]] -- a more customized Octave build including many self-compiled tools.
== Footnotes ==

Navigation menu