# HG changeset patch
# User ohair
# Node ID f6da81d808dcab20c32c4da3db12c9c
2d100b69e73fef9cb225ef1ee34a3f9ebdba80ed
6755914: Changes for openjdk6 build 10
6604044: java crashes talking to second X screen
6523403: OSS CMM: Need to provide lcms library with PYCC and LINEAR_RGB OS ICC profiles
6636469: Java Fullscreen Exclusive Mode not working with Xorg server 1.3.0 and above
6602426: TEST_BUG: test/sun/misc/Version/VersionCheck.java fails
6479286: LTP: XMLEncoder does not persist LineBorder properly
6673853: LegacyIntrospectorTest is testing an old deprecated com.sun API not present in OpenJDK.
6707643: (tz) Support tzdata2008c
Summary: Final b10 state (as defined by the source bundle)
Reviewed-by: darcy
diff -r 2d100b69e73f -r f6da81d808dc README-builds.html
--- a/README-builds.html Fri Jan 30 16:59:18
+++ b/README-builds.html Fri Jan 30 17:00:25
@@ -1,8 @@
OpenJDK Build README
This README file contains build instructions for the
Building the source code for the
a certain degree of technical expertise.
OpenJDK 6 Build README
OpenJDK 6 Build README
This README file contains build instructions for the
Building the source code for the
a certain degree of technical expertise.
This document is specific to OpenJDK 6, which has some
very minor differences in the build requirements over
the OpenJDK 7 sources,
e.g. OpenJDK 6 requires access to Motif files.
Where there are differences they should stand out,
like this block of text does.
Linux and Solaris:
Linux only:
Windows only:
Unix Command Tools ()
Linux and Solaris:
Windows only:
Unix Command Tools ()
This file often describes specific requirements for what we call the
"minimum build environments" (MBE) for the JDK.
Building with the MBE will generate the most compatible
bits that install on, and run correctly on, the most variations
of the same base OS and hardware architecture.
These usually represent what is often called the
least common denominator platforms.
It is understood that most developers will NOT be using these
specific platforms, and in fact creating these specific platforms
may be difficult due to the age of some of this software.
The minimum OS and C/C++ compiler versions needed for building the
Base OS and Architecture
Linux X86 (32bit)
Red Hat Enterprise Linux 4
Linux X64 (64bit)
Red Hat Enterprise Linux 4
Solaris SPARC (32bit)
Solaris 10 + patches
for patch downloads.
Sun Studio 11
Solaris SPARCV9 (64bit)
Solaris 10 + patches
for patch downloads.
Sun Studio 11
Solaris X86 (32bit)
Solaris 10 + patches
for patch downloads.
Sun Studio 11
Solaris X64 (64bit)
Solaris 10 + patches
for patch downloads.
Sun Studio 11
Windows X86 (32bit)
Windows XP
Microsoft Visual Studio .NET 2003 Professional
Windows X64 (64bit)
Windows Server 2003 - Enterprise x64 Edition
Microsoft Platform SDK - April 2005
We won't be listing all the possible environments, but
we will try to provide what information we have available to us.
In addition to needing the Bootstrap JDK and the Binary Plugs,
when building on Ubuntu you will need to
make sure certain packages are installed.
In particular, certain X11 packages, make, m4, gawk, gcc 4,
binutils, cups, freetype
Ubuntu 6.06
The following list of packages for Ubuntu 6.06 is a working set that
does appear to work.
Note that it's quite possible that some of these
packages are not required, so anyone discovering that some of the
packages listed below are NOT required,
please let the
team know.
All the packages below can be installed with the
Synaptic Package manager provided with the base Ubuntu 6.06 release.
binutils (2.16.1cvsubuntu2.1)
cpp (4:4.0.3-1)
cpp-4.0 (4.0.3-1ubuntu5)
libfreetype6-dev
g++ (4:4.0.3-1)
g++-4.0 (4.0.3-1ubuntu5)
gawk (1:3.1.5-2build1)
gcc (4:4.0.3-1)
gcc-4.0 (4.0.3-1ubuntu5)
libasound2-dev (1.0.10-2ubuntu4)
libc6 (2.3.6-0ubuntu20) to 2.3.6-0ubuntu20.4
libc6-dev (2.3.6-0ubuntu20.4)
libc6-i686 (2.3.6-0ubuntu20) to 2.3.6-0ubuntu20.4
libcupsys2-dev (1.2.2-0ubuntu0.6.06)
libgcrypt11-dev (1.2.2-1)
libgnutls-dev (1.2.9-2ubuntu1.1)
libgnutls12 (1.2.9-2ubuntu1) to 1.2.9-2ubuntu1.1
libgpg-error-dev (1.1-4)
libice-dev (2:1.0.0-0ubuntu2)
liblockfile1 (1.06.1)
libopencdk8-dev (0.5.7-2)
libpopt-dev (1.7-5)
libsm-dev (2:1.0.0-0ubuntu2)
libstdc++6-4.0-dev (4.0.3-1ubuntu5)
libtasn1-2-dev (0.2.17-1ubuntu1)
libx11-dev (2:1.0.0-0ubuntu9)
libxau-dev (1:1.0.0-0ubuntu4)
libxaw-headers (2:1.0.1-0ubuntu3)
libxaw7-dev (2:1.0.1-0ubuntu3)
libxdmcp-dev (1:1.0.0-0ubuntu2)
libxext-dev (2:1.0.0-0ubuntu4)
libxi-dev (2:1.0.0-0ubuntu3)
libxmu-dev (2:1.0.0-0ubuntu3)
libxmu-headers (2:1.0.0-0ubuntu3)
libxmuu-dev (2:1.0.0-0ubuntu3)
libxp-dev (6.8.2-11ubuntu2)
libxpm-dev (1:3.5.4.2-0ubuntu3)
libxrandr-dev (1:1.1.0.2-0ubuntu4)
libxt-dev (1:1.0.0-0ubuntu3)
libxtrap-dev (2:1.0.0-0ubuntu2)
libxtst-dev (2:1.0.1-0ubuntu2)
libxv-dev (2:1.0.1-0ubuntu3)
linux-kernel-headers (2.6.11.2-0ubuntu18)
m4 (1.4.4-1)
make (3.80+3.81.b4-1)
ssl-cert (1.0.13)
x-dev (7.0.4-0ubuntu2)
x11proto-core-dev (7.0.4-0ubuntu2)
x11proto-input-dev (1.3.2-0ubuntu2)
x11proto-kb-dev (1.0.2-0ubuntu2)
x11proto-randr-dev (1.1.2-0ubuntu2)
x11proto-record-dev (1.13.2-0ubuntu2)
x11proto-trap-dev (3.4.3-0ubuntu2)
x11proto-video-dev (2.2.2-0ubuntu2)
x11proto-xext-dev (7.0.2-0ubuntu2)
xlibs-dev (7.0.0-0ubuntu45)
zlib1g-dev (1:1.2.3-6ubuntu4)
This file often describes specific requirements for what we call the
"minimum build environments" (MBE) for the JDK.
Building with the MBE will generate the most compatible
bits that install on, and run correctly on, the most variations
of the same base OS and hardware architecture.
These usually represent what is often called the
least common denominator platforms.
It is understood that most developers will NOT be using these
specific platforms, and in fact creating these specific platforms
may be difficult due to the age of some of this software.
The minimum OS and C/C++ compiler versions needed for building the
Base OS and Architecture
Linux X86 (32bit)
Red Hat Enterprise Linux 4
Linux X64 (64bit)
Red Hat Enterprise Linux 4
Solaris SPARC (32bit)
Solaris 10 + patches
for patch downloads.
Sun Studio 11
Solaris SPARCV9 (64bit)
Solaris 10 + patches
for patch downloads.
Sun Studio 11
Solaris X86 (32bit)
Solaris 10 + patches
for patch downloads.
Sun Studio 11
Solaris X64 (64bit)
Solaris 10 + patches
for patch downloads.
Sun Studio 11
Windows X86 (32bit)
Windows XP
Microsoft Visual Studio .NET 2003 Professional
Windows X64 (64bit)
Windows Server 2003 - Enterprise x64 Edition
Microsoft Platform SDK - April 2005
We won't be listing all the possible environments, but
we will try to provide what information we have available to us.
In addition to needing the Bootstrap JDK and the Binary Plugs,
when building on Ubuntu you will need to
make sure certain packages are installed.
In particular, certain X11 packages, make, m4, gawk, gcc 4,
binutils, cups, freetype
Ubuntu 6.06
The following list of packages for Ubuntu 6.06 is a working set that
does appear to work.
Note that it's quite possible that some of these
packages are not required, so anyone discovering that some of the
packages listed below are NOT required,
please let the
team know.
All the packages below can be installed with the
Synaptic Package manager provided with the base Ubuntu 6.06 release.
binutils (2.16.1cvsubuntu2.1)
cpp (4:4.0.3-1)
cpp-4.0 (4.0.3-1ubuntu5)
libfreetype6-dev
g++ (4:4.0.3-1)
g++-4.0 (4.0.3-1ubuntu5)
gawk (1:3.1.5-2build1)
gcc (4:4.0.3-1)
gcc-4.0 (4.0.3-1ubuntu5)
libasound2-dev (1.0.10-2ubuntu4)
libc6 (2.3.6-0ubuntu20) to 2.3.6-0ubuntu20.4
libc6-dev (2.3.6-0ubuntu20.4)
libc6-i686 (2.3.6-0ubuntu20) to 2.3.6-0ubuntu20.4
libcupsys2-dev (1.2.2-0ubuntu0.6.06)
libgcrypt11-dev (1.2.2-1)
libgnutls-dev (1.2.9-2ubuntu1.1)
libgnutls12 (1.2.9-2ubuntu1) to 1.2.9-2ubuntu1.1
libgpg-error-dev (1.1-4)
libice-dev (2:1.0.0-0ubuntu2)
liblockfile1 (1.06.1)
libopencdk8-dev (0.5.7-2)
libpopt-dev (1.7-5)
libsm-dev (2:1.0.0-0ubuntu2)
libstdc++6-4.0-dev (4.0.3-1ubuntu5)
libtasn1-2-dev (0.2.17-1ubuntu1)
libx11-dev (2:1.0.0-0ubuntu9)
libxau-dev (1:1.0.0-0ubuntu4)
libxaw-headers (2:1.0.1-0ubuntu3)
libxaw7-dev (2:1.0.1-0ubuntu3)
libxdmcp-dev (1:1.0.0-0ubuntu2)
libxext-dev (2:1.0.0-0ubuntu4)
libxi-dev (2:1.0.0-0ubuntu3)
libxmu-dev (2:1.0.0-0ubuntu3)
libxmu-headers (2:1.0.0-0ubuntu3)
libxmuu-dev (2:1.0.0-0ubuntu3)
libxp-dev (6.8.2-11ubuntu2)
libxpm-dev (1:3.5.4.2-0ubuntu3)
libxrandr-dev (1:1.1.0.2-0ubuntu4)
libxt-dev (1:1.0.0-0ubuntu3)
libxtrap-dev (2:1.0.0-0ubuntu2)
libxtst-dev (2:1.0.1-0ubuntu2)
libxv-dev (2:1.0.1-0ubuntu3)
linux-kernel-headers (2.6.11.2-0ubuntu18)
m4 (1.4.4-1)
make (3.80+3.81.b4-1)
ssl-cert (1.0.13)
x-dev (7.0.4-0ubuntu2)
x11proto-core-dev (7.0.4-0ubuntu2)
x11proto-input-dev (1.3.2-0ubuntu2)
x11proto-kb-dev (1.0.2-0ubuntu2)
x11proto-randr-dev (1.1.2-0ubuntu2)
x11proto-record-dev (1.13.2-0ubuntu2)
x11proto-trap-dev (3.4.3-0ubuntu2)
x11proto-video-dev (2.2.2-0ubuntu2)
x11proto-xext-dev (7.0.2-0ubuntu2)
xlibs-dev (7.0.0-0ubuntu45)
zlib1g-dev (1:1.2.3-6ubuntu4)
Ubuntu 7.04
Using the Synaptic Package Manager, download the following
packages (double indented packages are automatically aquired
due to package dependencies):
build-essential
libstdc++6.4.1-dev
linux-libc-dev
libasound2-dev
libmotif3-dev
libcupsys2-dev
libgcrypt11-dev
lgnutls-dev
libgpg-error-dev
liblzo-dev
libopencdk8-dev
libpopt-dev
libtasn1-3-dev
zlib1g-dev
sun-java6-jdk
java-common
odbcinst1debian1
sun-java6-bin
sun-java6-jre
x11proto-print-dev
libxaw7-dev
libxaw-headers
libfreetype6-dev
The source code for the OpenJDK is delivered in a set of
directories:
langtools,
The hotspot directory contains the source code and make
files for building the OpenJDK Hotspot Virtual Machine.
The langtools directory contains the source code and make
files for building the OpenJDK javac and language tools.
The corba directory contains the source code and make
files for building the OpenJDK Corba files.
The jaxws directory contains the source code and make
files for building the OpenJDK JAXWS files.
The jaxp directory contains the source code and make
files for building the OpenJDK JAXP files.
The jdk directory contains the source code and make files for
building the OpenJDK runtime libraries and misc files.
The top level Makefile (or control/Makefile)
is used to build the entire OpenJDK.
Building the
is done with a gmake
command line and various
environment or make variable settings that direct the make rules
to where various components have been installed.
Where possible the makefiles will attempt to located the various
components in the default locations or any component specific
variable settings.
When the normal defaults fail or components cannot be found,
the various
ALT_* variables (alternates)
can be used to help the makefiles locate components.
Refer to the bash/sh/ksh setup file
jdk/make/jdk_generic_profile.sh
if you need help in setting up your environment variables.
A build could be as simple as:
Ubuntu 7.04
Using the Synaptic Package Manager, download the following
packages (double indented packages are automatically aquired
due to package dependencies):
build-essential
libstdc++6.4.1-dev
linux-libc-dev
libasound2-dev
libmotif3-dev
libcupsys2-dev
libgcrypt11-dev
lgnutls-dev
libgpg-error-dev
liblzo-dev
libopencdk8-dev
libpopt-dev
libtasn1-3-dev
zlib1g-dev
sun-java6-jdk
java-common
odbcinst1debian1
sun-java6-bin
sun-java6-jre
x11proto-print-dev
libxaw7-dev
libxaw-headers
libfreetype6-dev
The source code for the OpenJDK is delivered in a set of
directories:
langtools,
The hotspot directory contains the source code and make
files for building the OpenJDK Hotspot Virtual Machine.
The langtools directory contains the source code and make
files for building the OpenJDK javac and language tools.
The corba directory contains the source code and make
files for building the OpenJDK Corba files.
The jaxws directory contains the source code and make
files for building the OpenJDK JAXWS files.
The jaxp directory contains the source code and make
files for building the OpenJDK JAXP files.
The jdk directory contains the source code and make files for
building the OpenJDK runtime libraries and misc files.
The top level Makefile
is used to build the entire OpenJDK.
Building the OpenJDK
is done with a gmake
command line and various
environment or make variable settings that direct the make rules
to where various components have been installed.
Where possible the makefiles will attempt to located the various
components in the default locations or any component specific
variable settings.
When the normal defaults fail or components cannot be found,
the various
ALT_* variables (alternates)
can be used to help the makefiles locate components.
Refer to the bash/sh/ksh setup file
jdk/make/jdk_generic_profile.sh
if you need help in setting up your environment variables.
A build could be as simple as:
. jdk/make/jdk_generic_profile.sh
gmake sanity && gmake
Of course ksh or sh would work too.
But some customization will probably be necessary.
The sanity rule will make some basic checks on build
dependencies and generate appropriate warning messages
regarding missing, out of date, or newer than expected components
found on your system.
The Makefiles in the
are only valid when used with the
GNU version of the utility command make
A few notes about using GNU make:
In general, you need GNU make version 3.78.1 or newer.
Place the location of the GNU make binary in the PATH.
The /usr/bin/make command should work fine for you.
Do NOT use /usr/bin/make on Solaris.
If your Solaris system has the software
from the Solaris Companion CD installed,
you should use gmake
which will be located in either the /opt/sfw/bin or
/usr/sfw/bin directory.
Of course ksh or sh would work too.
But some customization will probably be necessary.
The sanity rule will make some basic checks on build
dependencies and generate appropriate warning messages
regarding missing, out of date, or newer than expected components
found on your system.
The Makefiles in the OpenJDK are only valid when used with the
GNU version of the utility command make
A few notes about using GNU make:
In general, you need GNU make version 3.78.1 or newer.
Place the location of the GNU make binary in the PATH.
The /usr/bin/make command should work fine for you.
Do NOT use /usr/bin/make on Solaris.
If your Solaris system has the software
from the Solaris Companion CD installed,
you should use gmake
which will be located in either the /opt/sfw/bin or
/usr/sfw/bin directory.
Make sure you start your build inside a bash/sh/ksh shell.
WARNING: Watch out for make version 3.81, it may
not work due to a lack of support for drive letter paths
like C:/. See
Use a 3.80 version, or find a newer
version that has this problem fixed.
The older 3.80 version of make.exe can be downloaded with this
Also see the
on this topic.
Information on GNU make, and access to ftp download sites, are
available on the
The latest source to GNU make is available at
i586 only:
The minimum recommended hardware for building the Linux version
is a Pentium class processor or better, at least 256 MB of RAM, and
approximately 1.5 GB of free disk space.
The minimum recommended hardware for building the Linux
version is an AMD Opteron class processor, at least 512 MB of RAM, and
approximately 4 GB of free disk space.
The build will use the tools contained in
of a standard installation of the Linux operating environment.
You should ensure that these directories are in your
Note that some Linux systems have a habit of pre-populating
your environment variables for you, for example JAVA_HOME
might get pre-defined for you to refer to the JDK installed on
your Linux system.
You will need to unset JAVA_HOME.
It's a good idea to run env and verify the
environment variables you are getting from the default system
settings make sense for building the
Install the
Install the
Install or upgrade the .
Install the
The minimum recommended hardware for building the
Solaris SPARC version is an UltraSPARC with 512 MB of RAM.
For building
the Solaris x86 version, a Pentium class processor or better and at
least 512 MB of RAM are recommended.
Approximately 1.4 GB of free disk
space is needed for a 32-bit build.
If you are building the 64bit version, you should
run the command "isainfo -v" to verify that you have a
64-bit installation, it should say sparcv9 or
An additional 7 GB of free disk space is needed
for a 64-bit build.
The build uses the tools contained in /usr/ccs/bin
and /usr/bin of a standard developer or full installation of
the Solaris operating environment.
Solaris patches specific to the JDK can be downloaded from the
You should ensure that the latest patch cluster for
your version of the Solaris operating environment has also
been installed.
Install the
Install the
Install the
Install the
i586 only:
The minimum recommended hardware for building the 32bit or X86
Windows version is an Pentium class processor or better, at least
512 MB of RAM, and approximately 600 MB of free disk space.
NOTE: The Windows 2000 build machines need to use the
file system NTFS.
Build machines formatted to FAT32 will not work
because FAT32 doesn't support case-sensitivity in file names.
The minimum recommended hardware for building
the Windows X64 version is an AMD Opteron class processor, at least 1
GB of RAM, and approximately 10 GB of free disk space.
Make sure you start your build inside a bash/sh/ksh shell.
WARNING: Watch out for make version 3.81, it may
not work due to a lack of support for drive letter paths
like C:/. Use a 3.80 version, or find a newer
version that has this problem fixed.
Information on GNU make, and access to ftp download sites, are
available on the
The latest source to GNU make is available at
i586 only:
The minimum recommended hardware for building the Linux version
is a Pentium class processor or better, at least 256 MB of RAM, and
approximately 1.5 GB of free disk space.
The minimum recommended hardware for building the Linux
version is an AMD Opteron class processor, at least 512 MB of RAM, and
approximately 4 GB of free disk space.
The build will use the tools contained in
of a standard installation of the Linux operating environment.
You should ensure that these directories are in your
Note that some Linux systems have a habit of pre-populating
your environment variables for you, for example JAVA_HOME
might get pre-defined for you to refer to the JDK installed on
your Linux system.
You will need to unset JAVA_HOME.
It's a good idea to run env and verify the
environment variables you are getting from the default system
settings make sense for building the
Install the
Install the
Install the
Install or upgrade the .
The minimum recommended hardware for building the
Solaris SPARC version is an UltraSPARC with 512 MB of RAM.
For building
the Solaris x86 version, a Pentium class processor or better and at
least 128 MB of RAM are recommended.
Approximately 1.4 GB of free disk
space is needed for a 32-bit build.
If you are building the 64bit version, you should
run the command "isainfo -v" to verify that you have a
64-bit installation.
An additional 7 GB of free disk space is needed
for a 64-bit build.
The build uses the tools contained in /usr/ccs/bin
and /usr/bin of a standard developer or full installation of
the Solaris operating environment.
Install the
Install the
Install the
Install the
i586 only:
The minimum recommended hardware for building the 32bit or X86
Windows version is an Pentium class processor or better, at least
512 MB of RAM, and approximately 600 MB of free disk space.
NOTE: The Windows 2000 build machines need to use the
file system NTFS.
Build machines formatted to FAT32 will not work
because FAT32 doesn't support case-sensitivity in file names.
The minimum recommended hardware for building
the Windows X64 version is an AMD Opteron class processor, at least 1
GB of RAM, and approximately 10 GB of free disk space.
Note that GNU make is a historic utility and is based very
heavily on shell scripting, so it does not tolerate the Windows habit
of having spaces in pathnames or the use of the \characters in pathnames.
Luckily on most Windows systems, you can use /instead of \, and
there is always a 'short' pathname without spaces for any path that
contains spaces.
Unfortunately, this short pathname can be somewhat dynamic and the
formula is difficult to explain.
You can use cygpath utility to map pathnames with spaces
or the \character into the C:/ style of pathname
(called 'mixed'), e.g.
cygpath -s -m "path".
The makefiles will try to translate any pathnames supplied
to it into the C:/ style automatically.
Note that use of CYGWIN creates a unique problem with regards to
setting . Normally on Windows
the PATH variable contains directories
separated with the ";" character (Solaris and Linux uses ":").
With CYGWIN, it uses ":", but that means that paths like "C:/path"
cannot be placed in the CYGWIN version
of PATH and
instead CYGWIN uses something like /cygdrive/c/path
which CYGWIN understands, but only CYGWIN understands.
So be careful with paths on Windows.
Install the
Install the
Install the
Install the
Setup all environment variables for compilers
Depending on the platform, the
build process has some basic
dependencies on components not part of the
Some of these are specific to a platform, some even specific to
an architecture.
Each dependency will have a set of ALT variables that can be set
to tell the makefiles where to locate the component.
In most cases setting these ALT variables may not be necessary
and the makefiles will find defaults on the system in standard
install locations or through component specific variables.
builds require access to the previously released
JDK 6, this is often called a bootstrap JDK.
The JDK 6 binaries can be downloaded from Sun's
For build performance reasons
is very important that this bootstrap JDK be made available on the
local disk of the machine doing the build.
You should always set
to point to the location of
the bootstrap JDK installation, this is the directory pathname
that contains a bin, lib, and include
It's also a good idea to also place its bin directory
in the PATH environment variable, although it's
not required.
Some pre-installed JDK images may be available to you in the
directory /usr/jdk/instances.
If you don't set
the makefiles will look in that location for a JDK it can use.
Not all of the source code that makes up the JDK is available
under an open-source license.
In order to build an OpenJDK binary from source code,
you must first download and install the appropriate
binary plug bundles from the OpenJDK, go to the
site and select
- the "Bundles(6)" link.
During the OpenJDK build process these "binary plugs"
for the encumbered components will be copied into your
resulting OpenJDK binary build image.
These binary plug files are only for the purpose of
building an OpenJDK binary.
Make sure you set
to the root of this installation.
for a better understanding of the Certificate Authority (CA).
A certificates file named "cacerts"
represents a system-wide keystore with CA certificates.
In JDK and JRE
binary bundles, the "cacerts" file contains root CA certificates from
several public CAs (e.g., VeriSign, Thawte, and Baltimore).
The source contain a cacerts file
without CA root certificates.
Formal JDK builders will need to secure
permission from each public CA and include the certificates into their
own custom cacerts file.
Failure to provide a populated cacerts file
will result in verification errors of a certificate chain during runtime.
The variable
can be used to override the default location of the
cacerts file that will get placed in your build.
By default an empty cacerts file is provided and that should be
fine for most JDK developers.
Note that GNU make is a historic utility and is based very
heavily on shell scripting, so it does not tolerate the Windows habit
of having spaces in pathnames or the use of the \characters in pathnames.
Luckily on most Windows systems, you can use /instead of \, and
there is always a 'short' pathname without spaces for any path that
contains spaces.
Unfortunately, this short pathname can be somewhat dynamic and the
formula is difficult to explain.
You can use cygpath utility to map pathnames with spaces
or the \character into the C:/ style of pathname
(called 'mixed'), e.g.
cygpath -s -m "path".
The makefiles will try to translate any pathnames supplied
to it into the C:/ style automatically.
Note that use of CYGWIN creates a unique problem with regards to
setting . Normally on Windows
the PATH variable contains directories
separated with the ";" character (Solaris and Linux uses ":").
With CYGWIN, it uses ":", but that means that paths like "C:/path"
cannot be placed in the CYGWIN version
of PATH and
instead CYGWIN uses something like /cygdrive/c/path
which CYGWIN understands, but only CYGWIN understands.
So be careful with paths on Windows.
The GNU gcc compiler version should be 3.2.2 or newer.
The binutils package should be 2.11.93.0.2-11 or newer.
The compiler used should be the default compiler installed
in /usr/bin.
Install the
Install the
Install the
Install the
Setup all environment variables for compilers
At a minimum, the
(containing version 5.8 of the C and C++ compilers) is required,
with patches from the
to point to the location of
the compiler binaries, and place this location in the PATH.
The Sun Studio Express compilers at:
are also an option, although these compilers have not
been extensively used yet.
Depending on the platform, the OpenJDK build process has some basic
dependencies on components not part of the OpenJDK sources.
Some of these are specific to a platform, some even specific to
an architecture.
Each dependency will have a set of ALT variables that can be set
to tell the makefiles where to locate the component.
In most cases setting these ALT variables may not be necessary
and the makefiles will find defaults on the system in standard
install locations or through component specific variables.
All OpenJDK builds require access to the previously released
JDK 6, this is often called a bootstrap JDK.
Normally the "boot" JDK is the previously released version
of the JDK, so it's unusual for a JDK 6 build like this to
require a JDK 6 "boot".
Unfortunately, it is currently required due to some JDK 6
dependencies in some of the sources.
The JDK 6 binaries can be downloaded from Sun's
For build performance reasons
is very important that this bootstrap JDK be made available on the
local disk of the machine doing the build.
You should always set
to point to the location of
the bootstrap JDK installation, this is the directory pathname
that contains a bin, lib, and include
It's also a good idea to also place its bin directory
in the PATH environment variable, although it's
not required.
Some pre-installed JDK images may be available to you in the
directory /usr/jdk/instances.
If you don't set
the makefiles will look in that location for a JDK it can use.
Not all of the source code that makes up the JDK is available
under an open-source license.
This is a temporary situation and these binary plugs will be
replaced with fully open source replacements as soon as possible.
So currently, in order to build a complete OpenJDK image,
you must first download and install the appropriate
binary plug bundles for the OpenJDK, go to the
site and select
"Bundles(6)"
link and download the binaryplugs for
your particular platform.
The file downloaded is a jar file that must be extracted by running
the jar file with:
java -jar jdk-6-ea-plug-bnn-os-arch-dd_month_year.jar
A prompt will be issued for acceptance of these binary plug files.
During the OpenJDK build process these "binary plugs"
for the encumbered components will be copied into your
resulting OpenJDK binary build image.
These binary plug files are only for the purpose of
building an OpenJDK binary.
Make sure you set
to the root of this installation.
setting is only needed if you are not building the entire
JDK. For example, if you have built the entire JDK once, and
wanted to avoid repeatedly building the Hotspot VM, you could
set this to the location of the previous JDK install image
and the build will copy the needed files from this import area.
for a better understanding of the Certificate Authority (CA).
A certificates file named "cacerts"
represents a system-wide keystore with CA certificates.
In JDK and JRE
binary bundles, the "cacerts" file contains root CA certificates from
several public CAs (e.g., VeriSign, Thawte, and Baltimore).
The source contain a cacerts file
without CA root certificates.
Formal JDK builders will need to secure
permission from each public CA and include the certificates into their
own custom cacerts file.
Failure to provide a populated cacerts file
will result in verification errors of a certificate chain during runtime.
The variable
can be used to override the default location of the
cacerts file that will get placed in your build.
By default an empty cacerts file is provided and that should be
fine for most JDK developers.
The GNU gcc compiler version should be 3.2.2 or newer.
The binutils package should be 2.11.93.0.2-11 or newer.
The compiler used should be the default compiler installed
in /usr/bin.
Older Linux systems may require a gcc and bunutils update.
The Redhat Enterprise Advanced Server 2.1 update 2 system
is one of these systems.
RedHat Linux users can obtain this binutils package from
You will need to remove the default compiler and binutils
packages and install the required packages
into the default location on the system.
However if you have a new video card driver, like
Geforce 4 it is best to use
the same compiler as the kernel was built with to
build the new video card driver module.
So you should build the modules before making this change.
At a minimum, the
(containing version 5.8 of the C and C++ compilers) is required,
with patches from the
to point to the location of
the compiler binaries, and place this location in the PATH.
The Sun Studio Express compilers at:
are also an option, although these compilers have not
been extensively used yet.
The 32-bit OpenJDK Windows build
requires Microsoft Visual Studio .NET 2003 (VS2003) Professional
Edition compiler.
The compiler and other tools are expected to reside
in the location defined by the variable VS71COMNTOOLS which
is set by the Microsoft Visual Studio .NET installer.
Once the compiler is installed,
it is recommended that you run VCVARS32.BAT
to set the compiler environment variables
prior to building the
The above environment variables MUST be set.
The Microsoft Visual Studio .NET 2005 (VS2005) compiler
will not work at this time due to the new runtime dll
and the manifest requirements.
On X64, the Microsoft Platform Software
Development Kit (SDK), April 2005 Edition compiler,
is required for building the OpenJDK
because it contains the C/C++ compiler.
You will need to minimally install the Core SDK and
the MDAC SDK features of this compiler.
Once the Platform SDK is installed,
it is recommended that you run SetEnv.Cmd /X64
to set the compiler environment variables
prior to building the
The above environment variables MUST be set.
Note that this compiler may say it's version is a
Microsoft Visual Studio .NET 2005 (VS2005), but be careful,
it will not match the official VS2005 product.
This Platform SDK compiler is only used on X64 builds.
Version 2.2 (November 3rd 1997) or newer of the zip utility
and version 5.12 or newer of the unzip utility is needed
to build the JDK.
With Solaris, Linux, and Windows CYGWIN, the zip and unzip
utilities installed on the system should be fine.
Information and the source code for
ZIP.EXE and UNZIP.EXE is available on the
CUPS header files are required for building the
OpenJDK on Solaris.
The Solaris header files can be obtained by installing
the package SFWcups from the Solaris Software
Companion CD/DVD, these often will be installed into
/opt/sfw/cups.
CUPS header files are required for building the
OpenJDK on Linux.
The Linux header files are usually available from a "cups"
development package, it's recommended that you try and use
the package provided by the particular version of Linux that
you are using.
The CUPS header files can always be downloaded from
The variable
can be used to override the default location of the
CUPS Header files.
Motif headers (not libraries) are required for building the
OpenJDK 6.
Normally these files can be found on Solaris systems
at /usr/include/Xm, so on Solaris systems no further downloads
should be needed.
On Linux, your particular Linux distribution may provide a
"motif" development package you can install. If this package
installs the files into /usr/include/Xm, no further action should
be needed.
An acceptable version of these Motif header files are
available in the source bundle
You would need to install the package and set the environment variable
to refer to the top of this installation.
Version 2.3 or newer of FreeType is required for building the OpenJDK.
On Unix systems required files can be available as part of your
distribution (while you still may need to upgrade them).
Note that you need development version of package that
includes both FreeType library and header files.
You can always download latest FreeType version from the
Makefiles will try to pick FreeType from /usr/lib and /usr/include.
In case it is installed elsewhere you will need to set environment
to refer to place where library and header files are installed.
Linux only:
Version 0.9.1 or newer of the ALSA files are
required for building the OpenJDK on Linux.
These Linux files are usually available from an "alsa"
of "libasound"
development package, it's highly recommended that you try and use
the package provided by the particular version of Linux that
you are using.
The makefiles will check this emit a sanity error if it is
missing or the wrong version.
In particular, older Linux systems will likely not have the
right version of ALSA installed, for example
Redhat AS 2.1 U2 and SuSE 8.1 do not include a sufficiently
recent ALSA distribution.
On rpm-based systems, you can see if ALSA is installed by
running this command:
rpm -qa | grep alsa
Both alsa and alsa-devel packages are needed.
If your distribution does not come with ALSA, and you can't
find ALSA packages built for your particular system,
you can try to install the pre-built ALSA rpm packages from
Note that installing a newer ALSA could
break sound output if an older version of ALSA was previously
installed on the system, but it will enable JDK compilation.
Installation: execute as root
[i586]: rpm -Uv --force alsa-lib-devel-0.9.1-rh61.i386.rpm
[x64]: rpm -Uv --force alsa-lib-devel-0.9.8-amd64.x86_64.rpm
Uninstallation:
[i586]: rpm -ev alsa-lib-devel-0.9.1-rh61
[x64]:rpm -ev alsa-lib-devel-0.9.8-amd64
Make sure that you do not link to the static library
(libasound.a),
by verifying that the dynamic library (libasound.so) is
correctly installed in /usr/lib.
As a last resort you can go to the
and build it from
Download driver and library
source tarballs from
As root, execute the following
commands (you may need to adapt the version number):
$ tar xjf alsa-driver-0.9.1.tar.bz2
$ cd alsa-driver-0.9.1
$ ./configure
$ make install
$ tar xjf alsa-lib-0.9.1.tar.bz2
$ cd alsa-lib-0.9.1
$ ./configure
$ make install
Should one of the above steps fail, refer to the documentation on
ALSA's home page.
Note that this is a minimum install that enables
building the JDK platform. To actually use ALSA sound drivers, more
steps are necessary as outlined in the documentation on ALSA's homepage.
ALSA can be uninstalled by executing make uninstall first in
the alsa-lib-0.9.1 directory and then in
alsa-driver-0.9.1.
There are no ALT* variables to change the assumed locations of ALSA,
the makefiles will expect to find the ALSA include files and library at:
/usr/include/alsa and /usr/lib/libasound.so.
Windows Specific Dependencies
The 32-bit
Windows build
requires Microsoft Visual Studio .NET 2003 (VS2003) Professional
Edition compiler.
The compiler and other tools are expected to reside
in the location defined by the variable VS71COMNTOOLS which
is set by the Microsoft Visual Studio .NET installer.
Once the compiler is installed,
it is recommended that you run VCVARS32.BAT
to set the compiler environment variables
prior to building the
The above environment variables MUST be set.
The Microsoft Visual Studio .NET 2005 (VS2005) compiler
will not work at this time due to the new runtime dll
and the manifest requirements.
the Microsoft Platform Software
Development Kit (SDK), April 2005 Edition compiler, is required for
building the
because it contains the C/C++ compiler.
You will need to minimally install the Core SDK and
the MDAC SDK features of this compiler.
Once the Platform SDK is installed,
it is recommended that you run SetEnv.Cmd /X64
to set the compiler environment variables
prior to building the
The above environment variables MUST be set.
Note that this compiler may say it's version is a
Microsoft Visual Studio .NET 2005 (VS2005), but be careful,
it will not match the official VS2005 product.
This Platform SDK compiler is only used on X64 builds.
CUPS header files are required for building the
OpenJDK on Solaris.
The Solaris header files can be obtained by installing
the package SFWcups from the Solaris Software
Companion CD/DVD, these often will be installed into
/opt/sfw/cups.
CUPS header files are required for building the
OpenJDK on Linux.
The Linux header files are usually available from a "cups"
development package, it's recommended that you try and use
the package provided by the particular version of Linux that
you are using.
The CUPS header files can always be downloaded from
The variable
can be used to override the default location of the
CUPS Header files.
Motif headers (not libraries) are required for building the
Normally these files can be found on Solaris systems
at /usr/include/Xm, so on Solaris systems no further downloads
should be needed.
On Linux, your particular Linux distribution may provide a
"motif" development package you can install. If this package
installs the files into /usr/include/Xm, no further action should
be needed.
An acceptable version of these Motif header files are
available in the source bundle
You would need to install the package and set the environment variable
to refer to the top of this installation.
Version 2.3 or newer of FreeType is required for building the OpenJDK.
On Unix systems required files can be available as part of your
distribution (while you still may need to upgrade them).
Note that you need development version of package that
includes both FreeType library and header files.
You can always download latest FreeType version from the
Makefiles will try to pick FreeType from /usr/lib and /usr/include.
In case it is installed elsewhere you will need to set environment
to refer to place where library and header files are installed.
Linux only:
Version 0.9.1 or newer of the ALSA files are
required for building the
OpenJDK on Linux.
These Linux files are usually available from an "alsa"
of "libasound"
development package, it's recommended that you try and use
the package provided by the particular version of Linux that
you are using.
The makefiles will check this emit a sanity error if it is
missing or the wrong version.
As a last resort you can go to the
Windows Specific Dependencies
Unix Command Tools ()
requires access to a set of unix command tools
on Windows which can be supplied by
requires CYGWIN version 1.5.12 or newer.
Information about CYGWIN can
be obtained from the CYGWIN website at
By default CYGWIN doesn't install all the tools required for building
the OpenJDK.
Along with the default installation, you need to install
the following tools.
Unix Command Tools ()
The OpenJDK requires access to a set of unix command tools
on Windows which can be supplied by
The OpenJDK build requires CYGWIN version 1.5.12 or newer.
Information about CYGWIN can
be obtained from the CYGWIN website at
By default CYGWIN doesn't install all the tools required for building
the OpenJDK.
Along with the default installation, you need to install
the following tools.
Binary Name
Description
binutils: The GNU assembler, linker and binary
make: The GNU version of the 'make' utility
Interpreters
m4: GNU implementation of the traditional Unix macro
cpio: A program to manage archives of files
awk: Pattern-directed scanning and processing language
file: Determines file type using 'magic' numbers
zip: Package and compress (archive) files
unzip: Extract compressed files in a ZIP archive
free: Display amount of free and used memory in the system
Note that the CYGWIN software can conflict with other non-CYGWIN
software on your Windows system.
CYGWIN provides a
known issues and problems, of particular interest is the
section on
Binary Name
Description
binutils: The GNU assembler, linker and binary
make: The GNU version of the 'make' utility
Interpreters
m4: GNU implementation of the traditional Unix macro
cpio: A program to manage archives of files
file: Determines file type using 'magic' numbers
Microsoft DirectX 9.0 SDK (Summer 2004)
headers are required for building
This SDK can be downloaded from
If the link above becomes obsolete, the SDK can be found from
(search with "DirectX 9.0 SDK Update Summer 2004").
The location of this SDK can be set with
but it's normally found via the DirectX environment variable
DXSDK_DIR.
i586 only:
The OpenJDK 32bit build requires access to
MSVCRT.DLL version 6.00.8337.0 or newer.
If the MSVCRT.DLL is not installed in
the system32 directory set the
variable to the location.
The OpenJDK 64bit build requires access to
MSVCRT.DLL version 7.0.3790.0 or newer, which is
usually supplied by the
If it is not available from the Platform SDK,
variable to the location.
i586 only:
build requires access to
MSVCR71.DLL version 7.10.3052.4 or newer which should be
supplied by the
If the MSVCR71.DLL is not available from the
Visual Studio product
variable to the location.
Once a machine is setup to build the OpenJDK,
the steps to create the build are fairly simple.
The various ALT settings can either be made into
or can be supplied on the
Use the sanity rule to double check all the ALT settings:
[ARCH_DATA_MODEL=32 or 64]
[other "ALT_" overrides]
Start the build with the command:
[ARCH_DATA_MODEL=32 or 64]
[ALT_OUTPUTDIR=output_directory]
[other "ALT_" overrides]
Microsoft DirectX 9.0 SDK (Summer 2004)
headers are required for building
This SDK can be downloaded from
If the link above becomes obsolete, the SDK can be found from
(search with "DirectX 9.0 SDK Update Summer 2004").
The location of this SDK can be set with
but it's normally found via the DirectX environment variable
DXSDK_DIR.
Note that ARCH_DATA_MODEL is really only needed on Solaris to
indicate you want to built the 64-bit version.
And before the Solaris 64-bit binaries can be used, they
must be merged with the binaries from a separate 32-bit build.
The merged binaries may then be used in either 32-bit or 64-bit mode, with
the selection occurring at runtime
with the -d32 or -d64 options.
When the build is completed, you should see the generated
binaries and associated files in the j2sdk-image
directory in the output directory.
The default output directory is
build/platform,
where platform is one of
solaris-sparc
solaris-sparcv9
solaris-i586
solaris-amd64
linux-i586
linux-amd64
windows-i586
windows-amd64
In particular, the
build/platform/j2sdk-image/bin
directory should contain executables for the
OpenJDK tools and utilities.
i586 only:
32bit build requires
access to MSVCRT.DLL
version 6.00.8337.0 or newer.
If the MSVCRT.DLL is not installed in
the system32 directory set the
variable to the location.
The OpenJDK 64bit build requires access to
MSVCRT.DLL version 7.0.3790.0 or newer, which is
usually supplied by the
If it is not available from the Platform SDK,
variable to the location.
You can test that the build completed properly by using the build
to run the various demos that you will find in the
build/platform/j2sdk-image/demo
directory.
The provided regression tests can be run with the jtreg
utility from
Some of the
environment or make variables (just called variables in this
document) that can impact the build are:
i586 only:
build requires access to
MSVCR71.DLL version 7.10.3052.4 or newer which should be
supplied by the
If the MSVCR71.DLL is not available from the
Visual Studio product
variable to the location.
Once a machine is setup to build the
the steps to create the
build are fairly simple.
The various ALT settings can either be made into
or can be supplied on the
Use the sanity rule to double check all the ALT settings:
[ARCH_DATA_MODEL=32 or 64]
[other "ALT_" overrides]
Start the build with the command:
[ARCH_DATA_MODEL=32 or 64]
[ALT_OUTPUTDIR=output_directory]
[other "ALT_" overrides]
Note that ARCH_DATA_MODEL is really only needed on Solaris to
indicate you want to built the 64-bit version.
And before the Solaris 64-bit binaries can be used, they
must be merged with the binaries from a separate 32-bit build.
The merged binaries may then be used in either 32-bit or 64-bit mode, with
the selection occurring at runtime
with the -d32 or -d64 options.
When the build is completed, you should see the generated
binaries and associated files in the j2sdk-image
directory in the output directory.
The default output directory is
build/platform,
where platform is one of
solaris-sparc
solaris-sparcv9
solaris-i586
solaris-amd64
linux-i586
linux-amd64
windows-i586
windows-amd64
In particular, the
build/platform/j2sdk-image/bin
directory should contain executables for the
tools and utilities.
You can test that the build completed properly by using the build
to run the various demos that you will find in the
build/platform/j2sdk-image/demo
directory.
The provided regression tests can be run with the jtreg
utility from
-Some of the
-environment or make variables (just called variables in this
-document) that can impact the build are:
Typically you want to set the PATH to include:
The location of the GNU make binary
The location of the JDK 6 java
The location of the C/C++ compilers
The location or locations for the Unix command utilities
(e.g. /usr/bin)
The ARCH_DATA_MODEL variable
is used to specify whether the build is to generate 32-bit or 64-bit
The Solaris build supports either 32-bit or 64-bit builds, but
Windows and Linux will support only one, depending on the specific
OS being used.
Normally, setting this variable is only necessary on Solaris.
Set ARCH_DATA_MODEL to 32 for generating 32-bit binaries,
or to 64 for generating 64-bit binaries.
The location of the bootstrap JDK installation.
for more information.
You should always install your own local Bootstrap JDK and
always set ALT_BOOTDIR explicitly.
An override for specifying the (absolute) path of where the
build output is to go.
The default output directory will be build/platform.
The location of the C/C++ compiler.
The default varies depending on the platform.
The location of the
The default will refer to
jdk/src/share/lib/security/cacerts.
The location of the binary plugs installation.
for more information.
You should always have a local copy of a
recent Binary Plugs install image
and set this variable to that location.
The location of the CUPS header files.
for more information.
If this path does not exist the fallback path is
/usr/include.
The location of the Motif 2.1 headers and libraries.
for details.
The location of the FreeType shared library.
for details.
The location of the FreeType header files.
for details.
Windows specific:
Typically you want to set the PATH to include:
The location of the GNU make binary
The location of the Bootstrap JDK java
The location of the C/C++ compilers
The location or locations for the Unix command utilities
(e.g. /usr/bin)
The location of the Microsoft Visual Studio .NET 2003
tools 'bin' directory.
The default is usually derived from
The milestone name for the build (e.g."beta").
The default value is "internal".
BUILD_NUMBER
The location of the
The default will be to try and use the DirectX environment
variable DXSDK_DIR,
failing that, look in C:/DXSDK.
The build number for the build (e.g. "b27").
The default value is "b00".
The ARCH_DATA_MODEL variable
is used to specify whether the build is to generate 32-bit or 64-bit
The Solaris build supports either 32-bit or 64-bit builds, but
Windows and Linux will support only one, depending on the specific
OS being used.
Normally, setting this variable is only necessary on Solaris.
Set ARCH_DATA_MODEL to 32 for generating 32-bit binaries,
or to 64 for generating 64-bit binaries.
The location of the
The location of the bootstrap JDK installation.
for more information.
You should always install your own local Bootstrap JDK and
always set ALT_BOOTDIR explicitly.
i586 only:
The location of the
The location of the binary plugs installation.
for more information.
You should always have a local copy of a
recent Binary Plugs install image
and set this variable to that location.
The location of a previously built JDK installation.
for more information.
An override for specifying the (absolute) path of where the
build output is to go.
The default output directory will be build/platform.
The location of the C/C++ compiler.
The default varies depending on the platform.
The location of the
The default will refer to
jdk/src/share/lib/security/cacerts.
The location of the CUPS header files.
for more information.
If this path does not exist the fallback path is
/usr/include.
The location of the Motif 2.1 headers and libraries.
for details.
The location of the FreeType shared library.
for details.
The location of the FreeType header files.
for details.
The default root location of the devtools.
The default value is
$(ALT_SLASH_JAVA)/devtools.
The location of tools like the
binaries, but might also contain the GNU make utility
So this area is a bit of a grab bag, especially on Windows.
The default value depends on the platform and
Unix Commands being used.
On Linux the default will be
$(ALT_JDK_DEVTOOLS_PATH)/linux/bin,
on Solaris
$(ALT_JDK_DEVTOOLS_PATH)/{sparc,i386}/bin,
on Windows with MKS
%SYSTEMDRIVE%/UTILS,
and on Windows with CYGWIN
An override for specifying where the
Unix command set are located.
The default location varies depending on the platform,
"%SYSTEMDRIVE%/MKSNT" or
$(ROOTDIR) on Windows with MKS, otherwise it's
"/bin" or /usr/bin.
Solaris only:
An override for specifying where the Unix CCS
command set are located.
The default location is /usr/ccs/bin
An override for specifying where the
Unix /usr/bin commands are located. You usually do not need
to set this variable: the default location is /usr/bin)
The default root location for many of the ALT path locations
of the following ALT variables.
The default value is
"/java" on Solaris and Linux,
"J:" on Windows.
These are useful in managing builds on multiple platforms.
The default network location for all of the import JDK images
for all platforms.
is not set, this directory will be used and should contain
the following directories:
solaris-sparc,
solaris-i586,
solaris-sparcv9,
solaris-amd64,
linux-i586,
linux-amd64,
windows-i586,
windows-amd64.
Where each of these directories contain the import JDK image
for that platform.
These are useful in managing builds on multiple platforms.
The default network location for all of the binary plug images
for all platforms.
is not set, this directory will be used and should contain
the following directories:
solaris-sparc,
solaris-i586,
solaris-sparcv9,
solaris-amd64,
linux-i586,
linux-amd64,
windows-i586,
windows-amd64.
Where each of these directories contain the binary plugs image
for that platform.
Windows specific:
The location of the Microsoft Visual Studio .NET 2003
tools 'bin' directory.
The default is usually derived from
The location of the
The default will be to try and use the DirectX environment
variable DXSDK_DIR,
failing that, look in C:/DXSDK.
The location of the
i586 only:
The location of the
A build can fail for any number of reasons.
Most failures
are a result of trying to build in an environment in which all the
pre-build requirements have not been met.
The first step in
troubleshooting a build failure is to recheck that you have satisfied
all the pre-build requirements for your platform.
Look for the check list of the platform you are building on in the
You can validate your build environment by using the sanity
Any errors listed
will stop the build from starting, and any warnings may result in
a flawed product build.
We strongly encourage you to evaluate every
sanity check warning and fix it if required, before you proceed
further with your build.
Some of the more common problems with builds are briefly described
below, with suggestions for remedies.
Slow Builds:
If your build machine seems to be overloaded from too many
simultaneous C++ compiles, try setting the HOTSPOT_BUILD_JOBS
variable to 1 (if you're using a multiple CPU
machine, setting it to more than the the number of CPUs is probably
not a good idea).
Creating the javadocs can be very slow, if you are running
javadoc, consider skipping that step.
Faster hardware and more RAM always helps too.
The VM build tends to be CPU intensive (many C++ compiles),
and the rest of the JDK will often be disk intensive.
Faster compiles are possible using a tool called
File time issues:
If you see warnings that refer to file time stamps, e.g.
Warning message: File `xxx' has modification time in
the future.
Warning message:
Clock skew detected. Your build may
be incomplete.
These warnings can occur when the clock on the build machine is out of
sync with the timestamps on the source files. Other errors, apparently
unrelated but in fact caused by the clock skew, can occur along with
the clock skew warnings. These secondary errors may tend to obscure the
fact that the true root cause of the problem is an out-of-sync clock.
For example, an out-of-sync clock has been known to cause an old
version of javac to be used to compile some files, resulting in errors
when the pre-1.4 compiler ran across the new assert keyword
in the 1.4 source code.
If you see these warnings, reset the clock on the build
machine, run "gmake clobber" or delete the directory
containing the build output, and restart the build from the beginning.
Error message: Trouble writing out table to disk
Increase the amount of swap space on your build machine.
Error Message: libstdc++ not found:
This is caused by a missing libstdc++.a library.
This is installed as part of a specific package
(e.g. libstdc++.so.devel.386).
By default some 64bit Linux versions (e.g. Fedora)
only install the 64bit version of the libstdc++ package.
Various parts of the JDK build require a static
link of the C++ runtime libraries to allow for maximum
portability of the built images.
Error Message: cannot restore segment prot after reloc
This is probably an issue with SELinux (See
Parts of the VM is built without the -fPIC for
performance reasons.
To completely disable SELinux:
# system-config-securitylevel
In the window that appears, select the SELinux tab
Disable SELinux
Alternatively, instead of completely disabling it you could
disable just this one check.
Select System->Administration->SELinux Management
In the SELinux Management Tool which appears,
select "Boolean" from the menu on the left
Expand the "Memory Protection" group
Check the first item, labeled
"Allow all unconfined executables to use libraries requiring text relocation ..."
A build can fail for any number of reasons.
Most failures
are a result of trying to build in an environment in which all the
pre-build requirements have not been met.
The first step in
troubleshooting a build failure is to recheck that you have satisfied
all the pre-build requirements for your platform.
Look for the check list of the platform you are building on in the
You can validate your build environment by using the sanity
Any errors listed
will stop the build from starting, and any warnings may result in
a flawed product build.
We strongly encourage you to evaluate every
sanity check warning and fix it if required, before you proceed
further with your build.
Some of the more common problems with builds are briefly described
below, with suggestions for remedies.
Slow Builds:
If your build machine seems to be overloaded from too many
simultaneous C++ compiles, try setting the HOTSPOT_BUILD_JOBS
variable to 1 (if you're using a multiple CPU
machine, setting it to more than the the number of CPUs is probably
not a good idea).
Creating the javadocs can be very slow, if you are running
javadoc, consider skipping that step.
Faster hardware and more RAM always helps too.
The VM build tends to be CPU intensive (many C++ compiles),
and the rest of the JDK will often be disk intensive.
Faster compiles are possible using a tool called
File time issues:
If you see warnings that refer to file time stamps, e.g.
Warning message: File `xxx' has modification time in
the future.
Warning message:
Clock skew detected. Your build may
be incomplete.
These warnings can occur when the clock on the build machine is out of
sync with the timestamps on the source files. Other errors, apparently
unrelated but in fact caused by the clock skew, can occur along with
the clock skew warnings. These secondary errors may tend to obscure the
fact that the true root cause of the problem is an out-of-sync clock.
For example, an out-of-sync clock has been known to cause an old
version of javac to be used to compile some files, resulting in errors
when the pre-1.4 compiler ran across the new assert keyword
in the 1.4 source code.
If you see these warnings, reset the clock on the build
machine, run "gmake clobber" or delete the directory
containing the build output, and restart the build from the beginning.
Error message: Trouble writing out table to disk
Increase the amount of swap space on your build machine.
Error Message: libstdc++ not found:
This is caused by a missing libstdc++.a library.
This is installed as part of a specific package
(e.g. libstdc++.so.devel.386).
By default some 64bit Linux versions (e.g. Fedora)
only install the 64bit version of the libstdc++ package.
Various parts of the JDK build require a static
link of the C++ runtime libraries to allow for maximum
portability of the built images.
Error Message: cannot restore segment prot after reloc
This is probably an issue with SELinux (See
Parts of the VM is built without the -fPIC for
performance reasons.
To completely disable SELinux:
# system-config-securitylevel
In the window that appears, select the SELinux tab
Disable SELinux
Alternatively, instead of completely disabling it you could
disable just this one check.
Select System->Administration->SELinux Management
In the SELinux Management Tool which appears,
select "Boolean" from the menu on the left
Expand the "Memory Protection" group
Check the first item, labeled
"Allow all unconfined executables to use libraries requiring text relocation ..."
Windows Error Message: *** fatal error - couldn't allocate heap, ...
The CYGWIN software can conflict with other non-CYGWIN
software. See the CYGWIN FAQ section on
Windows Error Message: *** multiple target patterns.
The CYGWIN make version 3.81 may not like the Windows C:/
style paths, it may not like the ':' character in the path
when used in a makefile target definition.
diff -r 2d100b69e73f -r f6da81d808dc make/sun/cmm/Makefile
--- a/make/sun/cmm/Makefile Fri Jan 30 16:59:18
+++ b/make/sun/cmm/Makefile Fri Jan 30 17:00:25
@@ -41,12 +41,8 @@
ICCPROFILE_DEST_DIR = $(LIBDIR)/cmm
iccprofiles: $(ICCPROFILE_DEST_DIR)/sRGB.pf $(ICCPROFILE_DEST_DIR)/GRAY.pf \
$(ICCPROFILE_DEST_DIR)/CIEXYZ.pf
-ifndef OPENJDK
-iccprofiles:
$(ICCPROFILE_DEST_DIR)/PYCC.pf \
$(ICCPROFILE_DEST_DIR)/LINEAR_RGB.pf
$(ICCPROFILE_DEST_DIR)/CIEXYZ.pf $(ICCPROFILE_DEST_DIR)/PYCC.pf \
$(ICCPROFILE_DEST_DIR)/LINEAR_RGB.pf
$(ICCPROFILE_DEST_DIR)/sRGB.pf: $(ICCPROFILE_SRC_DIR)/sRGB.pf
$(RM) $(ICCPROFILE_DEST_DIR)/sRGB.pf
diff -r 2d100b69e73f -r f6da81d808dc make/sun/javazic/tzdata/VERSION
--- a/make/sun/javazic/tzdata/VERSION Fri Jan 30 16:59:18
+++ b/make/sun/javazic/tzdata/VERSION Fri Jan 30 17:00:25
@@ -21,4 +21,4 @@
# CA 95054 USA or visit www.sun.com if you need additional information or
# have any questions.
-tzdata2008b
+tzdata2008c
diff -r 2d100b69e73f -r f6da81d808dc make/sun/javazic/tzdata/africa
--- a/make/sun/javazic/tzdata/africa Fri Jan 30 16:59:18
+++ b/make/sun/javazic/tzdata/africa Fri Jan 30 17:00:25
@@ -22,7 +22,7 @@
# have any questions.
-# @(#)africa 8.10
+# @(#)africa 8.11
# This data is by no if you think you know better,
@@ -424,6 +424,77 @@
# See the `europe' file for Spanish Morocco (Africa/Ceuta).
+# From Alex Krivenyshev ():
+# Here is an article that Morocco plan to introduce Daylight Saving Time between
+# 1 June, 2008 and 27 September, 2008.
+# "... Morocco is to save energy by adjusting its clock during summer so it will
+# be one hour ahead of GMT between 1 June and 27 September, according to
+# Communication Minister and Gov ernment Spokesman, Khalid Naciri...."
+# From Alex Krivenyshev ():
+# The Morocco time change can be confirmed on Morocco web site Maghreb Arabe Presse:
+# Morocco shifts to daylight time on June 1st through September 27, Govt.
+# spokesman.
+# From Patrice Scattolin ():
+# According to this article:
+# (and republished here:
+# the changes occurs at midnight:
+# saturday night may 31st at midnight (which in french is to be
+# intrepreted as the night between saturday and sunday)
+# sunday night the 28th
at midnight
+# Seeing that the 28th is monday, I am guessing that she intends to say
+# the midnight of the 28th which is the midnight between sunday and
+# monday, which jives with other sources that say that it's inclusive
+# june1st to sept 27th.
+# The decision was taken by decree *2-08-224 *but I can't find the decree
+# published on the web.
+# It's also confirmed here:
+# on a government portal as being
between june 1st and sept 27th (not yet
+# posted in english).
+# The following google query will generate many relevant hits:
+# From Alex Krivenyshev ():
+# Is Western Sahara (part which administrated by Morocco) going to follow
+# Morocco DST changes?
Any information?
What about other part of
+# Western Sahara - under administration of POLISARIO Front (also named
+# SADR Saharawi Arab Democratic Republic)?
+# From Arthur David Olson ():
+# XXX--guess that it is only M guess only 2008 for now.
# RULE NAME FROM TO TYPE IN ON AT SAVE LETTER/S
Rule Morocco 1939 only - Sep 12
0:00 1:00 S
Rule Morocco 1939 only - Nov 19
@@ -440,11 +511,13 @@
Rule Morocco 1977 only - Sep 28
Rule Morocco 1978 only - Jun
0:00 1:00 S
Rule Morocco 1978 only - Aug
+Rule Morocco 2008 only - Jun
0:00 1:00 S
+Rule Morocco 2008 only - Sep 28
# Zone NAME
GMTOFF RULES FORMAT [UNTIL]
Zone Africa/Casablanca -0:30:20 - LMT 1913 Oct 26
0:00 Morocco WE%sT 1984 Mar 16
1:00 - CET 1986
0:00 - WET
0:00 Morocco WE%sT
# Western Sahara
Zone Africa/El_Aaiun -0:52:48 - LMT 1934 Jan
-1:00 - WAT 1976 Apr 14
diff -r 2d100b69e73f -r f6da81d808dc make/sun/javazic/tzdata/asia
--- a/make/sun/javazic/tzdata/asia Fri Jan 30 16:59:18
+++ b/make/sun/javazic/tzdata/asia Fri Jan 30 17:00:25
@@ -22,7 +22,7 @@
# have any questions.
-# @(#)asia 8.18
+# @(#)asia 8.20
# This data is by no if you think you know better,
@@ -00,42 @@
# They decided not to adopt daylight-saving time....
# http://www.mongolnews.mn/index.php?module=unuudur&sec=view&id=15742
+# From Deborah Goldsmith ():
+# We received a bug report claiming that the tz database UTC offset for
+# Asia/Choibalsan (GMT+09:00) is incorrect, and that it should be GMT
+# +08:00 instead. Different sources appear to disagree with the tz
+# database on this, e.g.:
+# both say GMT+08:00.
+# From Steffen Thorsen ():
+# eznis airways, which operates several domestic flights, has a flight
+# schedule here:
+# =2 0:01 1:00 S
Rule Pakistan 2002 only - Oct Sun>=2 0:01 0 -
+Rule Pakistan 2008 only - Jun 1 0:00 1:00 S
+Rule Pakistan 2008 only - Sep 1 0:00 0 -
# Zone NAME
GMTOFF RULES FORMAT [UNTIL]
Zone Asia/Karachi 4:28:12 - LMT 1907
5:30 - IST 1942 Sep
diff -r 2d100b69e73f -r f6da81d808dc src/share/classes/java/beans/MetaData.java
--- a/src/share/classes/java/beans/MetaData.java Fri Jan 30 16:59:18
+++ b/src/share/classes/java/beans/MetaData.java Fri Jan 30 17:00:25
@@ -20,7 @@
registerConstructor("javax.swing.plaf.BorderUIResource$EmptyBorderUIResource", new String[]{"borderInsets"});
registerConstructor("javax.swing.border.EtchedBorder", new String[]{"etchType", "highlightColor", "shadowColor"});
registerConstructor("javax.swing.plaf.BorderUIResource$EtchedBorderUIResource", new String[]{"etchType", "highlightColor", "shadowColor"});
registerConstructor("javax.swing.border.LineBorder", new String[]{"lineColor", "thickness"});
registerConstructor("javax.swing.border.LineBorder", new String[]{"lineColor", "thickness", "roundedCorners"});
registerConstructor("javax.swing.plaf.BorderUIResource$LineBorderUIResource", new String[]{"lineColor", "thickness"});
registerConstructor("javax.swing.border.SoftBevelBorder", new String[]{"bevelType", "highlightOuterColor", "highlightInnerColor", "shadowOuterColor", "shadowInnerColor"});
// registerConstructorWithBadEqual("javax.swing.plaf.BorderUIResource$SoftBevelBorderUIResource", new String[]{"bevelType", "highlightOuter", "highlightInner", "shadowOuter", "shadowInner"});
diff -r 2d100b69e73f -r f6da81d808dc src/share/}