|
|
(4 intermediate revisions by 2 users not shown) |
Line 1: |
Line 1: |
| Installing in your home directory is a method to install GNU Octave next to your repository installation at the same time. This works with every Linux distribution and is especially for old Ubuntu LTS versions very useful!
| | #REDIRECT [[Building]] |
| | |
| One advantage is that you do not clutter your system by running ''sudo make install''.
| |
| Another advantage is that you can keep your Octave installation that is provided by your distribution.
| |
| | |
| == 1. Install dependencies ==
| |
| | |
| Take a look at [[Building for Linux systems]] and [[Building]].
| |
| | |
| General information you can gather from the `./configure` summary or read the {{Path|INSTALL.OCTAVE}} file that comes distributed with Octave.
| |
| | |
| == 2. Download Octave Sourcecode ==
| |
| | |
| Take a release from ftp.gnu.org, e.g. 3.8.0.
| |
| | |
| wget ftp://ftp.gnu.org/gnu/octave/octave-3.8.0.tar.bz2
| |
| tar xfvj octave-3.8.0.tar.bz2
| |
| cd octave-3.8.0/
| |
| | |
| or clone current development branch
| |
| | |
| hg clone http://hg.octave.org/octave/
| |
| cd octave/
| |
|
| |
| | |
| == 3. configure ==
| |
| | |
| Only if you want to install from mercurial ''(hg.octave.org)'', you have to do first:
| |
| ./bootstrap
| |
| | |
| Now it's time to run ./configure with a prefix that points to a directory in your home directory. E.g., my username is ''maxpower'' and I want to install Octave to ''~/.octave38/''
| |
| ./configure --prefix=/home/maxpower/.octave38/
| |
| | |
| Another way, if you intend to compile for yourself a lot of utilities, is to mirror the main /usr structure into your own dir:
| |
| ./configure --prefix=${HOME}/usr
| |
| Pay attention to the configure summary at the end (See chapter 1), install missing required packages if any.
| |
| | |
| == 4. make & make install ==
| |
| | |
| After you have successful configured octave without errors ''(warnings may be okay)'', you can run ''make''. If you have a dual core CPU, you can run make with two threads like that (increase -j number if you have more CPU cores).
| |
| make -j2
| |
| This may take now ~30-300 Minutes (depends on the speed of your cpu and the size of your RAM)
| |
| | |
| Feel free to run ''make check'' too.
| |
| | |
| When ''make -j2'' finished without errors, simply run '''without''' sudo/root permissions
| |
| make install
| |
| Octave will now be installed to either /home/maxpower/.octave38/, either ${HOME}/usr
| |
| | |
| | |
| == 5. create a smart bashrc entry ==
| |
| | |
| echo "alias octave38='~/.octave38/bin/octave'" >> ~/.bashrc
| |
| . ~/.bashrc # this will update your bashrc without doing logout and login!
| |
| | |
| If you simply enter ''octave'', you'll start your repository installation provided by your distribution. But when you enter ''octave38'', you'll start your new snappy octave version installed to your home directory.
| |
| | |
| | |
| == 6. Managing your own program hierarchy
| |
| If you want your own set of programs, a few commands in your .profile will help:
| |
| | |
| # 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"
| |
| fi
| |
| | |
| # export MANPATH="$MANPATH:/usr/local/teTeX/man"
| |
| # 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`"
| |
| fi
| |
| | |
| if [ -d "$HOME/usr/share/info" ]; then
| |
| export INFOPATH="$INFOPATH:$HOME/usr/share/info"
| |
| fi
| |
| | |
| 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"
| |
| fi
| |
| | |
| 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"
| |
| fi
| |
| | |
| | |
| | |
| | |
| | |
| == Uninstall ==
| |
| | |
| ==== Method A ====
| |
| | |
| If you're still have the compiled source folder, just do ''make uninstall'' from it. And don't forget to remove the ''alias octave38'' entry in your ''~/.bashrc''.
| |
| | |
| ==== Method B ====
| |
| | |
| Just delete (e.g. ''rm -rf ~/.octave38/'') the install folder and remove the ''alias octave38'' entry from your ''~/.bashrc''.
| |
| | |
| | |
| [[Category:Building]] | |
| [[Category:Installation]]
| |