mirror of
https://github.com/Mercury-Language/mercury.git
synced 2025-12-12 20:34:19 +00:00
README.Linux: Fix my confusion with autoconf options; using --host when cross-compiling is correct.
37 lines
1.2 KiB
Plaintext
37 lines
1.2 KiB
Plaintext
This file documents the Linux/x86 and Linux/x86_64 ports.
|
|
For the Linux/PowerPC port, see README.Linux-PPC.
|
|
For the Linux/Apha port, see README.Linux-Alpha.
|
|
(Ports to Linux on other architectures have not yet
|
|
been attempted, but should not be difficult.)
|
|
|
|
Linux systems that produce executables in a.out format are not supported by
|
|
the Mercury compiler.
|
|
|
|
|
|
BUILDING A 32-BIT MERCURY COMPILER ON 64-BIT LINUX
|
|
==================================================
|
|
|
|
To build a 32-bit Mercury compiler on 64-bit Linux, follow these steps:
|
|
|
|
(1) Ensure that the 32-bit (e.g. i686 etc) packages for the C compiler and
|
|
libraries are available on the build system.
|
|
|
|
(2) Ensure that you have a working Mercury compiler in your PATH
|
|
to bootstrap from.
|
|
|
|
(3) If the Mercury compiler in step (2) is a 64-bit compiler then add
|
|
the following line to a file named Mmake.params at the top-level
|
|
of the source tree:
|
|
|
|
MCFLAGS=--cross-compiling
|
|
|
|
If you are bootstrapping from an existing 32-bit compiler you
|
|
should not need to do this.
|
|
|
|
(4) Run aclocal -I m4; autoconf as normal. Then invoke configure
|
|
as follows:
|
|
|
|
$ ./configure --host=i686-pc-linux-gnu --with-cc="gcc -m32"
|
|
|
|
(5) Do mmake; mmake install as normal.
|