Building Mozilla on Unix platforms
Daniel Nunes, firstname.lastname@example.org 1.1, June 1998
How to build Mozilla on a Unix System.
- 2.1 Get the Code
- 2.2 Requirements
- 2.3 Set up the Build Environment
- 2.4 Build the Lizard
- 2.5 Run the Lizard
What this document is: A guide to building the Mozilla application.
- A listing of the development tools you will need to build Mozilla.
- A list of environment variables you will need to set before building.
- Each of the following subsections describes, or gives references to
descriptions of, the steps necessary to build Mozilla.
There are two principal ways of getting the code,
CVS will provide the most current code for building, but is
slower than ftp. Ftp drops are generally produced once per month,
and are known to compile.
The following should be installed:
- Motif 1.2
- The native C/C++ compiler (or GNU C/C++ compiler 2.7.2 in lieu of the native compiler)
- GNU make 3.74 or better
- Perl (or, if you have no Perl, then set
Your hardware should be equal to, or better than:
32 MB RAM, 128 MB swap (64 MB RAM recommended)
The following environment variables need to be set:
Optionally, you can setMOZILLA_CLIENT=1 MOZ_MEDIUM=1 NO_MDUPDATE=1
BUILD_OPT=1if you don't want a debug build.
If your Motif libraries are installed in a non-standard place, you can tell
the Mozilla makefiles where to look by setting
MOZILLA_MOTIF_SEARCH_PATH to point to the directory in which
your Motif installation resides.
Environment variables are set by the shell, and there are two common ways
of setting them.
setenv VARIABLE value or
Change to the directory you copied the source into (for example,
cd /builds). If this directory was empty before you installed the source, there should be two directories here:
cd mozilla gmake
You may notice that if you try running mozilla-export right after the build,
you'll run into a problem. You need to set
- On HP-UX, the equivalent environment variable is
- On AIX, the equivalent environment variable is
PATH_TO_SOURCEis the full path to your source tree) before the dynamically linked binary will run.
This varies by platform:
- If this error occurs, you might have to recompile libX11.so
with the -DX_LOCALE flag (thanks to Scott Lampert,