diff --git a/Makefile b/Makefile index d42650e58ce8af5b4b467ddd421c7e90e293af40..7c5b2db01c0db3a4bf8e813f646912145ef52691 100644 --- a/Makefile +++ b/Makefile @@ -156,12 +156,6 @@ ifeq ($(BUILD_DEPLOY), true) clobber:: deploy-clobber endif -ifeq ($(BUILD_JDK), true) - ifeq ($(BUNDLE_RULES_AVAILABLE), true) - generic_build_repo_series:: openjdk-binary-plugs-bundles - endif -endif - # The debug build, fastdebug or debug. Needs special handling. # Note that debug builds do NOT do INSTALL steps, but must be done # after the product build and before the INSTALL step of the product build. @@ -301,7 +295,6 @@ ifneq ($(SKIP_OPENJDK_BUILD), true) ifeq ($(BUILD_JDK), true) ifeq ($(BUNDLE_RULES_AVAILABLE), true) -OPENJDK_PLUGS=$(ABS_OUTPUTDIR)/$(OPENJDK_BINARY_PLUGS_INAME) OPENJDK_OUTPUTDIR=$(ABS_OUTPUTDIR)/open-output OPENJDK_BUILD_NAME \ = openjdk-$(JDK_MINOR_VERSION)-$(BUILD_NUMBER)-$(PLATFORM)-$(ARCH)-$(BUNDLE_DATE) @@ -330,7 +323,6 @@ openjdk_build: GENERATE_DOCS=false \ ALT_JDK_DEVTOOLS_DIR=$(JDK_DEVTOOLS_DIR) \ ALT_OUTPUTDIR=$(OPENJDK_OUTPUTDIR) \ - ALT_BINARY_PLUGS_PATH=$(OPENJDK_PLUGS) \ ALT_BOOTDIR=$(OPENJDK_BOOTDIR) \ ALT_JDK_IMPORT_PATH=$(OPENJDK_IMPORTJDK) \ product_build ) @@ -456,7 +448,6 @@ CACERTS_FILE.desc = Location of certificates file DEVTOOLS_PATH.desc = Directory containing zip and gnumake CUPS_HEADERS_PATH.desc = Include directory location for CUPS header files DXSDK_PATH.desc = Root directory of DirectX SDK -MSDEVTOOLS_PATH.desc = Root directory of VC++ tools (e.g. rc.exe) MSVCRT_DLL_PATH.desc = Directory containing mscvrt.dll # Make variables to print out (description and value) @@ -487,12 +478,10 @@ ifeq ($(PLATFORM), windows) VARIABLE_PRINTVAL_LIST += \ DXSDK_PATH \ - MSDEVTOOLS_PATH \ MSVCRT_DLL_PATH VARIABLE_CHECKDIR_LIST += \ DXSDK_PATH \ - MSDEVTOOLS_PATH \ MSVCRT_DLL_PATH endif @@ -548,7 +537,7 @@ examples_help: " ################################################################ -# Source and binary plug bundling +# Source bundling ################################################################ ifeq ($(BUNDLE_RULES_AVAILABLE), true) include $(BUNDLE_RULES) diff --git a/README b/README index eef68df24a7e265498e5144bb21e9bc720bbf7a4..722131d683f02b71c79b84c1444c399b5c0d00ec 100644 --- a/README +++ b/README @@ -1,28 +1,38 @@ README: - This file should be located at the top of the OpenJDK Mercurial repository - forest. This top or enclosing repository will include a "make" directory, - and a Makefile at the very top of the repository. - It should also include the 6 repositories: "jdk", "hotspot", "langtools", - "corba", "jaxws" and "jaxp". + This file should be located at the top of the OpenJDK Mercurial root + repository. This root repository will include a "make" directory, + and a Makefile for building the entire OpenJDK. + A full OpenJDK repository set (forest) should also include the following + 6 nested repositories: + "jdk", "hotspot", "langtools", "corba", "jaxws" and "jaxp". + There are also several source downloads for the jax* repositories that + will be needed. + + This one root repository can be obtained with something like: + hg clone http://hg.openjdk.java.net/jdk7/jdk7 openjdk7 + To make sure you have all the nested repositories, you can run: + cd openjdk7 && sh ./get_source.sh + (This is identical to using the Mercurial Forest Extension command + 'hg fclone http://hg.openjdk.java.net/jdk7/jdk7 openjdk7'). + People unfamiliar with Mercurial should read the first few chapters of + the Mercurial book: http://hgbook.red-bean.com/read/ See http://openjdk.java.net/ for more information about the OpenJDK. Simple Build Instructions: + + 0. Get the necessary system software/packages installed on your system, see + http://hg.openjdk.java.net/jdk7/build/raw-file/tip/README-builds.html - 1. Download and install a JDK 6 from + 1. If you don't have a jdk6 installed, download and install a JDK 6 from http://java.sun.com/javase/downloads/index.jsp - Set the environment variable ALT_BOOTDIR to the location of this JDK 6. + Set the environment variable ALT_BOOTDIR to the location of JDK 6. - 2. Download and install the Binary Plugs for the most recent JDK7 from - http://download.java.net/openjdk/jdk7/ - Set the environment variable ALT_BINARY_PLUGS_PATH to the location of - these binary plugs. - - 3. Check the sanity of doing a build with the current machine: + 2. Check the sanity of doing a build with your current system: gnumake sanity See README-builds.html if you run into problems. - 4. Do a complete build of the jdk: + 3. Do a complete build of the OpenJDK: gnumake all The resulting JDK image should be found in build/*/j2sdk-image diff --git a/README-builds.html b/README-builds.html index 1c2504c4dc5fcde19167ee8f8df5bee506773e6e..e48aaff3612f317e95f66a1f75002450d6b50ff4 100644 --- a/README-builds.html +++ b/README-builds.html @@ -24,12 +24,12 @@

Introduction

- This README file contains build instructions for the - OpenJDK. - Building the source code for the - OpenJDK - requires - a certain degree of technical expertise. + This README file contains build instructions for the + OpenJDK. + Building the source code for the + OpenJDK + requires + a certain degree of technical expertise.

@@ -37,18 +37,23 @@
+ + +
+

Use of Mercurial

+
+ The OpenJDK sources are maintained with the revision control system + Mercurial. + If you are new to Mercurial, please see the + Beginner Guides + or refer to the Mercurial Book. + The first few chapters of the book provide an excellent overview of + Mercurial, what it is and how it works. +
+ For using Mercurial with the OpenJDK refer to the + + Developer Guide: Installing and Configuring Mercurial + section for more information. + The Forest Extension is not part of the Mercurial install, + and is optional, + but can be obtained with the following commands: +
+ + hg clone https://bitbucket.org/pmezard/hgforest-crew/overview/ YourHgForest + +
+ Once you have the file forest.py, you need to add these + lines to your ${HOME}/.hgrc file: +
+ + [extensions] +
forest = YourHgForest/forest.py + +
+ + +

Getting the Source

+
+ To get the entire set of OpenJDK Mercurial repositories + using the Forest Extension: +
+ + hg fclone http://openjdk.java.net/jdk7/jdk7 YourOpenJDK + +
+ To get the entire set of OpenJDK Mercurial repositories + without using the Forest Extension: +
+ + hg clone http://openjdk.java.net/jdk7/jdk7 YourOpenJDK +
cd YourOpenJDK +
sh ./get_source.sh + +
+ Once you have all the repositories, the + script make/scripts/hgforest.sh + can be used to repeat the same hg + command on every repository in the forest, e.g. +
+ + cd YourOpenJDK +
sh ./make/scripts/hgforest.sh pull -u + +
+ You may find this script make/scripts/hgforest.sh faster + than the hg forest commands provided by the + Forest Extension. +
+ +
+

Minimum Build Environments

@@ -116,8 +191,8 @@ 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 - OpenJDK: + The minimum OS and C/C++ compiler versions needed for building the + OpenJDK:

@@ -146,7 +221,7 @@ @@ -156,7 +231,7 @@ @@ -166,7 +241,7 @@ @@ -176,7 +251,7 @@ @@ -195,14 +270,14 @@
Solaris 10u2 + patches
See - SunSolve for patch downloads. + SunSolve for patch downloads. 		Sun Studio 12 Update 1 + patches JDK 6u14 FCS Solaris 10u2 + patches
See - SunSolve for patch downloads. + SunSolve for patch downloads. 		Sun Studio 12 Update 1 + patches JDK 6u14 FCS Solaris 10u2 + patches
See - SunSolve for patch downloads. + SunSolve for patch downloads. 		Sun Studio 12 Update 1 + patches JDK 6u14 FCS Solaris 10u2 + patches
See - SunSolve for patch downloads. + SunSolve for patch downloads. 		Sun Studio 12 Update 1 + patches JDK 6u14 FCS
-

+

These same sources do indeed build on many more systems than the above older generation systems, again the above is just a minimum. -

+

Compilation problems with newer or different C/C++ compilers is a common problem. Similarly, compilation problems related to changes to the - /usr/include or system header files is also a + /usr/include or system header files is also a common problem with newer or unreleased OS versions. Please report these types of problems as bugs so that they can be dealt with accordingly. @@ -217,57 +292,57 @@

Fedora

-

Fedora 9

-

-

- After installing Fedora 9 +

Fedora 9

+

+

+ After installing Fedora 9 you need to install several build dependencies. The simplest way to do it is to execute the following commands as user - root: -

- yum-builddep java-openjdk -

- yum install gcc gcc-c++ -

+ root: +

+ yum-builddep java-openjdk +

+ yum install gcc gcc-c++ +

In addition, it's necessary to set a few environment variables for the build: -

- export LANG=C ALT_BOOTDIR=/usr/lib/jvm/java-openjdk +

+ export LANG=C ALT_BOOTDIR=/usr/lib/jvm/java-openjdk

-

Fedora 10

-

-

- After installing Fedora 10 +

Fedora 10

+

+

+ After installing Fedora 10 you need to install several build dependencies. The simplest way to do it is to execute the following commands as user - root: -

- yum-builddep java-1.6.0-openjdk -

- yum install gcc gcc-c++ -

+ root: +

+ yum-builddep java-1.6.0-openjdk +

+ yum install gcc gcc-c++ +

In addition, it's necessary to set a few environment variables for the build: -

- export LANG=C ALT_BOOTDIR=/usr/lib/jvm/java-openjdk +

+ export LANG=C ALT_BOOTDIR=/usr/lib/jvm/java-openjdk

-

Fedora 11

-

-

- After installing Fedora 11 +

Fedora 11

+

+

+ After installing Fedora 11 you need to install several build dependencies. The simplest way to do it is to execute the following commands as user - root: -

- yum-builddep java-1.6.0-openjdk -

- yum install gcc gcc-c++ -

+ root: +

+ yum-builddep java-1.6.0-openjdk +

+ yum install gcc gcc-c++ +

In addition, it's necessary to set a few environment variables for the build: -

- export LANG=C ALT_BOOTDIR=/usr/lib/jvm/java-openjdk -

+

+ export LANG=C ALT_BOOTDIR=/usr/lib/jvm/java-openjdk +

CentOS 5.2

@@ -285,7 +360,7 @@

- Plus the following packages: + Plus the following packages:

- The freetype 2.3 packages don't seem to be available, - but the freetype 2.3 sources can be downloaded, built, - and installed easily enough from - - the freetype site. - Build and install with something like: + The freetype 2.3 packages don't seem to be available, + but the freetype 2.3 sources can be downloaded, built, + and installed easily enough from + + the freetype site. + Build and install with something like:

./configure && make && sudo -u root make install

- Mercurial packages could not be found easily, but a Google - search should find ones, and they usually include Python if - it's needed. + Mercurial packages could not be found easily, but a Google + search should find ones, and they usually include Python if + it's needed.

Debian

Debian 5.0 (Lenny)

-

+
After installing Debian 5 you need to install several build dependencies. The simplest way to install the build dependencies is to execute the following commands as user root: -

- aptitude build-dep openjdk-6 -

- aptitude install openjdk-6-jdk libmotif-dev -

+

+ aptitude build-dep openjdk-6 +

+ aptitude install openjdk-6-jdk libmotif-dev +

In addition, it's necessary to set a few environment variables for the build: -

- export LANG=C ALT_BOOTDIR=/usr/lib/jvm/java-6-openjdk -

+

+ export LANG=C ALT_BOOTDIR=/usr/lib/jvm/java-6-openjdk +

-

Ubuntu

+

Ubuntu

Ubuntu 8.04

-

+
After installing Ubuntu 8.04 you need to install several build dependencies. -

+

First, you need to enable the universe repository in the Software Sources application and reload the repository information. The Software Sources application is available under the System/Administration menu. -

+

The simplest way to install the build dependencies is to execute the following commands: -

- sudo aptitude build-dep openjdk-6 -

- sudo aptitude install openjdk-6-jdk -

+

+ sudo aptitude build-dep openjdk-6 +

+ sudo aptitude install openjdk-6-jdk +

In addition, it's necessary to set a few environment variables for the build: -

- export LANG=C ALT_BOOTDIR=/usr/lib/jvm/java-6-openjdk -

-

Ubuntu 8.10

+

+ export LANG=C ALT_BOOTDIR=/usr/lib/jvm/java-6-openjdk +

+

Ubuntu 8.10

-

+
After installing Ubuntu 8.10 you need to install several build dependencies. The simplest way to do it is to execute the following commands: -

- sudo aptitude build-dep openjdk-6 -

- sudo aptitude install openjdk-6-jdk -

+

+ sudo aptitude build-dep openjdk-6 +

+ sudo aptitude install openjdk-6-jdk +

In addition, it's necessary to set a few environment variables for the build: -

- export LANG=C ALT_BOOTDIR=/usr/lib/jvm/java-6-openjdk -

-

Ubuntu 9.04

+

+ export LANG=C ALT_BOOTDIR=/usr/lib/jvm/java-6-openjdk +

+

Ubuntu 9.04

-

+
After installing Ubuntu 9.04 you need to install several build dependencies. The simplest way to do it is to execute the following commands: -

- sudo aptitude build-dep openjdk-6 -

- sudo aptitude install openjdk-6-jdk -

+

+ sudo aptitude build-dep openjdk-6 +

+ sudo aptitude install openjdk-6-jdk +

In addition, it's necessary to set a few environment variables for the build: -

- export LANG=C ALT_BOOTDIR=/usr/lib/jvm/java-6-openjdk -

+

+ export LANG=C ALT_BOOTDIR=/usr/lib/jvm/java-6-openjdk +

OpenSUSE

OpenSUSE 11.1

-

+
After installing OpenSUSE 11.1 you need to install several build dependencies. The simplest way to install the build dependencies is to execute the following commands: -

- sudo zypper source-install -d java-1_6_0-openjdk -

- sudo zypper install make -

+

+ sudo zypper source-install -d java-1_6_0-openjdk +

+ sudo zypper install make +

In addition, it is necessary to set a few environment variables for the build: -

- export LANG=C ALT_BOOTDIR=/usr/lib/jvm/java-1.6.0-openjdk -

+

+ export LANG=C ALT_BOOTDIR=/usr/lib/jvm/java-1.6.0-openjdk +

Finally, you need to unset the JAVA_HOME environment variable: -

- export -n JAVA_HOME -

-
+

+ export -n JAVA_HOME +

+

Mandriva

Mandriva Linux One 2009 Spring

-

+
After installing Mandriva Linux One 2009 Spring you need to install several build dependencies. The simplest way to install the build dependencies is to execute the following commands as user root: -

- urpmi java-1.6.0-openjdk-devel ant make gcc gcc-c++ freetype-devel zip unzip libcups2-devel libxrender1-devel libalsa2-devel libstc++-static-devel libxtst6-devel libxi-devel +

+ urpmi java-1.6.0-openjdk-devel ant make gcc gcc-c++ freetype-devel zip unzip libcups2-devel libxrender1-devel libalsa2-devel libstc++-static-devel libxtst6-devel libxi-devel

In addition, it is necessary to set a few environment variables for the build: -

- export LANG=C ALT_BOOTDIR=/usr/lib/jvm/java-1.6.0-openjdk -

+

+ export LANG=C ALT_BOOTDIR=/usr/lib/jvm/java-1.6.0-openjdk +

OpenSolaris

OpenSolaris 2009.06

-

+
After installing OpenSolaris 2009.06 you need to install several build dependencies. The simplest way to install the build dependencies is to execute the following commands: -

- pfexec pkg install SUNWgmake SUNWj6dev SUNWant sunstudioexpress SUNWcups SUNWzip SUNWunzip SUNWxwhl SUNWxorg-headers SUNWaudh SUNWfreetype2 +

+ pfexec pkg install SUNWgmake SUNWj6dev SUNWant sunstudioexpress SUNWcups SUNWzip SUNWunzip SUNWxwhl SUNWxorg-headers SUNWaudh SUNWfreetype2

In addition, it is necessary to set a few environment variables for the build: -

- export LANG=C ALT_COMPILER_PATH=/opt/SunStudioExpress/bin/ ALT_CUPS_HEADERS_PATH=/usr/include/ -

+

+ export LANG=C ALT_COMPILER_PATH=/opt/SunStudioExpress/bin/ ALT_CUPS_HEADERS_PATH=/usr/include/ +

Finally, you need to make sure that the build process can find the Sun Studio compilers: -

- export PATH=$PATH:/opt/SunStudioExpress/bin/ -

+

+ export PATH=$PATH:/opt/SunStudioExpress/bin/ +

Source Directory Structure

- The source code for the OpenJDK is delivered in a set of - directories: - hotspot, - langtools, - corba, - jaxws, - jaxp, - and - jdk. - 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. + The source code for the OpenJDK is delivered in a set of + directories: + hotspot, + langtools, + corba, + jaxws, + jaxp, + and + jdk. + 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.

@@ -495,10 +570,10 @@ 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: + 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: 


                 bash
@@ -507,12 +582,12 @@

- 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. + 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.

@@ -559,14 +634,14 @@ version that has this problem fixed. The older 3.80 version of make.exe can be downloaded with this - link. + link. Use of this older 3.80 make.exe may require that you install the libintl2.dll library or libintl2 cygwin package which is no longer installed by default by the cygwin installer.
Also see the - mozilla developer center + mozilla developer center on this topic.
It's hoped that when make 3.82 starts shipping in a future cygwin @@ -574,19 +649,19 @@ In addition to the above 3.80 make.exe you can download this - www.cmake.org make.exe which will not have a libintl2.dll + www.cmake.org make.exe which will not have a libintl2.dll dependency.

- Information on GNU make, and access to ftp download sites, are - available on the - - GNU make web site - . - The latest source to GNU make is available at - - ftp.gnu.org/pub/gnu/make/. + Information on GNU make, and access to ftp download sites, are + available on the + + GNU make web site + . + The latest source to GNU make is available at + + ftp.gnu.org/pub/gnu/make/.

@@ -597,27 +672,27 @@ is a Pentium class processor or better, at least 256 MB of RAM, and approximately 1.5 GB of free disk space.

- X64 only: - 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. + X64 only: + 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 - /bin and - /usr/bin - of a standard installation of the Linux operating environment. - You should ensure that these directories are in your - PATH. + The build will use the tools contained in + /bin and + /usr/bin + of a standard installation of the Linux operating environment. + You should ensure that these directories are in your + PATH.

- 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 - OpenJDK. + 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 + OpenJDK.

Basic Linux Check List

@@ -628,18 +703,13 @@ Bootstrap JDK, set ALT_BOOTDIR. -
  • - Install the - Binary Plugs, set - ALT_BINARY_PLUGS_PATH. -
  • Optional Import JDK, set ALT_JDK_IMPORT_PATH.
  • Install or upgrade the FreeType development - package. + package.
  • Install @@ -660,23 +730,23 @@ Approximately 1.4 GB of free disk space is needed for a 32-bit build.

    - If you are building the 64-bit version, you should - run the command "isainfo -v" to verify that you have a - 64-bit installation, it should say sparcv9 or - amd64. - An additional 7 GB of free disk space is needed - for a 64-bit build. + If you are building the 64-bit version, you should + run the command "isainfo -v" to verify that you have a + 64-bit installation, it should say sparcv9 or + amd64. + 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. + 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 - - SunSolve JDK Solaris patches download page. - You should ensure that the latest patch cluster for - your version of the Solaris operating environment has also - been installed. + Solaris patches specific to the JDK can be downloaded from the + + SunSolve JDK Solaris patches download page. + You should ensure that the latest patch cluster for + your version of the Solaris operating environment has also + been installed.

    Basic Solaris Check List

    @@ -687,11 +757,6 @@ Bootstrap JDK, set ALT_BOOTDIR.
    • -
  • - Install the - Binary Plugs, set - ALT_BINARY_PLUGS_PATH. -
  • Optional Import JDK, set ALT_JDK_IMPORT_PATH. @@ -731,10 +796,10 @@ because FAT32 doesn't support case-sensitivity in file names.

    - X64 only: - 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. + X64 only: + 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.

    Windows Paths

    @@ -753,18 +818,18 @@ (called 'mixed'), e.g. cygpath -s -m "path".

    - The makefiles will try to translate any pathnames supplied - to it into the C:/ style automatically. + 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 PATH. 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. + Note that use of CYGWIN creates a unique problem with regards to + setting PATH. 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.

    Basic Windows Check List

    @@ -779,11 +844,6 @@ Bootstrap JDK, set ALT_BOOTDIR.
    • -
  • - Install the - Binary Plugs, set - ALT_BINARY_PLUGS_PATH.. -
  • Optional Import JDK, set ALT_JDK_IMPORT_PATH. @@ -828,7 +888,7 @@ JDK 6, this is often called a bootstrap JDK. The JDK 6 binaries can be downloaded from Sun's JDK 6 download site. + target="_blank">JDK 6 download site. For build performance reasons is very important that this bootstrap JDK be made available on the local disk of the machine doing the build. @@ -841,44 +901,12 @@ in the PATH environment variable, although it's not required.

    - Solaris: - Some pre-installed JDK images may be available to you in the - directory /usr/jdk/instances. - If you don't set - ALT_BOOTDIR - the makefiles will look in that location for a JDK it can use. - - -

    Binary Plugs

    -
    - 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 - OpenJDK site and select - the - "Bundles(7)" - 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-7-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 - ALT_BINARY_PLUGS_PATH - to the root of this installation. + Solaris: + Some pre-installed JDK images may be available to you in the + directory /usr/jdk/instances. + If you don't set + ALT_BOOTDIR + the makefiles will look in that location for a JDK it can use.

    Optional Import JDK

    @@ -896,7 +924,7 @@ All OpenJDK builds require access to least Ant 1.6.5. The Ant tool is available from the - Ant download site. + Ant download site. You should always make sure ant is in your PATH, and on Windows you may also need to set ANT_HOME @@ -908,7 +936,7 @@

    Certificate Authority File (cacert)

    See - http://en.wikipedia.org/wiki/Certificate_Authority + http://en.wikipedia.org/wiki/Certificate_Authority for a better understanding of the Certificate Authority (CA). A certificates file named "cacerts" represents a system-wide keystore with CA certificates. @@ -942,121 +970,121 @@
    At a minimum, the - Sun Studio 12 Update 1 Compilers + Sun Studio 12 Update 1 Compilers (containing version 5.10 of the C and C++ compilers) is required, including specific patches. -

    +

    The Solaris SPARC patch list is: -

      -
    • - 118683-05: SunOS 5.10: Patch for profiling libraries and assembler -
      • -
    • - 119963-21: SunOS 5.10: Shared library patch for C++ -
      • -
    • - 120753-08: SunOS 5.10: Microtasking libraries (libmtsk) patch -
      • -
    • - 128228-09: Sun Studio 12 Update 1: Patch for Sun C++ Compiler -
      • -
    • - 141860-03: Sun Studio 12 Update 1: Patch for Compiler Common patch for Sun C C++ F77 F95 -
      • -
    • - 141861-05: Sun Studio 12 Update 1: Patch for Sun C Compiler -
      • -
    • - 142371-01: Sun Studio 12.1 Update 1: Patch for dbx -
      • -
    • - 143384-02: Sun Studio 12 Update 1: Patch for debuginfo handling -
      • -
    • - 143385-02: Sun Studio 12 Update 1: Patch for Compiler Common patch for Sun C C++ F77 F95 -
      • -
    • - 142369-01: Sun Studio 12.1: Patch for Performance Analyzer Tools -
      • +
        +
      • + 118683-05: SunOS 5.10: Patch for profiling libraries and assembler +
        • +
      • + 119963-21: SunOS 5.10: Shared library patch for C++ +
        • +
      • + 120753-08: SunOS 5.10: Microtasking libraries (libmtsk) patch +
        • +
      • + 128228-09: Sun Studio 12 Update 1: Patch for Sun C++ Compiler +
        • +
      • + 141860-03: Sun Studio 12 Update 1: Patch for Compiler Common patch for Sun C C++ F77 F95 +
        • +
      • + 141861-05: Sun Studio 12 Update 1: Patch for Sun C Compiler +
        • +
      • + 142371-01: Sun Studio 12.1 Update 1: Patch for dbx +
        • +
      • + 143384-02: Sun Studio 12 Update 1: Patch for debuginfo handling +
        • +
      • + 143385-02: Sun Studio 12 Update 1: Patch for Compiler Common patch for Sun C C++ F77 F95 +
        • +
      • + 142369-01: Sun Studio 12.1: Patch for Performance Analyzer Tools +

      - The Solaris X86 patch list is: + The Solaris X86 patch list is:

        -
      • - 119961-07: SunOS 5.10_x86, x64, Patch for profiling libraries and assembler -
        • -
      • - 119964-21: SunOS 5.10_x86: Shared library patch for C++_x86 -
        • -
      • - 120754-08: SunOS 5.10_x86: Microtasking libraries (libmtsk) patch -
        • -
      • - 141858-06: Sun Studio 12 Update 1_x86: Sun Compiler Common patch for x86 backend -
        • -
      • - 128229-09: Sun Studio 12 Update 1_x86: Patch for C++ Compiler -
        • -
      • - 142363-05: Sun Studio 12 Update 1_x86: Patch for C Compiler -
        • -
      • - 142368-01: Sun Studio 12.1_x86: Patch for Performance Analyzer Tools -
        • +
      • + 119961-07: SunOS 5.10_x86, x64, Patch for profiling libraries and assembler +
        • +
      • + 119964-21: SunOS 5.10_x86: Shared library patch for C++_x86 +
        • +
      • + 120754-08: SunOS 5.10_x86: Microtasking libraries (libmtsk) patch +
        • +
      • + 141858-06: Sun Studio 12 Update 1_x86: Sun Compiler Common patch for x86 backend +
        • +
      • + 128229-09: Sun Studio 12 Update 1_x86: Patch for C++ Compiler +
        • +
      • + 142363-05: Sun Studio 12 Update 1_x86: Patch for C Compiler +
        • +
      • + 142368-01: Sun Studio 12.1_x86: Patch for Performance Analyzer Tools +

      - Set - ALT_COMPILER_PATH - to point to the location of - the compiler binaries, and place this location in the PATH. + Set + ALT_COMPILER_PATH + to point to the location of + the compiler binaries, and place this location in the PATH.

      - The Oracle Solaris Studio Express compilers at: - - Oracle Solaris Studio Express Download site - are also an option, although these compilers have not - been extensively used yet. + The Oracle Solaris Studio Express compilers at: + + Oracle Solaris Studio Express Download site + are also an option, although these compilers have not + been extensively used yet.

    Windows i586: Microsoft Visual Studio 2010 Compilers
    -

    -BEGIN WARNING: At this time (Spring/Summer 2010) JDK 7 is starting a transition to -use the newest VS2010 Microsoft compilers. These build instructions are updated -to show where we are going. We have a QA process to go through before -official builds actually use VS2010. So for now, official builds are -still using VS2003. No other compilers are known to build the entire JDK, -including non-open portions. -So for now you should be able to build with either VS2003 or VS2010. -We do not guarantee that VS2008 will work, although there is sufficient -makefile support to make at least basic JDK builds plausible. -Visual Studio 2010 Express compilers are now able to build all the -open source repositories, but this is 32 bit only. To build 64 bit -Windows binaries use the the 7.1 Windows SDK.END WARNING. -

    - The 32-bit OpenJDK Windows build - requires - Microsoft Visual Studio C++ 2010 (VS2010) Professional - Edition or Express compiler. - The compiler and other tools are expected to reside - in the location defined by the variable - VS100COMNTOOLS which - is set by the Microsoft Visual Studio installer. +

    + BEGIN WARNING: At this time (Spring/Summer 2010) JDK 7 is starting a transition to + use the newest VS2010 Microsoft compilers. These build instructions are updated + to show where we are going. We have a QA process to go through before + official builds actually use VS2010. So for now, official builds are + still using VS2003. No other compilers are known to build the entire JDK, + including non-open portions. + So for now you should be able to build with either VS2003 or VS2010. + We do not guarantee that VS2008 will work, although there is sufficient + makefile support to make at least basic JDK builds plausible. + Visual Studio 2010 Express compilers are now able to build all the + open source repositories, but this is 32 bit only. To build 64 bit + Windows binaries use the the 7.1 Windows SDK.END WARNING. +

    + The 32-bit OpenJDK Windows build + requires + Microsoft Visual Studio C++ 2010 (VS2010) Professional + Edition or Express compiler. + The compiler and other tools are expected to reside + in the location defined by the variable + VS100COMNTOOLS which + is set by the Microsoft Visual Studio installer.

    - Once the compiler is installed, - it is recommended that you run VCVARS32.BAT - to set the compiler environment variables - INCLUDE, - LIB, and - PATH - prior to building the - OpenJDK. - The above environment variables MUST be set. - This compiler also contains the Windows SDK v 7.0a, - which is an update to the Windows 7 SDK. + Once the compiler is installed, + it is recommended that you run VCVARS32.BAT + to set the compiler environment variables + INCLUDE, + LIB, and + PATH + prior to building the + OpenJDK. + The above environment variables MUST be set. + This compiler also contains the Windows SDK v 7.0a, + which is an update to the Windows 7 SDK.

    - WARNING: Make sure you check out the - CYGWIN link.exe WARNING. - The path /usr/bin must be after the path to the - Visual Studio product. + WARNING: Make sure you check out the + CYGWIN link.exe WARNING. + The path /usr/bin must be after the path to the + Visual Studio product.

    Windows x64: Microsoft Visual Studio 2010 Professional Compiler
    @@ -1069,22 +1097,22 @@ Windows binaries use the the 7.1 Windows SDK.END WARNING. you have VS2010 Professional.
    Windows x64: Microsoft Windows 7.1 SDK 64 bit compilers. - For a free alternative for 64 bit builds, use the 7.1 SDK. - Microsoft say that to set up your paths for this run -
    +                For a free alternative for 64 bit builds, use the 7.1 SDK.
+                Microsoft say that to set up your paths for this run
+                
         c:\Program Files\Microsoft SDKs\Windows\v7.1\bin\setenv.cmd /x64.
-
    
-                   What was tested is just directly setting up LIB, INCLUDE,
-                   PATH and based on the installation directories using the
-                   DOS short name appropriate for the system, (you will
-                   need to set them for yours, not just blindly copy this) eg :
-
    +                
    
+                What was tested is just directly setting up LIB, INCLUDE,
+                PATH and based on the installation directories using the
+                DOS short name appropriate for the system, (you will
+                need to set them for yours, not just blindly copy this) eg :
+                
         set VSINSTALLDIR=c:\PROGRA~2\MICROS~1.0
     set WindowsSdkDir=c:\PROGRA~1\MICROS~1\Windows\v7.1
     set PATH=%VSINSTALLDIR%\vc\bin\amd64;%VSINSTALLDIR%\Common7\IDE;%WindowsSdkDir%\bin;%PATH%
     set INCLUDE=%VSINSTALLDIR%\vc\include;%WindowsSdkDir%\include
     set LIB=%VSINSTALLDIR%\vc\lib\amd64;%WindowsSdkDir%\lib\x64
-
    
+

    Zip and Unzip

    @@ -1110,41 +1138,41 @@ Windows binaries use the the 7.1 Windows SDK.END WARNING. Companion CD/DVD, these often will be installed into /opt/sfw/cups.

    - Linux: - 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. + Linux: + 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 - www.cups.org. - The variable - ALT_CUPS_HEADERS_PATH - can be used to override the default location of the - CUPS Header files. + The CUPS header files can always be downloaded from + www.cups.org. + The variable + ALT_CUPS_HEADERS_PATH + can be used to override the default location of the + CUPS Header files.

    XRender Extension Headers (Solaris & Linux)

    - Solaris: - XRender header files are required for building the - OpenJDK on Solaris. - The XRender header file is included with the other X11 header files - in the package SFWxwinc on new enough versions of - Solaris and will be installed in - /usr/X11/include/X11/extensions/Xrender.h + Solaris: + XRender header files are required for building the + OpenJDK on Solaris. + The XRender header file is included with the other X11 header files + in the package SFWxwinc on new enough versions of + Solaris and will be installed in + /usr/X11/include/X11/extensions/Xrender.h

    - Linux: - XRender header files are required for building the - OpenJDK on Linux. - The Linux header files are usually available from a "Xrender" - development package, it's recommended that you try and use - the package provided by the particular distribution of Linux that - you are using. -

    + Linux: + XRender header files are required for building the + OpenJDK on Linux. + The Linux header files are usually available from a "Xrender" + development package, it's recommended that you try and use + the package provided by the particular distribution of Linux that + you are using. +

    FreeType 2

    @@ -1155,31 +1183,31 @@ Windows binaries use the the 7.1 Windows SDK.END WARNING. 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 - FreeType website. + You can always download latest FreeType version from the + FreeType website.

    - Makefiles will try to pick FreeType from /usr/lib and /usr/include. - In case it is installed elsewhere you will need to set environment - variables - ALT_FREETYPE_LIB_PATH - and - ALT_FREETYPE_HEADERS_PATH - to refer to place where library and header files are installed. + Makefiles will try to pick FreeType from /usr/lib and /usr/include. + In case it is installed elsewhere you will need to set environment + variables + ALT_FREETYPE_LIB_PATH + and + ALT_FREETYPE_HEADERS_PATH + to refer to place where library and header files are installed.

    - Building the freetype 2 libraries from scratch is also possible, - however on Windows refer to the - - Windows FreeType DLL build instructions. + Building the freetype 2 libraries from scratch is also possible, + however on Windows refer to the + + Windows FreeType DLL build instructions.

    - Note that by default FreeType is built with byte code hinting - support disabled due to licensing restrictions. - In this case, text appearance and metrics are expected to - differ from Sun's official JDK build. - See - - the SourceForge FreeType2 Home Page - - for more information. + Note that by default FreeType is built with byte code hinting + support disabled due to licensing restrictions. + In this case, text appearance and metrics are expected to + differ from Sun's official JDK build. + See + + the SourceForge FreeType2 Home Page + + for more information.

    Advanced Linux Sound Architecture (ALSA) (Linux only)

    @@ -1195,25 +1223,25 @@ Windows binaries use the the 7.1 Windows SDK.END WARNING. 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: + 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 - - www.freshrpms.net. - 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. + 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 + + www.freshrpms.net. + 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
    @@ -1228,7 +1256,7 @@ Windows binaries use the the 7.1 Windows SDK.END WARNING.
    As a last resort you can go to the - Advanced Linux Sound Architecture Site and build it from + Advanced Linux Sound Architecture Site and build it from source.
    Download driver and library @@ -1256,9 +1284,9 @@ Windows binaries use the the 7.1 Windows SDK.END WARNING. 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. + 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: @@ -1273,15 +1301,15 @@ Windows binaries use the the 7.1 Windows SDK.END WARNING. on Windows which can be supplied by CYGWIN.

    - The OpenJDK build requires CYGWIN version 1.5.12 or newer. - Information about CYGWIN can - be obtained from the CYGWIN website at - www.cygwin.com. + The OpenJDK build requires CYGWIN version 1.5.12 or newer. + Information about CYGWIN can + be obtained from the CYGWIN website at + www.cygwin.com.

    - 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. + 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.

    @@ -1298,21 +1326,21 @@ Windows binaries use the the 7.1 Windows SDK.END WARNING. + utilities + NOTE: See the GNU make section + processor @@ -1354,21 +1382,21 @@ Windows binaries use the the 7.1 Windows SDK.END WARNING.
    Devel binutils The GNU assembler, linker and binary - utilities
    make.exe Devel make The GNU version of the 'make' utility built for CYGWIN.
    - NOTE: See the GNU make section
    m4.exe Interpreters m4 GNU implementation of the traditional Unix macro - processor
    cpio.exe

    - Note that the CYGWIN software can conflict with other non-CYGWIN - software on your Windows system. - CYGWIN provides a - FAQ for - known issues and problems, of particular interest is the - section on - - BLODA (applications that interfere with CYGWIN). + Note that the CYGWIN software can conflict with other non-CYGWIN + software on your Windows system. + CYGWIN provides a + FAQ for + known issues and problems, of particular interest is the + section on + + BLODA (applications that interfere with CYGWIN).

    - WARNING: - Be very careful with link.exe, it will conflict - with the Visual Studio version. You need the Visual Studio - version of link.exe, not the CYGWIN one. - So it's important that the Visual Studio paths in PATH preceed - the CYGWIN path /usr/bin. + WARNING: + Be very careful with link.exe, it will conflict + with the Visual Studio version. You need the Visual Studio + version of link.exe, not the CYGWIN one. + So it's important that the Visual Studio paths in PATH preceed + the CYGWIN path /usr/bin. Microsoft DirectX 9.0 SDK header files and libraries

    @@ -1377,7 +1405,7 @@ Windows binaries use the the 7.1 Windows SDK.END WARNING. OpenJDK. This SDK can be downloaded from - Microsoft DirectX 9.0 SDK (Summer 2004). + Microsoft DirectX 9.0 SDK (Summer 2004). If the link above becomes obsolete, the SDK can be found from the Microsoft Download Site (search with "DirectX 9.0 SDK Update Summer 2004"). @@ -1431,14 +1459,14 @@ Windows binaries use the the 7.1 Windows SDK.END WARNING.

    • - Solaris: - 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. + Solaris: + 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.

    @@ -1450,37 +1478,39 @@ Windows binaries use the the 7.1 Windows SDK.END WARNING. The default output directory is build/platform, where platform is one of - +
    + +
    In particular, the build/platform/j2sdk-image/bin directory should contain executables for the OpenJDK 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. + 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 - the jtreg site. + The provided regression tests can be run with the jtreg + utility from + the jtreg site.

    Environment/Make Variables

    - Some of the - environment or make variables (just called variables in this - document) that can impact the build are: + Some of the + environment or make variables (just called variables in this + document) that can impact the build are:

    PATH
    @@ -1488,11 +1518,11 @@ Windows binaries use the the 7.1 Windows SDK.END WARNING.
    MILESTONE
    @@ -1523,14 +1553,6 @@ Windows binaries use the the 7.1 Windows SDK.END WARNING. You should always install your own local Bootstrap JDK and always set ALT_BOOTDIR explicitly. -
    ALT_BINARY_PLUGS_PATH
    -
    - The location of the binary plugs installation. - See Binary Plugs for more information. - You should always have a local copy of a - recent Binary Plugs install image - and set this variable to that location. -
    ALT_JDK_IMPORT_PATH
    The location of a previously built JDK installation. @@ -1627,36 +1649,19 @@ Windows binaries use the the 7.1 Windows SDK.END WARNING. Where each of these directories contain the import JDK image for that platform.
    -
    ALT_BUILD_BINARY_PLUGS_PATH
    -
    - These are useful in managing builds on multiple platforms. - The default network location for all of the binary plug images - for all platforms. - If ALT_BINARY_PLUGS_PATH - 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, - and - windows-amd64. - Where each of these directories contain the binary plugs image - for that platform. -
    Windows specific:
    -
    ALT_MSDEVTOOLS_PATH
    +
    ALT_WINDOWSSDKDIR
    The location of the - Microsoft Visual Studio - tools 'bin' directory. - The default is usually derived from - ALT_COMPILER_PATH. + Microsoft Windows SDK where some tools will be + located. + The default is whatever WINDOWSSDKDIR is set to + (or WindowsSdkDir) or the path + 
    +                            c:\Program Files\Microsoft SDKs\Windows\v6.1a
+
    ALT_DXSDK_PATH
    @@ -1694,17 +1699,17 @@ Windows binaries use the the 7.1 Windows SDK.END WARNING. Look for the check list of the platform you are building on in the Table of Contents.

    - You can validate your build environment by using the sanity - target. - 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. + You can validate your build environment by using the sanity + target. + 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. + Some of the more common problems with builds are briefly described + below, with suggestions for remedies.

    • Slow Builds: @@ -1715,15 +1720,15 @@ Windows binaries use the the 7.1 Windows SDK.END WARNING. 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. + 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 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 - ccache. + Faster compiles are possible using a tool called + ccache.

  • @@ -1732,10 +1737,10 @@ Windows binaries use the the 7.1 Windows SDK.END WARNING. If you see warnings that refer to file time stamps, e.g.
    Warning message: File `xxx' has modification time in - the future. + the future.
    Warning message: Clock skew detected. Your build may - be incomplete. + 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 @@ -1747,9 +1752,9 @@ Windows binaries use the the 7.1 Windows SDK.END WARNING. 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. + 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.

  • @@ -1776,32 +1781,28 @@ Windows binaries use the the 7.1 Windows SDK.END WARNING.
    This is probably an issue with SELinux (See - http://en.wikipedia.org/wiki/SELinux). + http://en.wikipedia.org/wiki/SELinux). Parts of the VM is built without the -fPIC for performance reasons.

    - To completely disable SELinux: - -

      -
    1. $ su root
      2. -
    2. # system-config-securitylevel
      3. -
    3. In the window that appears, select the SELinux tab
      4. -
    4. Disable SELinux
      5. -
    - + To completely disable SELinux: +
      +
    1. $ su root
      2. +
    2. # system-config-securitylevel
      3. +
    3. In the window that appears, select the SELinux tab
      4. +
    4. Disable SELinux
      5. +

    - Alternatively, instead of completely disabling it you could - disable just this one check. - -

      -
    1. Select System->Administration->SELinux Management
      2. -
    2. In the SELinux Management Tool which appears, + Alternatively, instead of completely disabling it you could + disable just this one check. +
        +
      1. Select System->Administration->SELinux Management
        2. +
      2. In the SELinux Management Tool which appears, select "Boolean" from the menu on the left
        3. -
      3. Expand the "Memory Protection" group
        4. -
      4. Check the first item, labeled +
      5. Expand the "Memory Protection" group
        6. +
      6. Check the first item, labeled "Allow all unconfined executables to use libraries requiring text relocation ..."
        7. -
      -       +
  • @@ -1810,7 +1811,7 @@ Windows binaries use the the 7.1 Windows SDK.END WARNING. The CYGWIN software can conflict with other non-CYGWIN software. See the CYGWIN FAQ section on - BLODA (applications that interfere with CYGWIN). + BLODA (applications that interfere with CYGWIN).
  • diff --git a/get_source.sh b/get_source.sh new file mode 100644 index 0000000000000000000000000000000000000000..bc609b3ee8d0a52a4bba93bf6fd1085268aaef88 --- /dev/null +++ b/get_source.sh @@ -0,0 +1,33 @@ +#!/bin/sh + +# +# Copyright (c) 2010, Oracle and/or its affiliates. All rights reserved. +# DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER. +# +# This code is free software; you can redistribute it and/or modify it +# under the terms of the GNU General Public License version 2 only, as +# published by the Free Software Foundation. Oracle designates this +# particular file as subject to the "Classpath" exception as provided +# by Oracle in the LICENSE file that accompanied this code. +# +# This code is distributed in the hope that it will be useful, but WITHOUT +# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or +# FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License +# version 2 for more details (a copy is included in the LICENSE file that +# accompanied this code). +# +# You should have received a copy of the GNU General Public License version +# 2 along with this work; if not, write to the Free Software Foundation, +# Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA. +# +# Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA +# or visit www.oracle.com if you need additional information or have any +# questions. +# + +# Get clones of all nested repositories +sh ./make/scripts/hgforest.sh clone + +# Update all existing repositories to the latest sources +sh ./make/scripts/hgforest.sh pull -u + diff --git a/make/scripts/hgforest.sh b/make/scripts/hgforest.sh new file mode 100644 index 0000000000000000000000000000000000000000..7834826d8ebf50d91ac57c8030eb1af9e210cb34 --- /dev/null +++ b/make/scripts/hgforest.sh @@ -0,0 +1,104 @@ +#!/bin/sh + +# +# Copyright (c) 2009, 2010, Oracle and/or its affiliates. All rights reserved. +# DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER. +# +# This code is free software; you can redistribute it and/or modify it +# under the terms of the GNU General Public License version 2 only, as +# published by the Free Software Foundation. +# +# This code is distributed in the hope that it will be useful, but WITHOUT +# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or +# FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License +# version 2 for more details (a copy is included in the LICENSE file that +# accompanied this code). +# +# You should have received a copy of the GNU General Public License version +# 2 along with this work; if not, write to the Free Software Foundation, +# Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA. +# +# Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA +# or visit www.oracle.com if you need additional information or have any +# questions. +# + +# Shell script for a fast parallel forest command + +tmp=/tmp/forest.$$ +rm -f -r ${tmp} +mkdir -p ${tmp} + +# Remove tmp area on A. B. Normal termination +trap 'rm -f -r ${tmp}' KILL +trap 'rm -f -r ${tmp}' EXIT + +# Only look in specific locations for possible forests (avoids long searches) +pull_default="" +if [ "$1" = "clone" -o "$1" = "fclone" ] ; then + subrepos="corba jaxp jaxws langtools jdk hotspot" + if [ -f .hg/hgrc ] ; then + pull_default=`hg paths default` + fi + if [ "${pull_default}" = "" ] ; then + echo "ERROR: Need initial clone with 'hg paths default' defined" + exit 1 + fi + repos="" + for i in ${subrepos} ; do + if [ ! -f ${i}/.hg/hgrc ] ; then + repos="${repos} ${i}" + fi + done + at_a_time=2 +else + hgdirs=`ls -d ./.hg ./*/.hg ./*/*/.hg ./*/*/*/.hg ./*/*/*/*/.hg 2>/dev/null` + # Derive repository names from the .hg directory locations + repos="" + for i in ${hgdirs} ; do + repos="${repos} `echo ${i} | sed -e 's@/.hg$@@'`" + done + at_a_time=8 +fi + +# Any repos to deal with? +if [ "${repos}" = "" ] ; then + echo "No repositories to process." + exit +fi + +# Echo out what repositories we will process +echo "# Repos: ${repos}" + +# Run the supplied command on all repos in parallel, save output until end +n=0 +for i in ${repos} ; do + echo "Starting on ${i}" + n=`expr ${n} '+' 1` + ( + ( + if [ "$1" = "clone" -o "$1" = "fclone" ] ; then + cline="hg $* ${pull_default}/${i} ${i}" + echo "# ${cline}" + ( eval "${cline}" ) + else + cline="hg $*" + echo "# cd ${i} && ${cline}" + ( cd ${i} && eval "${cline}" ) + fi + echo "# exit code $?" + ) > ${tmp}/repo.${n} 2>&1 ; cat ${tmp}/repo.${n} ) & + if [ `expr ${n} '%' ${at_a_time}` -eq 0 ] ; then + sleep 5 + fi +done + +# Wait for all hg commands to complete +wait + +# Cleanup +rm -f -r ${tmp} + +# Terminate with exit 0 all the time (hard to know when to say "failed") +exit 0 +