32
edits
Octave in home directory: Difference between revisions
Jump to navigation
Jump to search
m
update version number from 3.8.0 to 3.8.2
(THE LFS way) |
m (update version number from 3.8.0 to 3.8.2) |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 12: | Line 12: | ||
== 2. Download Octave Sourcecode == | == 2. Download Octave Sourcecode == | ||
Take a release from ftp.gnu.org, e.g. 3.8. | Take a release from ftp.gnu.org, e.g. 3.8.2. | ||
wget ftp://ftp.gnu.org/gnu/octave/octave-3.8. | wget ftp://ftp.gnu.org/gnu/octave/octave-3.8.2.tar.bz2 | ||
tar xfvj octave-3.8. | tar xfvj octave-3.8.2.tar.bz2 | ||
cd octave-3.8. | cd octave-3.8.2/ | ||
or clone current development branch | or clone current development branch | ||
| Line 32: | Line 32: | ||
./configure --prefix=/home/maxpower/.octave38/ | ./configure --prefix=/home/maxpower/.octave38/ | ||
An alternative is presented in section 6. Use it if you intent to compile from yourself many packages. | |||
Pay attention to the configure summary at the end (See chapter 1), install missing required packages if any. | Pay attention to the configure summary at the end (See chapter 1), install missing required packages if any. | ||
| Line 57: | Line 57: | ||
== 6. Managing your own program hierarchy | == 6. Managing your own program hierarchy (optional) == | ||
If you | 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 | # set LD_LIBRARY_PATH if not set | ||
| Line 67: | Line 71: | ||
(echo $PATH | grep -q $HOME/usr/bin) || export PATH="$HOME/bin:$HOME/usr/bin:$HOME/usr/local/bin:$PATH" | (echo $PATH | grep -q $HOME/usr/bin) || export PATH="$HOME/bin:$HOME/usr/bin:$HOME/usr/local/bin:$PATH" | ||
fi | fi | ||
# set MANPATH so it includes user's private bin if it exists | # set MANPATH so it includes user's private bin if it exists | ||
if [ -d "$HOME/usr/share/man" ] ; then | 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`" | (echo $MANPATH | grep -q $HOME/usr/share/man) || export MANPATH="$HOME/usr/local/share/man:$HOME/usr/share/man:`manpath -q`" | ||
fi | fi | ||
if [ -d "$HOME/usr/share/info" ]; then | if [ -d "$HOME/usr/share/info" ]; then | ||
export INFOPATH="$INFOPATH:$HOME/usr/share/info" | export INFOPATH="$INFOPATH:$HOME/usr/share/info" | ||
fi | fi | ||
if [ -d "$HOME/usr/lib/python" ]; then | 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" | (echo $PYTHONPATH | grep -q $HOME/usr/lib/python) || export PYTHONPATH="$HOME/usr/local/lib/python:$HOME/usr/lib/python" | ||
fi | fi | ||
if [ -d "$HOME/usr/lib/pkgconfig" ]; then | 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" | (echo $PKG_CONFIG_PATH | grep -q $HOME/usr/lib/pkgconfig) || export PKG_CONFIG_PATH="$HOME/usr/lib/pkgconfig" | ||
fi | fi | ||
This way, most ordinary commands like "man octave", "info octave", or launching octave itself, will first explore your own hierachy. | |||
== Uninstall == | == Uninstall == | ||