501
edits
Compiling on OpenBSD: Difference between revisions
Jump to navigation
Jump to search
no edit summary
(List detailed instructions for building on OpenBSD) |
No edit summary |
||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 12: | Line 12: | ||
pkg_add autoconf automake bison gperf libtool | pkg_add autoconf automake bison gperf libtool | ||
== Workarounds for Building from Mercurial == | |||
If building from a Mercurial clone, the source tree must first be bootstrapped. This relies on the additional GNU tools listed above. This step also requires the gnulib library to exist as a subdirectory of the Octave tree, or by passing <tt>--gnulib-srcdir</tt> to the bootstrap script. | |||
./bootstrap | |||
There is a problem with the OpenBSD libtool package that fails to build Octave without some tweaks. After successfully running bootstrap, the <tt>build-aux/ltmain.sh</tt> shell script must be replaced with one from another system, for example from the Debian GNU/Linux libtool package. | |||
And lastly, the versions of bison and flex available on OpenBSD are too old to work with features used by Octave. Newer versions will have to be installed, or the files produced by those tools need to be copied from another system. The files produced by bison and flex are normally distributed with the source archive, so this is only a problem with attempting to build from the Mercurial repository. | |||
== Configuring and Compiling Octave == | == Configuring and Compiling Octave == | ||
| Line 34: | Line 44: | ||
--disable-docs | --disable-docs | ||
Before compiling, the process limit for data segment size needs to be increased to enable the compiler to handle certain files in Octave's code base. This is done with the ulimit command before starting the build. So, once configured as above, run | |||
ulimit -d 8388608 | |||
gmake | |||
gmake check | |||
to compile Octave and run the test suite. | |||
[[Category:Building]] | |||