Back to main page ...The following sections show how Regina can be built successfully on various GNU/Linux distributions and other systems. These suggestions come from past experiences in building debian packages and RPMs on several different platforms.
|
As always, it is generally simpler just to download and install a binary package if you can. Take a look at the Regina download site and see if your distribution is supported.
Please also see the page on building from sources for system requirements and a general overview of the build process.
If these tips do not work for you, please send an email (including your config.log if possible) so that this page and/or the automatic configuration scripts can be updated to reflect systems like yours.
If your machine runs a 64-bit version of linux (the x86_64 or amd64 architectures) and you use an RPM-based distribution such as Fedora, Mandriva or SuSE, you may need to pass the following argument to the ./configure script:
example$ ./configure --enable-libsuffix=64
This enables ./configure to find the correct 64-bit development libraries in /usr/lib64/, and also ensures that files are installed in the correct final location.
If you are using a Debian-based distribution such as Debian or Ubuntu, you should not give this argument since 64-bit Debian places libraries directly in /usr/lib/.
The KDE user manuals are kept in a different directory, and so the users' handbook is sometimes installed where KDE cannot find it. Try passing the following additional argument to the ./configure script:
example$ ./configure kde_htmldir=/usr/share/doc/kde/HTML
If the ./configure script is having trouble locating your Qt/KDE installation, try the following:
example$ source /etc/profile.d/qt.sh
example$ ./configure
Users running the x86_64 architecture should also see the section on 64-bit systems.
Assuming you have installed Fink beneath /sw, you may need to pass the following arguments to ./configure to ensure that it can find the Fink libraries:
example$ ./configure --with-extra-includes=/sw/include --with-extra-libs=/sw/lib
In addition, the users' handbook is sometimes installed in the wrong location, which means the KDE Help Centre cannot find it. This can be fixed with the following additional argument:
example$ ./configure --with-extra-includes=/sw/include --with-extra-libs=/sw/lib kde_htmldir=/sw/share/doc/kde
If the ./configure script is having trouble locating your Qt/KDE installation, try the following:
example$ export QTDIR=/usr/lib/qt3/
example$ ./configure
Users running the x86_64 architecture should also see the section on 64-bit systems.
Because SuSE installs KDE beneath /opt, you might need to pass several arguments to the ./configure script to ensure that the KDE parts of Regina are installed where KDE can find them, and the non-KDE parts of Regina are installed in a more standard location.
The arguments used by the author to build the SuSE packages include:
example$ ./configure --prefix=/opt/kde3 --includedir=/usr/include --mandir=/usr/share/man
In addition, if you wish to build the MPI utilities (assuming you have mpich-devel installed), you may need the following additional argument:
example$ ./configure --prefix=/opt/kde3 --includedir=/usr/include --mandir=/usr/share/man MPICXX=/opt/mpich/ch-p4/bin/mpicxx
Users running the x86_64 architecture should also see the section on 64-bit systems.
If you use SuSE 11.0 then you will need to upgrade your boost and boost-devel packages through SuSE's online update. This is because the boost packages originally shipped with SuSE 11.0 were broken.
The KDE user manuals are kept in a different directory, and so the users' handbook is sometimes installed where KDE cannot find it. Try passing the following additional argument to the ./configure script:
example$ ./configure kde_htmldir=/usr/share/doc/kde/HTML