1,860
edits
(→Pre-compiled binaries: Merged subsections. PPA is not up-to-date, so don't make hope to find newer versions there.) |
(→Compiling from source: Information reorganization. Flatten the TOC.) |
||
Line 21: | Line 21: | ||
The only ''tricky'' part is to install the dependencies. Once that is solved, installing from source should be as easy as {{Codeline|./configure && make && make install}}. See the manual for the [http://www.gnu.org/software/octave/doc/interpreter/Running-Configure-and-Make.html configure options]. | The only ''tricky'' part is to install the dependencies. Once that is solved, installing from source should be as easy as {{Codeline|./configure && make && make install}}. See the manual for the [http://www.gnu.org/software/octave/doc/interpreter/Running-Configure-and-Make.html configure options]. | ||
=== | === Install dependencies === | ||
Note that different Debian and Ubuntu versions may have slightly different package names but their differences should be pretty small, mostly limited to version numbers. | |||
The | ==== The easy way (but possibly incomplete) ==== | ||
The easy way to install ''most'' of the necessary dependencies is to {{Codeline|sudo apt-get build-dep octave}}. This will install all packages necessary to build and prepare a Debian package for the octave version available on your system repositories. However: | The easy way to install ''most'' of the necessary dependencies is to {{Codeline|sudo apt-get build-dep octave}}. This will install all packages necessary to build and prepare a Debian package for the octave version available on your system repositories. However: | ||
* will install unnecessary packages related to the building of a Debian package; | * will install unnecessary packages related to the building of a Debian package; | ||
Line 41: | Line 34: | ||
==== The even easier way ==== | ==== The even easier way ==== | ||
The [ | The [[MXE|MXE-octave]] package provides a way to compile Octave for different platforms. Dependencies and certain flags are handled automatically. | ||
==== The right way ==== | ==== The right way ==== | ||
The best way is to select and install all the dependencies as listed in the {{Path|INSTALL.OCTAVE}} file. The following are their package names in Debian repositories (they will have their own dependencies which your package maintainer will solve automatically). If you are building development versions, you'll require some more packages as listed on {{Path|etc/HACKING}} and {{Path|INSTALL}}. Many of them will already be installed on your system. | |||
{{ | |||
* build tools | * build tools | ||
:<pre>g++ gcc gfortran make</pre> | :<pre>g++ gcc gfortran make</pre> | ||
* build tools (development version) | |||
:<pre>autoconf automake bison flex gperf gzip icoutils librsvg2-bin libtool perl rsync tar</pre> | |||
* external packages | * external packages | ||
:<pre>libblas-dev liblapack-dev libpcre3-dev</pre> | :<pre>libblas-dev liblapack-dev libpcre3-dev</pre> | ||
Line 122: | Line 113: | ||
|} | |} | ||
{{Note|if only the native graphics toolkit will be used, gnuplot will not be necessary.}} | |||
{{Warning|<ul><li>The Debian repositoriy has several libraries for dealing with HDF data files. The recommended is {{Codeline|libhdf5-serial-dev}}. However, the {{Forge|msh|msh package}} requires [http://www.geuz.org/gmsh/ gmsh] which is incompatible with it.</li> | |||
<li>The GraphicsMagick++ library (libgraphicsmagick++-dev) on the Debian repositories was compiled with quantum 8 which limits reading images to 8 bit. The solution is to recompile [[GraphicsMagick]] with quantum 16 or 32 before building Octave.</li></ul>}} | |||
=== | === Configuration === | ||
==== HDF5 issue ==== | |||
With current Debian versions you may get the following when building from source: | |||
HDF5 library not found. Octave will not be able to save or load HDF5 data files. | |||
The problem is that there are multiple versions of the hdf5 package. Octave was written with the serial version in mind but it is likely to work with the others (OpenMPI and Mpich). Due to the naming scheme done in Debian, it is required to specify the location of the libraries. See bug {{bug|38928}} for details but basically, use the following when running configure: | |||
./configure CPPFLAGS=-I/usr/include/hdf5/serial LDFLAGS=-L/usr/lib/$(dpkg-architecture -qDEB_HOST_MULTIARCH)/hdf5/serial | |||
[[Category:Building]] | [[Category:Building]] | ||
[[Category:Installation]] | [[Category:Installation]] | ||
[[Category:Debian]] | [[Category:Debian]] |