0N/A<!
DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
11N/A <
title>OpenJDK Build README</
title>
11N/A <
body style="background-color:lightcyan">
11N/A <!-- ====================================================== --> 39N/A <
table width="100%">
11N/A <
td align="center">
11N/A <
h1>OpenJDK Build README</
h1>
11N/A <!-- ------------------------------------------------------ --> 11N/A <
h2><
a name="introduction">Introduction</
a></
h2>
11N/A This README file contains build instructions for the
11N/A Building the source code for the
11N/A a certain degree of technical expertise.
11N/A <!-- ------------------------------------------------------ --> 11N/A <
h2><
a name="contents">Contents</
a></
h2>
11N/A <
li><
a href="#introduction">Introduction</
a></
li>
11N/A <
li><
a href="#MBE">Minimum Build Environments</
a></
li>
11N/A <
li><
a href="#SDBE">Specific Developer Build Environments</
a></
li>
39N/A <
li><
a href="#fedora">Fedora Linux</
a> </
li>
39N/A <
li><
a href="#centos">CentOS Linux</
a> </
li>
39N/A <
li><
a href="#ubuntu">Ubuntu Linux</
a> </
li>
11N/A <
li><
a href="#directories">Source Directory Structure</
a> </
li>
11N/A <
li><
a href="#building">Build Information</
a>
11N/A <
li><
a href="#gmake">GNU Make (<
tt><
i>gmake</
i></
tt>)</
a> </
li>
11N/A <
li><
a href="#linux">Basic Linux System Setup</
a> </
li>
11N/A <
li><
a href="#solaris">Basic Solaris System Setup</
a> </
li>
11N/A <
li><
a href="#windows">Basic Windows System Setup</
a> </
li>
11N/A <
li><
a href="#dependencies">Build Dependencies</
a> </
li>
11N/A <
li><
a href="#bootjdk">Bootstrap JDK</
a> </
li>
11N/A <
li><
a href="#binaryplugs">Binary Plugs</
a> </
li>
11N/A <
li><
a href="#importjdk">Optional Import JDK</
a> </
li>
23N/A <
li><
a href="#ant">Ant</
a> </
li>
11N/A <
li><
a href="#cacerts">Certificate Authority File (cacert)</
a> </
li>
11N/A <
li><
a href="#compilers">Compilers</
a>
11N/A <
li><
a href="#msvc">Microsoft Visual Studio</
a> </
li>
11N/A <
li><
a href="#mssdk">Microsoft Platform SDK</
a> </
li>
11N/A <
li><
a href="#studio">Sun Studio</
a> </
li>
11N/A <
li><
a href="#zip">Zip and Unzip</
a> </
li>
11N/A <
li><
a href="#freetype">FreeType2 Fonts</
a> </
li>
11N/A <
li>Linux and Solaris:
11N/A <
li><
a href="#cups">CUPS Include files</
a> </
li>
11N/A <
li><
a href="#alsa">ALSA files</
a> </
li>
11N/A <
li>Unix Command Tools (<
a href="#cygwin">CYGWIN</
a>)</
li>
11N/A <
li><
a href="#dxsdk">DirectX 9.0 SDK</
a> </
li>
11N/A <
li><
a href="#creating">Creating the Build</
a> </
li>
11N/A <
li><
a href="#testing">Testing the Build</
a> </
li>
11N/A <
li><
a href="#troubleshooting">Troubleshooting</
a></
li>
11N/A <!-- ------------------------------------------------------ --> 11N/A <
h2><
a name="MBE">Minimum Build Environments</
a></
h2>
11N/A This file often describes specific requirements for what we call the
11N/A "minimum build environments" (MBE) for the JDK.
11N/A Building with the MBE will generate the most compatible
11N/A bits that install on, and run correctly on, the most variations
11N/A of the same base OS and hardware architecture.
11N/A These usually represent what is often called the
11N/A least common denominator platforms.
11N/A It is understood that most developers will NOT be using these
11N/A specific platforms, and in fact creating these specific platforms
11N/A may be difficult due to the age of some of this software.
11N/A The minimum OS and C/C++ compiler versions needed for building the
11N/A <
th>Base OS and Architecture</
th>
11N/A <
td>Linux X86 (32bit)</
td>
11N/A <
td>Red Hat Enterprise Linux 4 </
td>
11N/A <
td>Linux X64 (64bit)</
td>
11N/A <
td>Red Hat Enterprise Linux 4 </
td>
11N/A <
td>Solaris SPARC (32bit)</
td>
11N/A <
td>Solaris 10 + patches
11N/A SunSolve</
a> for patch downloads.
28N/A <
td>Sun Studio 12</
td>
11N/A <
td>Solaris SPARCV9 (64bit)</
td>
11N/A <
td>Solaris 10 + patches
11N/A SunSolve</
a> for patch downloads.
28N/A <
td>Sun Studio 12</
td>
11N/A <
td>Solaris X86 (32bit)</
td>
11N/A <
td>Solaris 10 + patches
11N/A SunSolve</
a> for patch downloads.
28N/A <
td>Sun Studio 12</
td>
11N/A <
td>Solaris X64 (64bit)</
td>
11N/A <
td>Solaris 10 + patches
11N/A SunSolve</
a> for patch downloads.
28N/A <
td>Sun Studio 12</
td>
11N/A <
td>Windows X86 (32bit)</
td>
11N/A <
td>Windows XP</
td>
11N/A <
td>Microsoft Visual Studio .NET 2003 Professional</
td>
11N/A <
td>Windows X64 (64bit)</
td>
11N/A <
td>Windows Server 2003 - Enterprise x64 Edition</
td>
11N/A <
td>Microsoft Platform SDK - April 2005</
td>
11N/A <!-- ------------------------------------------------------ --> 11N/A <
h2><
a name="SDBE">Specific Developer Build Environments</
a></
h2>
11N/A We won't be listing all the possible environments, but
11N/A we will try to provide what information we have available to us.
11N/A <!-- ------------------------------------------------------ --> 39N/A <
h3><
a name="fedora">Fedora 9</
a></
h3>
39N/A you need to make sure you have
39N/A the "Software Development" bundle installed, plus the
39N/A following packages:
39N/A <
li>cups devel: Cups Development Package</
li>
39N/A <
li>freetype 2.3+ devel: Freetype 2.3 Development Package</
li>
39N/A <
li>hg: Mercurial, if you need to clone or manage source repositories</
li>
39N/A <
li>ksh: May be needed when using <
tt>webrev</
tt></
li>
39N/A after you get all the packages installed.
11N/A <!-- ------------------------------------------------------ --> 39N/A <
h3><
a name="centos">CentOS 5.2</
a></
h3>
39N/A you need to make sure you have
39N/A the following Development bundles installed:
39N/A <
li>Development Libraries</
li>
39N/A <
li>Development Tools</
li>
39N/A <
li>Java Development</
li>
39N/A <
li>X Software Development</
li>
39N/A Plus the following packages:
39N/A <
li>cups devel: Cups Development Package</
li>
39N/A <
li>alsa devel: Alsa Development Package</
li>
39N/A <
li>ant: Ant Package</
li>
39N/A The freetype 2.3 packages don't seem to be available,
39N/A but the freetype 2.3 sources can be downloaded, built,
39N/A and installed easily enough from
39N/A the freetype site</
a>.
39N/A Build and install with something like:
39N/A Mercurial packages could not be found easily, but a Google
39N/A search should find ones, and they usually include Python if
11N/A <!-- ------------------------------------------------------ --> 11N/A <
h3><
a name="ubuntu">Ubuntu</
a></
h3>
11N/A In addition to needing the Bootstrap JDK and the Binary Plugs,
11N/A when building on Ubuntu you will need to
11N/A make sure certain packages are installed.
11N/A In particular, certain X11 packages, make, m4, gawk, gcc 4,
11N/A binutils, cups, freetype
11N/A <!-- ------------------------------------------------------ --> 11N/A <
h4>Ubuntu 6.06</
h4>
11N/A The following list of packages for Ubuntu 6.06 is a working set that
11N/A does appear to work.
11N/A <
b>Note that it's quite possible that some of these
11N/A packages are not required, so anyone discovering that some of the
11N/A packages listed below are NOT required,
11N/A All the packages below can be installed with the
11N/A Synaptic Package manager provided with the base Ubuntu 6.06 release.
11N/A <
li>binutils (2.16.1cvs20060117-1ubuntu2.1)</
li>
11N/A <
li>cpp (4:4.0.3-1)</
li>
11N/A <
li>cpp-4.0 (4.0.3-1ubuntu5)</
li>
11N/A <
li>libfreetype6-dev</
li>
11N/A <
li>g++ (4:4.0.3-1)</
li>
11N/A <
li>g++-4.0 (4.0.3-1ubuntu5)</
li>
11N/A <
li>gawk (1:3.1.5-2build1)</
li>
11N/A <
li>gcc (4:4.0.3-1)</
li>
11N/A <
li>gcc-4.0 (4.0.3-1ubuntu5)</
li>
11N/A <
li>libasound2-dev (1.0.10-2ubuntu4)</
li>
11N/A <
li>libc6 (2.3.6-0ubuntu20) to 2.3.6-0ubuntu20.4</
li>
11N/A <
li>libc6-dev (2.3.6-0ubuntu20.4)</
li>
11N/A <
li>libc6-i686 (2.3.6-0ubuntu20) to 2.3.6-0ubuntu20.4</
li>
11N/A <
li>libcupsys2-dev (1.2.2-0ubuntu0.6.06)</
li>
11N/A <
li>libgcrypt11-dev (1.2.2-1)</
li>
11N/A <
li>libgnutls-dev (1.2.9-2ubuntu1.1)</
li>
11N/A <
li>libgnutls12 (1.2.9-2ubuntu1) to 1.2.9-2ubuntu1.1</
li>
11N/A <
li>libgpg-error-dev (1.1-4)</
li>
11N/A <
li>libice-dev (2:1.0.0-0ubuntu2)</
li>
11N/A <
li>liblockfile1 (1.06.1)</
li>
11N/A <
li>libopencdk8-dev (0.5.7-2)</
li>
11N/A <
li>libpopt-dev (1.7-5)</
li>
11N/A <
li>libsm-dev (2:1.0.0-0ubuntu2)</
li>
11N/A <
li>libstdc++6-4.0-dev (4.0.3-1ubuntu5)</
li>
11N/A <
li>libtasn1-2-dev (0.2.17-1ubuntu1)</
li>
11N/A <
li>libx11-dev (2:1.0.0-0ubuntu9)</
li>
11N/A <
li>libxau-dev (1:1.0.0-0ubuntu4)</
li>
11N/A <
li>libxaw-headers (2:1.0.1-0ubuntu3)</
li>
11N/A <
li>libxaw7-dev (2:1.0.1-0ubuntu3)</
li>
11N/A <
li>libxdmcp-dev (1:1.0.0-0ubuntu2)</
li>
11N/A <
li>libxext-dev (2:1.0.0-0ubuntu4)</
li>
11N/A <
li>libxi-dev (2:1.0.0-0ubuntu3) </
li>
11N/A <
li>libxmu-dev (2:1.0.0-0ubuntu3)</
li>
11N/A <
li>libxmu-headers (2:1.0.0-0ubuntu3)</
li>
11N/A <
li>libxmuu-dev (2:1.0.0-0ubuntu3)</
li>
11N/A <
li>libxp-dev (6.8.2-11ubuntu2)</
li>
11N/A <
li>libxpm-dev (1:3.5.4.2-0ubuntu3)</
li>
11N/A <
li>libxrandr-dev (1:1.1.0.2-0ubuntu4)</
li>
11N/A <
li>libxt-dev (1:1.0.0-0ubuntu3)</
li>
11N/A <
li>libxtrap-dev (2:1.0.0-0ubuntu2)</
li>
11N/A <
li>libxtst-dev (2:1.0.1-0ubuntu2)</
li>
11N/A <
li>libxv-dev (2:1.0.1-0ubuntu3)</
li>
11N/A <
li>linux-kernel-headers (2.6.11.2-0ubuntu18)</
li>
11N/A <
li>m4 (1.4.4-1)</
li>
11N/A <
li>ssl-cert (1.0.13)</
li>
11N/A <
li>x-dev (7.0.4-0ubuntu2)</
li>
11N/A <
li>x11proto-core-dev (7.0.4-0ubuntu2)</
li>
11N/A <
li>x11proto-input-dev (1.3.2-0ubuntu2)</
li>
11N/A <
li>x11proto-kb-dev (1.0.2-0ubuntu2)</
li>
11N/A <
li>x11proto-randr-dev (1.1.2-0ubuntu2)</
li>
11N/A <
li>x11proto-record-dev (1.13.2-0ubuntu2)</
li>
11N/A <
li>x11proto-trap-dev (3.4.3-0ubuntu2)</
li>
11N/A <
li>x11proto-video-dev (2.2.2-0ubuntu2)</
li>
11N/A <
li>x11proto-xext-dev (7.0.2-0ubuntu2)</
li>
11N/A <
li>xlibs-dev (7.0.0-0ubuntu45)</
li>
11N/A <
li>zlib1g-dev (1:1.2.3-6ubuntu4)</
li>
11N/A <!-- ------------------------------------------------------ --> 11N/A <
h4>Ubuntu 7.04</
h4>
11N/A Using the Synaptic Package Manager, download the following
11N/A packages (double indented packages are automatically aquired
11N/A due to package dependencies):
11N/A <
li>build-essential</
li>
11N/A <
li>libstdc++6.4.1-dev</
li>
11N/A <
li>linux-libc-dev</
li>
11N/A <
li>libasound2-dev</
li>
11N/A <
li>libcupsys2-dev</
li>
11N/A <
li>libgcrypt11-dev</
li>
11N/A <
li>lgnutls-dev</
li>
11N/A <
li>libgpg-error-dev</
li>
11N/A <
li>liblzo-dev</
li>
11N/A <
li>libopencdk8-dev</
li>
11N/A <
li>libpopt-dev</
li>
11N/A <
li>libtasn1-3-dev</
li>
11N/A <
li>zlib1g-dev</
li>
11N/A <
li>sun-java6-jdk</
li>
11N/A <
li>java-common</
li>
11N/A <
li>odbcinst1debian1</
li>
11N/A <
li>sun-java6-bin</
li>
11N/A <
li>sun-java6-jre</
li>
11N/A <
li>x11proto-print-dev</
li>
11N/A <
li>libxaw7-dev</
li>
11N/A <
li>libxaw-headers</
li>
11N/A <
li>libfreetype6-dev</
li>
11N/A <!-- ------------------------------------------------------ --> 11N/A <
h2><
a name="directories">Source Directory Structure</
a></
h2>
11N/A The source code for the OpenJDK is delivered in a set of
11N/A <
tt>langtools</
tt>,
11N/A The <
tt>hotspot</
tt> directory contains the source code and make
11N/A files for building the OpenJDK Hotspot Virtual Machine.
11N/A The <
tt>langtools</
tt> directory contains the source code and make
11N/A files for building the OpenJDK javac and language tools.
11N/A The <
tt>corba</
tt> directory contains the source code and make
11N/A files for building the OpenJDK Corba files.
11N/A The <
tt>jaxws</
tt> directory contains the source code and make
11N/A files for building the OpenJDK JAXWS files.
11N/A The <
tt>jaxp</
tt> directory contains the source code and make
11N/A files for building the OpenJDK JAXP files.
11N/A The <
tt>jdk</
tt> directory contains the source code and make files for
11N/A building the OpenJDK runtime libraries and misc files.
11N/A The top level <
tt>Makefile</
tt>
11N/A is used to build the entire OpenJDK.
11N/A <!-- ------------------------------------------------------ --> 11N/A <
h2><
a name="building">Build Information</
a></
h2>
11N/A Building the OpenJDK
11N/A is done with a <
tt><
i>gmake</
i></
tt>
11N/A command line and various
11N/A environment or make variable settings that direct the make rules
11N/A to where various components have been installed.
11N/A Where possible the makefiles will attempt to located the various
11N/A components in the default locations or any component specific
11N/A When the normal defaults fail or components cannot be found,
11N/A <
tt>ALT_*</
tt> variables (alternates)
11N/A can be used to help the makefiles locate components.
11N/A if you need help in setting up your environment variables.
11N/A A build could be as simple as:
0N/A <
i>gmake</
i> sanity && <
i>gmake</
i>
11N/A Of course ksh or sh would work too.
11N/A But some customization will probably be necessary.
11N/A The <
tt>sanity</
tt> rule will make some basic checks on build
11N/A dependencies and generate appropriate warning messages
11N/A regarding missing, out of date, or newer than expected components
11N/A found on your system.
11N/A <!-- ------------------------------------------------------ --> 11N/A <
h3><
a name="gmake">GNU make (<
tt><
i>gmake</
i></
tt>)</
a></
h3>
11N/A The Makefiles in the OpenJDK are only valid when used with the
11N/A GNU version of the utility command <
tt>make</
tt>
11N/A (<
tt><
i>gmake</
i></
tt>).
11N/A A few notes about using GNU make:
11N/A In general, you need GNU make version 3.78.1 or newer.
11N/A Place the location of the GNU make binary in the <
tt>PATH</
tt>.
11N/A <
strong>Linux:</
strong>
11N/A <
strong>Solaris:</
strong>
11N/A If your Solaris system has the software
11N/A from the Solaris Companion CD installed,
11N/A you should use <
tt>gmake</
tt>
23N/A In more recent versions of Solaris GNU make can be found
11N/A <
strong>Windows:</
strong>
11N/A <
b>WARNING:</
b> Watch out for make version 3.81, it may
23N/A not work due to a lack of support for MS-DOS drive letter paths
23N/A like <
tt>C:/</
tt> or <
tt>C:\</
tt>.
11N/A Use a 3.80 version, or find a newer
23N/A version that has this problem fixed, like 3.82.
11N/A The older 3.80 version of
make.exe can be downloaded with this
23N/A Use of this older 3.80
make.exe may require that you install the
23N/A no longer installed by default by the cygwin installer.
11N/A mozilla developer center</
a>
23N/A It's hoped that when make 3.82 starts shipping in a future cygwin
23N/A release that this MS-DOS path issue will be fixed.
11N/A Information on GNU make, and access to ftp download sites, are
11N/A The latest source to GNU make is available at
11N/A <!-- ------------------------------------------------------ --> 11N/A <
h3><
a name="linux">Basic Linux System Setup</
a></
h3>
11N/A <
strong>i586 only:</
strong>
11N/A The minimum recommended hardware for building the Linux version
11N/A is a Pentium class processor or better, at least 256 MB of RAM, and
11N/A approximately 1.5 GB of free disk space.
11N/A <
strong>X64 only:</
strong>
11N/A The minimum recommended hardware for building the Linux
11N/A version is an AMD Opteron class processor, at least 512 MB of RAM, and
11N/A approximately 4 GB of free disk space.
11N/A The build will use the tools contained in
11N/A of a standard installation of the Linux operating environment.
11N/A You should ensure that these directories are in your
11N/A Note that some Linux systems have a habit of pre-populating
11N/A your environment variables for you, for example <
tt>JAVA_HOME</
tt>
11N/A might get pre-defined for you to refer to the JDK installed on
11N/A You will need to unset <
tt>JAVA_HOME</
tt>.
11N/A It's a good idea to run <
tt>env</
tt> and verify the
11N/A environment variables you are getting from the default system
11N/A settings make sense for building the
11N/A <!-- ------------------------------------------------------ --> 11N/A <
h4><
a name="linux_checklist">Basic Linux Check List</
a></
h4>
11N/A <
a href="#bootjdk">Bootstrap JDK</
a>, set
11N/A <
tt><
a href="#ALT_BOOTDIR">ALT_BOOTDIR</
a></
tt>.
11N/A <
a href="#binaryplugs">Binary Plugs</
a>, set
11N/A <
tt><
a href="#ALT_BINARY_PLUGS_PATH">ALT_BINARY_PLUGS_PATH</
a></
tt>.
11N/A <
a href="#importjdk">Optional Import JDK</
a>, set
11N/A <
tt><
a href="#ALT_JDK_IMPORT_PATH">ALT_JDK_IMPORT_PATH</
a></
tt>.
11N/A Install or upgrade the <
a href="#freetype">FreeType development
23N/A <
a href="#ant">Ant</
a>, set
23N/A <
tt><
a href="#ANT_HOME">ANT_HOME</
a></
tt>.
11N/A <!-- ------------------------------------------------------ --> 11N/A <
h3><
a name="solaris">Basic Solaris System Setup</
a></
h3>
11N/A The minimum recommended hardware for building the
11N/A Solaris SPARC version is an UltraSPARC with 512 MB of RAM.
11N/A the Solaris x86 version, a Pentium class processor or better and at
11N/A least 512 MB of RAM are recommended.
11N/A Approximately 1.4 GB of free disk
11N/A space is needed for a 32-bit build.
11N/A If you are building the 64bit version, you should
11N/A run the command "isainfo -v" to verify that you have a
11N/A 64-bit installation, it should say <
tt>sparcv9</
tt> or
11N/A An additional 7 GB of free disk space is needed
11N/A for a 64-bit build.
11N/A and <
tt>/
usr/
bin</
tt> of a standard developer or full installation of
11N/A the Solaris operating environment.
11N/A Solaris patches specific to the JDK can be downloaded from the
11N/A SunSolve JDK Solaris patches download page</
a>.
11N/A You should ensure that the latest patch cluster for
11N/A your version of the Solaris operating environment has also
11N/A <!-- ------------------------------------------------------ --> 11N/A <
h4><
a name="solaris_checklist">Basic Solaris Check List</
a></
h4>
11N/A <
a href="#bootjdk">Bootstrap JDK</
a>, set
11N/A <
tt><
a href="#ALT_BOOTDIR">ALT_BOOTDIR</
a></
tt>.
11N/A <
a href="#binaryplugs">Binary Plugs</
a>, set
11N/A <
tt><
a href="#ALT_BINARY_PLUGS_PATH">ALT_BINARY_PLUGS_PATH</
a></
tt>.
11N/A <
a href="#importjdk">Optional Import JDK</
a>, set
11N/A <
tt><
a href="#ALT_JDK_IMPORT_PATH">ALT_JDK_IMPORT_PATH</
a></
tt>.
11N/A <
a href="#studio">Sun Studio Compilers</
a>, set
11N/A <
a href="#ALT_COMPILER_PATH"><
tt>ALT_COMPILER_PATH</
tt></
a>.
11N/A <
a href="#cups">CUPS Include files</
a>, set
11N/A <
tt><
a href="#ALT_CUPS_HEADERS_PATH">ALT_CUPS_HEADERS_PATH</
a></
tt>.
23N/A <
a href="#ant">Ant</
a>, set
23N/A <
tt><
a href="#ANT_HOME">ANT_HOME</
a></
tt>.
11N/A <!-- ------------------------------------------------------ --> 11N/A <
h3><
a name="windows">Basic Windows System Setup</
a></
h3>
11N/A <
strong>i586 only:</
strong>
11N/A The minimum recommended hardware for building the 32bit or X86
11N/A Windows version is an Pentium class processor or better, at least
11N/A 512 MB of RAM, and approximately 600 MB of free disk space.
11N/A NOTE: The Windows 2000 build machines need to use the
11N/A Build machines formatted to FAT32 will not work
11N/A because FAT32 doesn't support case-sensitivity in file names.
11N/A <
strong>X64 only:</
strong>
11N/A The minimum recommended hardware for building
11N/A the Windows X64 version is an AMD Opteron class processor, at least 1
11N/A GB of RAM, and approximately 10 GB of free disk space.
11N/A <!-- ------------------------------------------------------ --> 11N/A <
h4><
a name="paths">Windows Paths</
a></
h4>
0N/A <
strong>Windows:</
strong>
11N/A Note that GNU make is a historic utility and is based very
11N/A heavily on shell scripting, so it does not tolerate the Windows habit
11N/A of having spaces in pathnames or the use of the <
tt>\</
tt>characters in pathnames.
11N/A Luckily on most Windows systems, you can use <
tt>/</
tt>instead of \, and
11N/A there is always a 'short' pathname without spaces for any path that
11N/A Unfortunately, this short pathname can be somewhat dynamic and the
11N/A formula is difficult to explain.
11N/A You can use <
tt>cygpath</
tt> utility to map pathnames with spaces
11N/A or the <
tt>\</
tt>character into the <
tt>C:/</
tt> style of pathname
11N/A <
tt>cygpath -s -m "<
i>path</
i>"</
tt>.
11N/A The makefiles will try to translate any pathnames supplied
11N/A to it into the <
tt>C:/</
tt> style automatically.
11N/A Note that use of CYGWIN creates a unique problem with regards to
11N/A setting <
a href="#path"><
tt>PATH</
tt></
a>. Normally on Windows
11N/A the <
tt>PATH</
tt> variable contains directories
11N/A separated with the ";" character (Solaris and Linux uses ":").
11N/A With CYGWIN, it uses ":", but that means that paths like "C:/path"
11N/A cannot be placed in the CYGWIN version of <
tt>PATH</
tt> and
11N/A which CYGWIN understands, but only CYGWIN understands.
11N/A So be careful with paths on Windows.
11N/A <!-- ------------------------------------------------------ --> 11N/A <
h4><
a name="windows_checklist">Basic Windows Check List</
a></
h4>
11N/A <
a href="#cygwin">CYGWIN product</
a>.
11N/A <
a href="#bootjdk">Bootstrap JDK</
a>, set
11N/A <
tt><
a href="#ALT_BOOTDIR">ALT_BOOTDIR</
a></
tt>.
11N/A <
a href="#binaryplugs">Binary Plugs</
a>, set
11N/A <
tt><
a href="#ALT_BINARY_PLUGS_PATH">ALT_BINARY_PLUGS_PATH</
a></
tt>..
11N/A <
a href="#importjdk">Optional Import JDK</
a>, set
11N/A <
tt><
a href="#ALT_JDK_IMPORT_PATH">ALT_JDK_IMPORT_PATH</
a></
tt>.
39N/A <
a href="#msvc">Microsoft Visual Studio .NET 2003 Professional</
a> (32bit) or the
39N/A <
a href="#mssdk">Microsoft Platform SDK</
a> (64bit).
11N/A Setup all environment variables for compilers
11N/A (see <
a href="#msvc">compilers</
a>).
11N/A <
a href="#dxsdk">Microsoft DirectX SDK</
a>.
23N/A <
a href="#ant">Ant</
a>, set
23N/A <
tt><
a href="#ANT_HOME">ANT_HOME</
a></
tt>.
11N/A <!-- ------------------------------------------------------ --> 11N/A <
h3><
a name="dependencies">Build Dependencies</
a></
h3>
11N/A Depending on the platform, the OpenJDK build process has some basic
11N/A dependencies on components not part of the OpenJDK sources.
11N/A Some of these are specific to a platform, some even specific to
11N/A Each dependency will have a set of ALT variables that can be set
11N/A to tell the makefiles where to locate the component.
11N/A In most cases setting these ALT variables may not be necessary
11N/A and the makefiles will find defaults on the system in standard
11N/A install locations or through component specific variables.
11N/A <!-- ------------------------------------------------------ --> 11N/A <
h4><
a name="bootjdk">Bootstrap JDK</
a></
h4>
11N/A All OpenJDK builds require access to the previously released
11N/A JDK 6, this is often called a bootstrap JDK.
11N/A The JDK 6 binaries can be downloaded from Sun's
11N/A For build performance reasons
11N/A is very important that this bootstrap JDK be made available on the
11N/A local disk of the machine doing the build.
11N/A You should always set
11N/A <
tt><
a href="#ALT_BOOTDIR">ALT_BOOTDIR</
a></
tt>
11N/A to point to the location of
11N/A the bootstrap JDK installation, this is the directory pathname
11N/A that contains a <
tt>bin, lib, and include</
tt>
11N/A It's also a good idea to also place its <
tt>bin</
tt> directory
11N/A in the <
tt>PATH</
tt> environment variable, although it's
11N/A <
strong>Solaris:</
strong>
11N/A Some pre-installed JDK images may be available to you in the
11N/A <
tt><
a href="#ALT_BOOTDIR">ALT_BOOTDIR</
a></
tt>
11N/A the makefiles will look in that location for a JDK it can use.
11N/A <!-- ------------------------------------------------------ --> 11N/A <
h4><
a name="binaryplugs">Binary Plugs</
a></
h4>
11N/A Not all of the source code that makes up the JDK is available
11N/A under an open-source license.
11N/A This is a temporary situation and these binary plugs will be
11N/A replaced with fully open source replacements as soon as possible.
11N/A So currently, in order to build a complete OpenJDK image,
11N/A you must first download and install the appropriate
11N/A binary plug bundles for the OpenJDK, go to the
11N/A the "<
b>Bundles(7)</
b>" link and download the binaryplugs for
11N/A your particular platform.
11N/A The file downloaded is a jar file that must be extracted by running
11N/A <
tt><
b>java -jar jdk-7-ea-plug-b<
i>nn</
i>-<
i>os</
i>-<
i>arch</
i>-<
i>dd</
i>_<
i>month</
i>_<
i>year</
i>.jar</
b></
tt>
11N/A A prompt will be issued for acceptance of these binary plug files.
11N/A During the OpenJDK build process these "binary plugs"
11N/A for the encumbered components will be copied into your
11N/A resulting OpenJDK binary build image.
11N/A These binary plug files are only for the purpose of
11N/A building an OpenJDK binary.
11N/A <
tt><
a href="#ALT_BINARY_PLUGS_PATH">ALT_BINARY_PLUGS_PATH</
a></
tt>
11N/A to the root of this installation.
11N/A <!-- ------------------------------------------------------ --> 11N/A <
h4><
a name="importjdk">Optional Import JDK</
a></
h4>
11N/A The <
tt><
a href="#ALT_JDK_IMPORT_PATH">ALT_JDK_IMPORT_PATH</
a></
tt>
11N/A setting is only needed if you are not building the entire
11N/A JDK. For example, if you have built the entire JDK once, and
11N/A wanted to avoid repeatedly building the Hotspot VM, you could
11N/A set this to the location of the previous JDK install image
11N/A and the build will copy the needed files from this import area.
11N/A <!-- ------------------------------------------------------ --> 23N/A <
h4><
a name="ant">Ant</
a></
h4>
23N/A All OpenJDK builds require access to least Ant 1.6.5.
23N/A The Ant tool is available from the
23N/A Ant download site</
a>.
23N/A You should always set
23N/A <
tt><
a href="#ANT_HOME">ANT_HOME</
a></
tt>
23N/A to point to the location of
23N/A the Ant installation, this is the directory pathname
23N/A that contains a <
tt>bin and lib</
tt>.
23N/A It's also a good idea to also place its <
tt>bin</
tt> directory
23N/A in the <
tt>PATH</
tt> environment variable, although it's
23N/A not absolutely required.
23N/A <!-- ------------------------------------------------------ --> 11N/A <
h4><
a name="cacerts">Certificate Authority File (cacert)</
a></
h4>
11N/A for a better understanding of the Certificate Authority (CA).
11N/A A certificates file named "cacerts"
11N/A represents a system-wide keystore with CA certificates.
11N/A binary bundles, the "cacerts" file contains root CA certificates from
11N/A several public CAs (
e.g., VeriSign, Thawte, and Baltimore).
11N/A The source contain a cacerts file
11N/A without CA root certificates.
11N/A Formal JDK builders will need to secure
11N/A permission from each public CA and include the certificates into their
11N/A own custom cacerts file.
11N/A Failure to provide a populated cacerts file
11N/A will result in verification errors of a certificate chain during runtime.
11N/A <
tt><
a href="#ALT_CACERTS_FILE">ALT_CACERTS_FILE</
a></
tt>
11N/A can be used to override the default location of the
11N/A cacerts file that will get placed in your build.
11N/A By default an empty cacerts file is provided and that should be
11N/A fine for most JDK developers.
11N/A <!-- ------------------------------------------------------ --> 11N/A <
h4><
a name="compilers">Compilers</
a></
h4>
11N/A The GNU gcc compiler version should be 3.2.2 or newer.
11N/A The binutils package should be 2.11.93.0.2-11 or newer.
11N/A The compiler used should be the default compiler installed
11N/A Older Linux systems may require a gcc and bunutils update.
11N/A The Redhat Enterprise Advanced Server 2.1 update 2 system
11N/A is one of these systems.
11N/A RedHat Linux users can obtain this binutils package from
11N/A target="_blank">Redhat web site</
a>.
11N/A You will need to remove the default compiler and binutils
11N/A packages and install the required packages
11N/A into the default location on the system.
11N/A However if you have a new video card driver, like
11N/A Geforce 4 it is best to use
11N/A the same compiler as the kernel was built with to
11N/A build the new video card driver module.
11N/A So you should build the modules before making this change.
11N/A <
strong><
a name="studio">Solaris: Sun Studio</
a></
strong>
28N/A Sun Studio 12 Compilers</
a>
28N/A (containing version 5.9 of the C and C++ compilers) is required,
11N/A with patches from the
11N/A SunSolve web site</
a>.
11N/A <
a href="#ALT_COMPILER_PATH"><
tt>ALT_COMPILER_PATH</
tt></
a>
11N/A to point to the location of
11N/A the compiler binaries, and place this location in the <
tt>PATH</
tt>.
11N/A The Sun Studio Express compilers at:
11N/A Sun Studio Express Download site</
a>
11N/A are also an option, although these compilers have not
11N/A been extensively used yet.
11N/A <
strong><
a name="msvc">Windows i586: Microsoft Visual Studio .NET 2003 Professional</
a></
strong>
11N/A The 32-bit OpenJDK Windows build
11N/A requires Microsoft Visual Studio .NET 2003 (VS2003) Professional
11N/A The compiler and other tools are expected to reside
11N/A in the location defined by the variable <
tt>VS71COMNTOOLS</
tt> which
11N/A is set by the Microsoft Visual Studio .NET installer.
11N/A Once the compiler is installed,
11N/A to set the compiler environment variables
11N/A prior to building the
11N/A The above environment variables <
b>MUST</
b> be set.
11N/A The Microsoft Visual Studio .NET 2005 (VS2005) compiler
11N/A will not work at this time due to the new runtime dll
11N/A and the manifest requirements.
39N/A <
b>WARNING:</
b> Make sure you check out the
39N/A The path <
tt>/
usr/
bin</
tt> must be after the path to the
39N/A Visual Studio product.
11N/A <
strong><
a name="mssdk">Windows X64: Microsoft Platform SDK April 2005</
a></
strong>
11N/A On <
b>X64</
b>, the Microsoft Platform Software
11N/A Development Kit (SDK), April 2005 Edition compiler,
11N/A is required for building the OpenJDK
11N/A because it contains the C/C++ compiler.
11N/A You will need to minimally install the Core SDK and
11N/A the MDAC SDK features of this compiler.
11N/A Once the Platform SDK is installed,
11N/A to set the compiler environment variables
11N/A prior to building the
11N/A The above environment variables <
b>MUST</
b> be set.
11N/A Note that this compiler may say it's version is a
11N/A Microsoft Visual Studio .NET 2005 (VS2005), but be careful,
11N/A it will not match the official VS2005 product.
11N/A This Platform SDK compiler is only used on X64 builds.
11N/A <!-- ------------------------------------------------------ --> 11N/A <
h4><
a name="zip">Zip and Unzip</
a></
h4>
11N/A Version 2.2 (November 3rd 1997) or newer of the zip utility
11N/A and version 5.12 or newer of the unzip utility is needed
11N/A With Solaris, Linux, and Windows CYGWIN, the zip and unzip
11N/A utilities installed on the system should be fine.
11N/A Information and the source code for
11N/A target="_blank">info-zip web site</
a>.
11N/A <!-- ------------------------------------------------------ --> 11N/A <
h4><
a name="cups">Common UNIX Printing System (CUPS) Headers (Solaris & Linux)</
a></
h4>
11N/A <
strong>Solaris:</
strong>
11N/A CUPS header files are required for building the
11N/A OpenJDK on Solaris.
11N/A The Solaris header files can be obtained by installing
11N/A the package <
strong>SFWcups</
strong> from the Solaris Software
11N/A Companion
CD/
DVD, these often will be installed into
11N/A <
strong>Linux:</
strong>
11N/A CUPS header files are required for building the
11N/A The Linux header files are usually available from a "cups"
11N/A development package, it's recommended that you try and use
11N/A the package provided by the particular version of Linux that
11N/A The CUPS header files can always be downloaded from
11N/A <
tt><
a href="#ALT_CUPS_HEADERS_PATH">ALT_CUPS_HEADERS_PATH</
a></
tt>
11N/A can be used to override the default location of the
11N/A <!-- ------------------------------------------------------ --> 11N/A <
h4><
a name="freetype">FreeType 2</
a></
h4>
11N/A Version 2.3 or newer of FreeType is required for building the OpenJDK.
11N/A On Unix systems required files can be available as part of your
11N/A distribution (while you still may need to upgrade them).
11N/A Note that you need development version of package that
11N/A includes both FreeType library and header files.
11N/A You can always download latest FreeType version from the
11N/A In case it is installed elsewhere you will need to set environment
11N/A <
tt><
a href="#ALT_FREETYPE_LIB_PATH">ALT_FREETYPE_LIB_PATH</
a></
tt>
11N/A <
tt><
a href="#ALT_FREETYPE_HEADERS_PATH">ALT_FREETYPE_HEADERS_PATH</
a></
tt>
11N/A to refer to place where library and header files are installed.
23N/A Building the freetype 2 libraries from scratch is also possible,
23N/A however on Windows refer to the
23N/A Windows FreeType DLL build instructions</
a>.
23N/A Note that by default FreeType is built with byte code hinting
23N/A support disabled due to licensing restrictions.
23N/A In this case, text appearance and metrics are expected to
23N/A differ from Sun's official JDK build.
23N/A the SourceForge FreeType2 Home Page
23N/A for more information.
11N/A <!-- ------------------------------------------------------ --> 11N/A <
h4><
a name="alsa">Advanced Linux Sound Architecture (ALSA) (Linux only)</
a></
h4>
11N/A <
strong>Linux only:</
strong>
11N/A Version 0.9.1 or newer of the ALSA files are
11N/A required for building the OpenJDK on Linux.
11N/A These Linux files are usually available from an "alsa"
11N/A development package, it's highly recommended that you try and use
11N/A the package provided by the particular version of Linux that
11N/A The makefiles will check this emit a sanity error if it is
11N/A missing or the wrong version.
11N/A In particular, older Linux systems will likely not have the
11N/A right version of ALSA installed, for example
11N/A Redhat AS 2.1 U2 and SuSE 8.1 do not include a sufficiently
11N/A recent ALSA distribution.
11N/A On rpm-based systems, you can see if ALSA is installed by
11N/A running this command:
11N/A <
tt>rpm -qa | grep alsa</
tt>
11N/A Both <
tt>alsa</
tt> and <
tt>alsa-devel</
tt> packages are needed.
11N/A If your distribution does not come with ALSA, and you can't
11N/A find ALSA packages built for your particular system,
11N/A you can try to install the pre-built ALSA rpm packages from
11N/A Note that installing a newer ALSA could
11N/A break sound output if an older version of ALSA was previously
11N/A installed on the system, but it will enable JDK compilation.
11N/A Installation: execute as root<
br>
11N/A Uninstallation:<
br>
11N/A [i586]: <
code>rpm -ev alsa-lib-devel-0.9.1-rh61</
code><
br>
11N/A [x64]:<
code>rpm -ev alsa-lib-devel-0.9.8-amd64</
code><
br>
11N/A Make sure that you do not link to the static library
11N/A As a last resort you can go to the
11N/A Advanced Linux Sound Architecture Site</
a> and build it from
11N/A Download driver and library
11N/A source tarballs from
11N/A As root, execute the following
11N/A commands (you may need to adapt the version number):
11N/A $ cd alsa-driver-0.9.1
11N/A $ cd alsa-lib-0.9.1
11N/A Should one of the above steps fail, refer to the documentation on
11N/A Note that this is a minimum install that enables
11N/A building the JDK platform. To actually use ALSA sound drivers, more
11N/A steps are necessary as outlined in the documentation on ALSA's homepage.
11N/A ALSA can be uninstalled by executing <
tt>make uninstall</
tt> first in
11N/A the <
tt>alsa-lib-0.9.1</
tt> directory and then in
11N/A <
tt>alsa-driver-0.9.1</
tt>.
11N/A There are no ALT* variables to change the assumed locations of ALSA,
11N/A the makefiles will expect to find the ALSA include files and library at:
11N/A <!-- ------------------------------------------------------ --> 11N/A <
h4>Windows Specific Dependencies</
h4>
11N/A <
strong>Unix Command Tools (<
a name="cygwin">CYGWIN</
a>)</
strong>
11N/A The OpenJDK requires access to a set of unix command tools
11N/A on Windows which can be supplied by
11N/A The OpenJDK build requires CYGWIN version 1.5.12 or newer.
11N/A Information about CYGWIN can
11N/A be obtained from the CYGWIN website at
11N/A By default CYGWIN doesn't install all the tools required for building
11N/A Along with the default installation, you need to install
11N/A the following tools.
11N/A <
td>Binary Name</
td>
11N/A <
td>Description</
td>
39N/A <
td>The GNU assembler, linker and binary
39N/A <
td>The GNU version of the 'make' utility built for CYGWIN.<
br>
23N/A <
b>NOTE</
b>: See <
a href="#gmake">the GNU make section</
a></
td>
11N/A <
td>Interpreters</
td>
39N/A <
td>GNU implementation of the traditional Unix macro
39N/A <
td>A program to manage archives of files</
td>
39N/A <
td>Pattern-directed scanning and processing language</
td>
39N/A <
td>Determines file type using 'magic' numbers</
td>
39N/A <
td>Package and compress (archive) files</
td>
39N/A <
td>Extract compressed files in a ZIP archive</
td>
39N/A <
td>Display amount of free and used memory in the system</
td>
11N/A Note that the CYGWIN software can conflict with other non-CYGWIN
11N/A software on your Windows system.
11N/A known issues and problems, of particular interest is the
11N/A BLODA (applications that interfere with CYGWIN)</
a>.
39N/A Be very careful with <
b><
tt>
link.exe</
tt></
b>, it will conflict
39N/A with the Visual Studio version. You need the Visual Studio
39N/A So it's important that the Visual Studio paths in PATH preceed
11N/A <
strong><
a name="dxsdk">Microsoft DirectX 9.0 SDK header files and libraries</
a></
strong>
11N/A Microsoft DirectX 9.0 SDK (Summer 2004)
11N/A headers are required for building
11N/A This SDK can be downloaded from
11N/A Microsoft DirectX 9.0 SDK (Summer 2004)</
a>.
11N/A If the link above becomes obsolete, the SDK can be found from
11N/A (search with "DirectX 9.0 SDK Update Summer 2004").
11N/A The location of this SDK can be set with
11N/A <
tt><
a href="#ALT_DXSDK_PATH">ALT_DXSDK_PATH</
a></
tt>
11N/A but it's normally found via the DirectX environment variable
11N/A <
tt>DXSDK_DIR</
tt>.
11N/A <
strong>i586 only:</
strong>
11N/A The OpenJDK 32bit build requires access to
11N/A the system32 directory set the
11N/A <
a href="#ALT_MSVCRT_DLL_PATH"><
tt>ALT_MSVCRT_DLL_PATH</
tt></
a>
11N/A variable to the location.
11N/A <
strong>X64 only:</
strong>
11N/A The OpenJDK 64bit build requires access to
11N/A usually supplied by the
11N/A <
a href="#mssdk">Platform SDK</
a>.
11N/A If it is not available from the Platform SDK,
11N/A <
a href="#ALT_MSVCRT_DLL_PATH"><
tt>ALT_MSVCRT_DLL_PATH</
tt></
a>
11N/A variable to the location.
11N/A <
strong>i586 only:</
strong>
11N/A build requires access to
11N/A <
a href="#msvc">Visual Studio product</
a>
11N/A Visual Studio product
11N/A <
a href="#ALT_MSVCR71_DLL_PATH"><
tt>ALT_MSVCR71_DLL_PATH</
tt></
a>
11N/A variable to the location.
11N/A <!-- ------------------------------------------------------ --> 11N/A <
h2><
a name="creating">Creating the Build</
a></
h2>
11N/A Once a machine is setup to build the OpenJDK,
11N/A the steps to create the build are fairly simple.
11N/A The various ALT settings can either be made into variables
11N/A or can be supplied on the
11N/A <
a href="#gmake"><
tt><
i>gmake</
i></
tt></
a>
11N/A <
li>Use the sanity rule to double check all the ALT settings:
11N/A [ARCH_DATA_MODEL=<
i>32 or 64</
i>]
11N/A [other "ALT_" overrides]
11N/A <
li>Start the build with the command:
11N/A [ARCH_DATA_MODEL=<
i>32 or 64</
i>]
11N/A [ALT_OUTPUTDIR=<
i>output_directory</
i>]
11N/A [other "ALT_" overrides]
11N/A <
strong>Solaris:</
strong>
11N/A Note that ARCH_DATA_MODEL is really only needed on Solaris to
11N/A indicate you want to built the 64-bit version.
11N/A And before the Solaris 64-bit binaries can be used, they
11N/A must be merged with the binaries from a separate 32-bit build.
11N/A The merged binaries may then be used in either 32-bit or 64-bit mode, with
11N/A the selection occurring at runtime
11N/A with the <
tt>-d32</
tt> or <
tt>-d64</
tt> options.
11N/A <!-- ------------------------------------------------------ --> 11N/A <
h2><
a name="testing">Testing the Build</
a></
h2>
11N/A When the build is completed, you should see the generated
11N/A binaries and associated files in the <
tt>j2sdk-image</
tt>
11N/A directory in the output directory.
11N/A The default output directory is
11N/A <
tt>build/<
i>platform</
i></
tt>,
11N/A where <
tt><
i>platform</
i></
tt> is one of
11N/A <
li>solaris-sparc</
li>
11N/A <
li>solaris-sparcv9</
li>
11N/A <
li>solaris-i586</
li>
11N/A <
li>solaris-amd64</
li>
11N/A <
li>linux-i586</
li>
11N/A <
li>linux-amd64</
li>
11N/A <
li>windows-i586</
li>
11N/A <
li>windows-amd64</
li>
11N/A directory should contain executables for the
11N/A OpenJDK tools and utilities.
11N/A You can test that the build completed properly by using the build
11N/A to run the various demos that you will find in the
11N/A The provided regression tests can be run with the <
tt>jtreg</
tt>
11N/A <!-- ------------------------------------------------------ --> 11N/A environment or make variables (just called <
b>variables</
b> in this
11N/A document) that can impact the build are:
11N/A <
dt><
a name="ALT_BINARY_PLUGS_PATH"><
tt>ALT_BINARY_PLUGS_PATH</
tt></
a></
dt>
11N/A The location of the binary plugs installation.
11N/A See <
a href="#binaryplugs">Binary Plugs</
a> for more information.
11N/A You should always have a local copy of a
11N/A recent Binary Plugs install image
11N/A and set this variable to that location.
23N/A <
dt><
a name="ALT_BOOTDIR"><
tt>ALT_BOOTDIR</
tt></
a></
dt>
23N/A The location of the bootstrap JDK installation.
23N/A See <
a href="#bootjdk">Bootstrap JDK</
a> for more information.
23N/A You should always install your own local Bootstrap JDK and
23N/A always set <
tt>ALT_BOOTDIR</
tt> explicitly.
23N/A <
dt><
a name="ALT_BUILD_BINARY_PLUGS_PATH"><
tt>ALT_BUILD_BINARY_PLUGS_PATH</
tt></
a></
dt>
23N/A These are useful in managing builds on multiple platforms.
23N/A The default network location for all of the binary plug images
23N/A If <
tt><
a href="#ALT_BINARY_PLUGS_PATH">ALT_BINARY_PLUGS_PATH</
a></
tt>
23N/A is not set, this directory will be used and should contain
23N/A the following directories:
23N/A <
tt>solaris-sparc</
tt>,
23N/A <
tt>solaris-i586</
tt>,
23N/A <
tt>solaris-sparcv9</
tt>,
23N/A <
tt>solaris-amd64</
tt>,
23N/A <
tt>linux-i586</
tt>,
23N/A <
tt>linux-amd64</
tt>,
23N/A <
tt>windows-i586</
tt>,
23N/A <
tt>windows-amd64</
tt>.
23N/A Where each of these directories contain the binary plugs image
11N/A <
dt><
a name="ALT_BUILD_JDK_IMPORT_PATH"><
tt>ALT_BUILD_JDK_IMPORT_PATH</
tt></
a></
dt>
11N/A These are useful in managing builds on multiple platforms.
11N/A The default network location for all of the import JDK images
11N/A If <
tt><
a href="#ALT_JDK_IMPORT_PATH">ALT_JDK_IMPORT_PATH</
a></
tt>
11N/A is not set, this directory will be used and should contain
11N/A the following directories:
11N/A <
tt>solaris-sparc</
tt>,
11N/A <
tt>solaris-i586</
tt>,
11N/A <
tt>solaris-sparcv9</
tt>,
11N/A <
tt>solaris-amd64</
tt>,
11N/A <
tt>linux-i586</
tt>,
11N/A <
tt>linux-amd64</
tt>,
11N/A <
tt>windows-i586</
tt>,
11N/A <
tt>windows-amd64</
tt>.
11N/A Where each of these directories contain the import JDK image
23N/A <
dt><
tt><
a name="ALT_CACERTS_FILE">ALT_CACERTS_FILE</
a></
tt></
dt>
23N/A The location of the <
a href="#cacerts">cacerts</
a> file.
23N/A The default will refer to
23N/A <
dt><
a name="ALT_COMPILER_PATH"><
tt>ALT_COMPILER_PATH</
tt></
a> </
dt>
23N/A The location of the C/C++ compiler.
23N/A The default varies depending on the platform.
23N/A <
dt><
a name="ALT_CUPS_HEADERS_PATH"><
tt>ALT_CUPS_HEADERS_PATH</
tt></
a> </
dt>
23N/A The location of the CUPS header files.
23N/A See <
a href="#cups">CUPS information</
a> for more information.
23N/A If this path does not exist the fallback path is
23N/A <
dt><
tt><
a name="ALT_DEVTOOLS_PATH">ALT_DEVTOOLS_PATH</
a></
tt> </
dt>
23N/A The location of tools like the
23N/A <
a href="#zip"><
tt>zip</
tt> and <
tt>unzip</
tt></
a>
23N/A binaries, but might also contain the GNU make utility
23N/A (<
tt><
i>gmake</
i></
tt>).
23N/A So this area is a bit of a grab bag, especially on Windows.
23N/A The default value depends on the platform and
23N/A Unix Commands being used.
23N/A On Linux the default will be
23N/A <
tt>$(ALT_JDK_DEVTOOLS_PATH)/<
i>{sparc,i386}</
i>/bin</
tt>,
23N/A on Windows with MKS
23N/A <
tt>%SYSTEMDRIVE%/UTILS</
tt>,
23N/A and on Windows with CYGWIN
23N/A <
dt><
tt><
a name="ALT_DXSDK_PATH">ALT_DXSDK_PATH</
a></
tt> </
dt>
23N/A <
strong>Windows Only:</
strong>
23N/A The location of the
23N/A <
a href="#dxsdk">Microsoft DirectX 9 SDK</
a>.
23N/A The default will be to try and use the DirectX environment
23N/A variable <
tt>DXSDK_DIR</
tt>,
23N/A failing that, look in <
tt>C:/DXSDK</
tt>.
23N/A <
dt><
a name="ALT_FREETYPE_HEADERS_PATH"><
tt>ALT_FREETYPE_HEADERS_PATH</
tt></
a></
dt>
23N/A The location of the FreeType header files.
23N/A See <
a href="#freetype">FreeType information</
a> for details.
23N/A <
dt><
a name="ALT_FREETYPE_LIB_PATH"><
tt>ALT_FREETYPE_LIB_PATH</
tt></
a></
dt>
23N/A The location of the FreeType shared library.
23N/A See <
a href="#freetype">FreeType information</
a> for details.
23N/A <
dt><
a name="ALT_JDK_DEVTOOLS_PATH"><
tt>ALT_JDK_DEVTOOLS_PATH</
tt></
a></
dt>
23N/A The default root location of the devtools.
23N/A The default value is
23N/A <
tt>$(ALT_SLASH_JAVA)/devtools</
tt>.
23N/A <
dt><
a name="ALT_JDK_IMPORT_PATH"><
tt>ALT_JDK_IMPORT_PATH</
tt></
a></
dt>
23N/A The location of a previously built JDK installation.
23N/A See <
a href="#importjdk">Optional Import JDK</
a> for more information.
23N/A <
dt><
a name="ALT_MSDEVTOOLS_PATH"><
tt>ALT_MSDEVTOOLS_PATH</
tt></
a> </
dt>
23N/A <
strong>Windows Only:</
strong>
23N/A The location of the Microsoft Visual Studio .NET 2003
23N/A tools 'bin' directory.
23N/A The default is usually derived from
23N/A <
a href="#ALT_COMPILER_PATH"><
tt>ALT_COMPILER_PATH</
tt></
a>.
23N/A <
dt><
tt><
a name="ALT_MSVCR71_DLL_PATH">ALT_MSVCR71_DLL_PATH</
a></
tt> </
dt>
23N/A <
strong>Windows i586 only:</
strong>
23N/A The location of the
23N/A <
dt><
tt><
a name="ALT_MSVCRT_DLL_PATH">ALT_MSVCRT_DLL_PATH</
a></
tt> </
dt>
23N/A <
strong>Windows Only:</
strong>
23N/A The location of the
23N/A <
dt><
a name="ALT_OUTPUTDIR"><
tt>ALT_OUTPUTDIR</
tt></
a> </
dt>
23N/A An override for specifying the (absolute) path of where the
23N/A build output is to go.
23N/A The default output directory will be build/<
i>platform</
i>.
23N/A <
dt><
a name="ALT_SLASHJAVA"><
tt>ALT_SLASHJAVA</
tt></
a></
dt>
23N/A The default root location for many of the ALT path locations
23N/A of the following ALT variables.
23N/A The default value is
23N/A <
tt>"/java"</
tt> on Solaris and Linux,
23N/A <
tt>"J:"</
tt> on Windows.
23N/A <
dt><
a name="ALT_UNIXCCS_PATH"><
tt>ALT_UNIXCCS_PATH</
tt></
a></
dt>
23N/A <
strong>Solaris only:</
strong>
23N/A An override for specifying where the Unix CCS
23N/A command set are located.
23N/A <
dt><
a name="ALT_UNIXCOMMAND_PATH"><
tt>ALT_UNIXCOMMAND_PATH</
tt></
a> </
dt>
23N/A An override for specifying where the
23N/A Unix command set are located.
23N/A The default location varies depending on the platform,
23N/A <
tt>"%SYSTEMDRIVE%/MKSNT"</
tt> or
23N/A <
tt>$(ROOTDIR)</
tt> on Windows with MKS, otherwise it's
23N/A <
dt><
a name="ALT_USRBIN_PATH"><
tt>ALT_USRBIN_PATH</
tt></
a></
dt>
23N/A An override for specifying where the
23N/A Unix <
tt>/
usr/
bin</
tt> commands are located. You usually do not need
23N/A to set this variable: the default location is <
tt>/
usr/
bin</
tt>)
23N/A <
dt><
a name="ANT_HOME"><
tt>ANT_HOME</
tt></
a></
dt>
23N/A The location of the Ant installation.
23N/A See <
a href="#ant">Ant</
a> for more information.
23N/A You should always set <
tt>ANT_HOME</
tt> explicitly.
23N/A <
dt><
a name="arch_data_model"><
tt>ARCH_DATA_MODEL</
tt></
a></
dt>
23N/A <
dd>The <
tt>ARCH_DATA_MODEL</
tt> variable
23N/A is used to specify whether the build is to generate 32-bit or 64-bit
23N/A The Solaris build supports either 32-bit or 64-bit builds, but
23N/A Windows and Linux will support only one, depending on the specific
23N/A Normally, setting this variable is only necessary on Solaris.
23N/A Set <
tt>ARCH_DATA_MODEL</
tt> to <
tt>32</
tt> for generating 32-bit binaries,
23N/A or to <
tt>64</
tt> for generating 64-bit binaries.
23N/A <
dt><
tt>BUILD_NUMBER</
tt> </
dt>
23N/A The build number for the build (<
i>
e.g.</
i> "b27").
23N/A The default value is "b00".
23N/A <
dt><
tt>MILESTONE</
tt> </
dt>
23N/A The milestone name for the build (<
i>
e.g.</
i>"beta").
23N/A The default value is "internal".
23N/A <
dt><
a name="path"><
tt>PATH</
tt></
a> </
dt>
23N/A <
dd>Typically you want to set the <
tt>PATH</
tt> to include:
23N/A <
li>The location of the GNU make binary</
li>
23N/A <
li>The location of the Bootstrap JDK <
tt>java</
tt>
23N/A (see <
a href="#bootjdk">Bootstrap JDK</
a>)</
li>
23N/A <
li>The location of the C/C++ compilers
23N/A (see <
a href="#compilers"><
tt>compilers</
tt></
a>)</
li>
23N/A <
li>The location or locations for the Unix command utilities
11N/A <!-- ------------------------------------------------------ --> 11N/A <
h2><
a name="troubleshooting">Troubleshooting</
a></
h2>
11N/A A build can fail for any number of reasons.
11N/A are a result of trying to build in an environment in which all the
11N/A pre-build requirements have not been met.
11N/A troubleshooting a build failure is to recheck that you have satisfied
11N/A all the pre-build requirements for your platform.
11N/A Look for the check list of the platform you are building on in the
11N/A <
a href="#contents">Table of Contents</
a>.
11N/A You can validate your build environment by using the <
tt>sanity</
tt>
11N/A will stop the build from starting, and any warnings may result in
11N/A a flawed product build.
11N/A We strongly encourage you to evaluate every
11N/A sanity check warning and fix it if required, before you proceed
11N/A further with your build.
11N/A Some of the more common problems with builds are briefly described
11N/A below, with suggestions for remedies.
11N/A <
b>Slow Builds:</
b>
11N/A If your build machine seems to be overloaded from too many
11N/A simultaneous C++ compiles, try setting the <
tt>HOTSPOT_BUILD_JOBS</
tt>
11N/A variable to <
tt>1</
tt> (if you're using a multiple CPU
11N/A machine, setting it to more than the the number of CPUs is probably
11N/A Creating the javadocs can be very slow, if you are running
11N/A javadoc, consider skipping that step.
11N/A Faster hardware and more RAM always helps too.
11N/A The VM build tends to be CPU intensive (many C++ compiles),
11N/A and the rest of the JDK will often be disk intensive.
11N/A Faster compiles are possible using a tool called
11N/A <
b>File time issues:</
b>
11N/A If you see warnings that refer to file time stamps,
e.g. 11N/A <
i>Warning message:</
i><
tt> File `xxx' has modification time in
11N/A <
i>Warning message:</
i> <
tt> Clock skew detected. Your build may
11N/A be incomplete.</
tt>
11N/A These warnings can occur when the clock on the build machine is out of
11N/A sync with the timestamps on the source files. Other errors, apparently
11N/A unrelated but in fact caused by the clock skew, can occur along with
11N/A the clock skew warnings. These secondary errors may tend to obscure the
11N/A fact that the true root cause of the problem is an out-of-sync clock.
11N/A For example, an out-of-sync clock has been known to cause an old
11N/A version of javac to be used to compile some files, resulting in errors
11N/A when the pre-1.4 compiler ran across the new <
tt>assert</
tt> keyword
11N/A in the 1.4 source code.
11N/A If you see these warnings, reset the clock on the build
11N/A machine, run "<
tt><
i>gmake</
i> clobber</
tt>" or delete the directory
11N/A containing the build output, and restart the build from the beginning.
11N/A <
b>Error message: <
tt>Trouble writing out table to disk</
tt></
b>
11N/A Increase the amount of swap space on your build machine.
11N/A <
b>Error Message: <
tt>libstdc++ not found:</
tt></
b>
11N/A This is caused by a missing libstdc++.a library.
11N/A This is installed as part of a specific package
11N/A By default some 64bit Linux versions (
e.g. Fedora)
11N/A only install the 64bit version of the libstdc++ package.
11N/A Various parts of the JDK build require a static
11N/A link of the C++ runtime libraries to allow for maximum
11N/A portability of the built images.
11N/A <
b>Error Message: <
tt>cannot restore segment prot after reloc</
tt></
b>
11N/A This is probably an issue with SELinux (See
11N/A Parts of the VM is built without the <
tt>-fPIC</
tt> for
11N/A performance reasons.
11N/A To completely disable SELinux:
11N/A <
li># system-config-securitylevel</
li>
11N/A <
li>In the window that appears, select the SELinux tab</
li>
11N/A <
li>Disable SELinux</
li>
11N/A Alternatively, instead of completely disabling it you could
11N/A disable just this one check.
11N/A <
li>Select System->Administration->SELinux Management</
li>
11N/A <
li>In the SELinux Management Tool which appears,
11N/A select "Boolean" from the menu on the left</
li>
11N/A <
li>Expand the "Memory Protection" group</
li>
11N/A <
li>Check the first item, labeled
11N/A "Allow all unconfined executables to use libraries requiring text relocation ..."</
li>
11N/A <
b>Windows Error Message: <
tt>*** fatal error - couldn't allocate heap, ... </
tt></
b>
11N/A The CYGWIN software can conflict with other non-CYGWIN
11N/A software. See the CYGWIN FAQ section on
11N/A BLODA (applications that interfere with CYGWIN)</
a>.
11N/A <
b>Windows Error Message: <
tt>*** multiple target patterns. Stop.</
tt></
b>
11N/A The CYGWIN make version 3.81 may not like the Windows <
tt>C:/</
tt>
11N/A style paths, it may not like the ':' character in the path
11N/A when used in a makefile target definition.
11N/A See the <
a href="#gmake"><
tt><
i>gmake</
i></
tt></
a> section.
