Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in or
create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision |
Your text |
Line 1: |
Line 1: |
| {{Warning|This page is outdated (October 2019). For more recent information, see [[Octave for other Unix systems]].}}
| |
|
| |
| This page lists specific instructions and issues with compiling the current development version of Octave on OpenBSD. The goal is for the issues listed here to be resolved so that compiling Octave on OpenBSD is as easy as it is for GNU/Linux and other Unixes. | | This page lists specific instructions and issues with compiling the current development version of Octave on OpenBSD. The goal is for the issues listed here to be resolved so that compiling Octave on OpenBSD is as easy as it is for GNU/Linux and other Unixes. |
|
| |
|
Line 14: |
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 46: |
Line 34: |
| --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
| | If building from a mercurial clone, the source tree must be bootstrapped before running configure. This requires the gnulib library to exist as a subdirectory of the Octave tree, or by passing <tt>--gnulib-srcdir</tt> to the bootstrap script. Some portability issues with gnulib on OpenBSD are currently being worked on, but once that is all worked out the version of gnulib mirrored in Octave's mercurial repository should work. |
| | |
| ulimit -d 8388608
| |
| gmake
| |
| gmake check
| |
| | |
| to compile Octave and run the test suite.
| |
| | |
| [[Category:Outdated pages]]
| |