Skip to content

Latest commit

 

History

History
856 lines (646 loc) · 48.2 KB

Build_Instructions_V17.md

File metadata and controls

856 lines (646 loc) · 48.2 KB
Raw

Building OpenJDK Version 17 with OpenJ9

Building OpenJDK 17 with OpenJ9 will be familiar to anyone who has already built OpenJDK. The easiest method involves the use of Docker and Dockerfiles to create a build environment that contains everything you need to produce a Linux binary of OpenJDK V17 with the Eclipse OpenJ9 virtual machine. If this method sounds ideal for you, go straight to the Linux 🐧 section.

Build instructions are available for the following platforms:

User documentation for the latest release of Eclipse OpenJ9 is available at the Eclipse Foundation. If you build a binary from the current OpenJ9 source, new features and changes might be in place for the next release of OpenJ9. Draft user documentation for the next release of OpenJ9 can be found here.

Linux

🐧 This build process provides detailed instructions for building a Linux x86-64 binary of OpenJDK V17 with OpenJ9 on Ubuntu 20. The binary can be built directly on your system, in a virtual machine, or in a Docker container 🐳.

If you are using a different Linux distribution, you might have to review the list of libraries that are bundled with your distribution and/or modify the instructions to use equivalent commands to the Advanced Packaging Tool (APT). For example, for Centos, substitute the apt-get command with yum.

If you want to build a binary for Linux on a different architecture, such as Power Systems™ or z Systems™, the process is very similar and any additional information for those architectures are included as Notes 📝 as we go along.

1. Prepare your system

🐧 Instructions are provided for preparing your system with and without the use of Docker technology.

Obtain the docker build script to determine the correct software pre-requisites for both.

Download the docker build script to your local system or copy and paste the following command:

wget https://raw.githubusercontent.com/eclipse-openj9/openj9/master/buildenv/docker/mkdocker.sh

Optionally, skip to Setting up your build environment without Docker.

Setting up your build environment with Docker 🐳

If you want to build a binary by using a Docker container, follow these steps to prepare your system:

  1. The first thing you need to do is install Docker. You can download the free Community edition from here, which also contains instructions for installing Docker on your system. You should also read the Getting started guide to familiarise yourself with the basic Docker concepts and terminology.

  2. Next, run the following command to build a Docker image, called openj9:

bash mkdocker.sh --tag=openj9 --dist=ubuntu --version=22 --gitcache=no --jdk=17 --build
  1. Start a Docker container from the openj9 image with the following command, where -v maps any directory, <host_directory>, on your local system to the containers /root/hostdir directory so that you can store the binaries, once they are built:
docker run -v <host_directory>:/root/hostdir -it openj9

📝 Depending on your Docker system configuration, you might need to prefix the docker commands with sudo.

Now that you have the Docker image running, you are ready to move to the next step, Get the source.

Setting up your build environment without Docker

If you don't want to user Docker, you can still build directly on your Ubuntu system or in a Ubuntu virtual machine. Use the output of the following command like a recipe card to determine the software dependencies that must be installed on the system, plus a few configuration steps.

bash mkdocker.sh --tag=openj9 --dist=ubuntu --version=22 --gitcache=no --jdk=17 --print
  1. Install the list of dependencies that can be obtained with the apt-get command from the following section of the Dockerfile:
apt-get update \
  && apt-get install -qq -y --no-install-recommends \
    ...
  1. The previous step installed g++-11 and gcc-11 packages, which might be different than the default version installed on your system. Export variables to set the version used in the build.
export CC=gcc-11 CXX=g++-11
  1. Download and setup the boot JDK using the latest AdoptOpenJDK v17 build.
cd <my_home_dir>
wget -O bootjdk17.tar.gz "https://api.adoptopenjdk.net/v3/binary/latest/17/ga/linux/x64/jdk/openj9/normal/adoptopenjdk"
tar -xzf bootjdk17.tar.gz
rm -f bootjdk17.tar.gz
mv $(ls | grep -i jdk-17) bootjdk17

2. Get the source

🐧 First you need to clone the Extensions for OpenJDK for OpenJ9 project. This repository is a git mirror of OpenJDK without the HotSpot JVM, but with an openj9 branch that contains a few necessary patches. Run the following command:

git clone https://github.com/ibmruntimes/openj9-openjdk-jdk17.git

Cloning this repository can take a while because OpenJDK is a large project! When the process is complete, change directory into the cloned repository:

cd openj9-openjdk-jdk17

Now fetch additional sources from the Eclipse OpenJ9 project and its clone of Eclipse OMR:

bash get_source.sh

📝 OpenSSL support: If you want to build an OpenJDK with OpenJ9 binary with OpenSSL support and you do not have a built version of OpenSSL v3.x available locally, you must specify -openssl-branch=<branch> where <branch> is an OpenSSL branch (or tag) like openssl-3.0.13. If the specified version of OpenSSL is already available in the standard location (SRC_DIR/openssl), get_source.sh uses it. Otherwise, the script deletes the content and downloads the specified version of OpenSSL source to the standard location and builds it. If you already have the version of OpenSSL in the standard location but you want a fresh copy, you must delete your current copy.

3. Configure

🐧 When you have all the source files that you need, run the configure script, which detects how to build in the current build environment.

bash configure --with-boot-jdk=/home/jenkins/bootjdks/jdk17

⚠️ The path in the example --with-boot-jdk= option is appropriate for the Docker installation. If you're not using the Docker environment, set the path that's appropriate for your setup, such as <my_home_dir>/bootjdk17.

📝 Configuring and building is not specific to OpenJ9 but uses the OpenJDK build infrastructure with OpenJ9 added. Many other configuration options are available, including options to increase the verbosity of the build output to include command lines (LOG=cmdlines), more info or debug information. For more information see OpenJDK build troubleshooting.

📝 Mixed and compressed references support: Different types of 64-bit builds can be created:

  • compressed references (only)
  • non-compressed references (only)
  • mixed references, either compressed or non-compressed references is selected when starting Java

Mixed references is the default to build when no options are specified. Note that --with-cmake=no cannot be used to build mixed references. configure options include:

  • --with-mixedrefs create a mixed references static build (equivalent to --with-mixedrefs=static)
  • --with-mixedrefs=no create a build supporting compressed references only
  • --with-mixedrefs=dynamic create a mixed references build that uses runtime checks
  • --with-mixedrefs=static (this is the default) create a mixed references build which avoids runtime checks by compiling source twice
  • --with-noncompressedrefs create a build supporting non-compressed references only

📝 OpenSSL support: If you want to build an OpenJDK that includes OpenSSL, you must specify --with-openssl={fetched|system|path_to_library}

where:

  • fetched uses the OpenSSL source downloaded by get-source.sh in step 2. Get the source.
  • system uses the package installed OpenSSL library in the system.
  • path_to_library uses a custom OpenSSL library that's already built.

If you want to include the OpenSSL cryptographic library in the OpenJDK binary, you must include --enable-openssl-bundling.

📝 When building using --with-cmake=no, you must specify freemarker.jar with an absolute path, such as --with-freemarker-jar=/root/freemarker.jar.

4. Build

🐧 Now you're ready to build OpenJDK V17 with OpenJ9:

make all

⚠️ If you just type make, rather than make all your build will be incomplete, because the default make target is exploded-image. If you want to specify make instead of make all, you must add --default-make-target=images when you run the configure script.

A binary for the full developer kit (jdk) is built and stored in the following directory:

  • build/linux-x86_64-server-release/images/jdk

    🐳 If you built your binaries in a Docker container, copy the binaries to the containers /root/hostdir directory so that you can access them on your local system. You'll find them in the directory you set for <host_directory> when you started your Docker container. See Setting up your build environment with Docker.

    📝 On other architectures the jdk directory is in build/linux-ppc64le-server-release/images (Linux on 64-bit Power systems) or build/linux-s390x-server-release/images (Linux on 64-bit z Systems).

📝 If you want a binary for the runtime environment (jre), you must run make legacy-jre-image, which produces a jre build in the build/linux-x86_64-server-release/images/jre directory.

📝 One of the images created with make all is the debug-image. This directory contains files that provide debug information for executables and shared libraries when using native debuggers. To use it, copy the contents of debug-image over the jdk before using the jdk with a native debugger. Another image created is the test image, which contains executables and native libraries required when running some functional and OpenJDK testing. For local testing set the NATIVE_TEST_LIBS environment variable to the test image location, see the OpenJ9 test user guide.

5. Test

🐧 For a simple test, try running the java -version command. Change to the jdk directory:

cd build/linux-x86_64-server-release/images/jdk

Run:

./bin/java -version

Here is some sample output:

openjdk version "17-internal" 2021-09-14
OpenJDK Runtime Environment (build 17-internal+0-adhoc.userid.jdk17)
Eclipse OpenJ9 VM (build v0.28.0-release-58b3fc7e628, JRE 17 Linux amd64-64-Bit Compressed References 20210907_17 (JIT enabled, AOT enabled)
OpenJ9   - 58b3fc7e628
OMR      - 6b8136da4f3
JCL      - b6c1a570c77 based on jdk-17+35)

📝 OpenSSL support: If you built an OpenJDK with OpenJ9 that includes OpenSSL v1.x support, the following acknowledgments apply in accordance with the license terms:

  • This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (https://www.openssl.org/).
  • This product includes cryptographic software written by Eric Young ([email protected]).

🐧 Congratulations! 🎉

AIX

📘

The following instructions guide you through the process of building an OpenJDK V17 binary that contains Eclipse OpenJ9 on AIX 7.2.

1. Prepare your system

📘 You must install the following AIX Licensed Program Products (LPPs):

You must also install the boot JDK: Java17_AIX_PPC64.

A number of RPM packages are also required. The easiest method for installing these packages is to use yum, because yum takes care of any additional dependent packages for you.

Download the following file: yum_install_aix-ppc64.txt

This file contains a list of required RPM packages that you can install by specifying the following command:

yum shell yum_install_aix-ppc64.txt

It is important to take the list of package dependencies from this file because it is kept up to date by our developers.

Only when building with --with-cmake=no, download and setup freemarker.jar into your home directory by running the following commands:

cd <my_home_dir>
wget https://sourceforge.net/projects/freemarker/files/freemarker/2.3.8/freemarker-2.3.8.tar.gz/download -O freemarker.tgz
tar -xzf freemarker.tgz freemarker-2.3.8/lib/freemarker.jar --strip-components=2
rm -f freemarker.tgz

2. Get the source

📘 First you need to clone the Extensions for OpenJDK for OpenJ9 project. This repository is a git mirror of OpenJDK without the HotSpot JVM, but with an openj9 branch that contains a few necessary patches. Run the following command:

git clone https://github.com/ibmruntimes/openj9-openjdk-jdk17.git

Cloning this repository can take a while because OpenJDK is a large project! When the process is complete, change directory into the cloned repository:

cd openj9-openjdk-jdk17

Now fetch additional sources from the Eclipse OpenJ9 project and its clone of Eclipse OMR:

bash get_source.sh

📝 OpenSSL support: If you want to build an OpenJDK with OpenJ9 binary with OpenSSL support and you do not have a built version of OpenSSL v3.x available locally, you must specify -openssl-branch=<branch> where <branch> is an OpenSSL branch (or tag) like openssl-3.0.13. If the specified version of OpenSSL is already available in the standard location (SRC_DIR/openssl), get_source.sh uses it. Otherwise, the script deletes the content and downloads the specified version of OpenSSL source to the standard location and builds it. If you already have the version of OpenSSL in the standard location but you want a fresh copy, you must delete your current copy.

3. Configure

📘 When you have all the source files that you need, run the configure script, which detects how to build in the current build environment.

bash configure \
    --with-boot-jdk=<path_to_boot_JDK17> \
    --with-cups-include=<cups_include_path> \
    --disable-warnings-as-errors

where <cups_include_path> is the absolute path to CUPS. For example, /opt/freeware/include.

📝 Configuring and building is not specific to OpenJ9 but uses the OpenJDK build infrastructure with OpenJ9 added. Many other configuration options are available, including options to increase the verbosity of the build output to include command lines (LOG=cmdlines), more info or debug information. For more information see OpenJDK build troubleshooting.

📝 Mixed and compressed references support: Different types of 64-bit builds can be created:

  • compressed references (only)
  • non-compressed references (only)
  • mixed references, either compressed or non-compressed references is selected when starting Java

Mixed references is the default to build when no options are specified. Note that --with-cmake=no cannot be used to build mixed references. configure options include:

  • --with-mixedrefs create a mixed references static build (equivalent to --with-mixedrefs=static)
  • --with-mixedrefs=no create a build supporting compressed references only
  • --with-mixedrefs=dynamic create a mixed references build that uses runtime checks
  • --with-mixedrefs=static (this is the default) create a mixed references build which avoids runtime checks by compiling source twice
  • --with-noncompressedrefs create a build supporting non-compressed references only

📝 OpenSSL support: If you want to build an OpenJDK that includes OpenSSL, you must specify --with-openssl={fetched|system|path_to_library}

where:

  • fetched uses the OpenSSL source downloaded by get-source.sh in step 2. Get the source.

  • system uses the package installed OpenSSL library in the system.

  • path_to_library uses a custom OpenSSL library that's already built.

    If you want to include the OpenSSL cryptographic library in the OpenJDK binary, you must include --enable-openssl-bundling.

📝 When building using --with-cmake=no, you must specify freemarker.jar with an absolute path, such as --with-freemarker-jar=<my_home_dir>/freemarker.jar, where <my_home_dir> is the location where you stored freemarker.jar.

4. build

📘 Now you're ready to build OpenJDK with OpenJ9:

make all

⚠️ If you just type make, rather than make all your build will be incomplete, because the default make target is exploded-image. If you want to specify make instead of make all, you must add --default-make-target=images when you run the configure script.

A binary for the full developer kit (jdk) is built and stored in the following directory:

  • build/aix-ppc64-server-release/images/jdk

📝 If you want a binary for the runtime environment (jre), you must run make legacy-jre-image, which produces a jre build in the build/aix-ppc64-server-release/images/jre directory.

📝 One of the images created with make all is the debug-image. This directory contains files that provide debug information for executables and shared libraries when using native debuggers. To use it, copy the contents of debug-image over the jdk before using the jdk with a native debugger. Another image created is the test image, which contains executables and native libraries required when running some functional and OpenJDK testing. For local testing set the NATIVE_TEST_LIBS environment variable to the test image location, see the OpenJ9 test user guide.

5. Test

📘 For a simple test, try running the java -version command. Change to the /jdk directory:

cd build/aix-ppc64-server-release/images/jdk

Run:

./bin/java -version

Here is some sample output:

openjdk version "17-internal" 2021-09-14
OpenJDK Runtime Environment (build 17-internal+0-adhoc.userid.jdk17)
Eclipse OpenJ9 VM (build v0.28.0-release-58b3fc7e628, JRE 17 AIX ppc64-64-Bit Compressed References 20210907_17 (JIT enabled, AOT enabled)
OpenJ9   - 58b3fc7e628
OMR      - 6b8136da4f3
JCL      - b6c1a570c77 based on jdk-17+35)

📝 OpenSSL support: If you built an OpenJDK with OpenJ9 that includes OpenSSL v1.x support, the following acknowledgments apply in accordance with the license terms:

  • This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (https://www.openssl.org/).
  • This product includes cryptographic software written by Eric Young ([email protected]).

📘 Congratulations! 🎉

Windows

📒

The following instructions guide you through the process of building a Windows OpenJDK V17 binary that contains Eclipse OpenJ9. This process can be used to build binaries for Windows.

1. Prepare your system

📒 You must install a number of software dependencies to create a suitable build environment on your system:

  • Cygwin, which provides a Unix-style command line interface. Install all packages in the Devel category. In the Archive category, install the packages zip and unzip. In the Utils category, install the cpio package. Install any further package dependencies that are identified by the installer. More information about using Cygwin can be found here.
  • Windows JDK 17, which is used as the boot JDK.
  • Microsoft Visual Studio 2022, which is the default compiler level used by OpenJDK17.
  • Freemarker V2.3.8 - only when building with --with-cmake=no
  • LLVM/Clang
  • NASM Assembler v2.13.03 or newer

Add the binary path of Clang to the PATH environment variable to override the older version of clang integrated in Cygwin. e.g.

export PATH="/cygdrive/c/Program Files/LLVM/bin:$PATH" (in Cygwin)

Add the path to nasm.exe to the PATH environment variable to override the older version of NASM installed in Cygwin. e.g.

export PATH="/cygdrive/c/Program Files/NASM:$PATH" (in Cygwin)

You can download Visual Studio manually or obtain it using the wget utility. If you choose to use wget, follow these steps:

  • Open a cygwin terminal and change to the /temp directory:
cd /cygdrive/c/temp
  • Run the following command:
wget https://aka.ms/vs/17/release/vs_community.exe -O vs2022.exe
  • Before installing Visual Studio, change the permissions on the installation file by running chmod u+x vs2022.exe.
  • Install Visual Studio by running the file vs2022.exe (There is no special step required for installing. Please follow the guide of the installer to install all desired components, the C++ compiler is required).

Not all of the shared libraries that are included with Visual Studio are registered during installation. In particular, the msdia140.dll libraries must be registered manually by running command prompt as administrator. To do so, execute the following from a command prompt:

regsvr32 "C:\Program Files (x86)\Microsoft Visual Studio\2022\Community\DIA SDK\bin\msdia140.dll"
regsvr32 "C:\Program Files (x86)\Microsoft Visual Studio\2022\Community\DIA SDK\bin\amd64\msdia140.dll"
  • When building with --with-cmake=no, unpack the Freemarker archive:
tar -xzf freemarker.tgz freemarker-2.3.8/lib/freemarker.jar --strip-components=2

2. Get the source

📒 First you need to clone the Extensions for OpenJDK for OpenJ9 project. This repository is a git mirror of OpenJDK without the HotSpot JVM, but with an openj9 branch that contains a few necessary patches.

Run the following command in the Cygwin terminal:

git clone https://github.com/ibmruntimes/openj9-openjdk-jdk17.git

Cloning this repository can take a while because OpenJDK is a large project! When the process is complete, change directory into the cloned repository:

cd openj9-openjdk-jdk17

Now fetch additional sources from the Eclipse OpenJ9 project and its clone of Eclipse OMR:

bash get_source.sh

📝 Do not check out the source code in a path which contains spaces or has a long name or is nested many levels deep.

📝 Create the directory that is going to contain the OpenJDK clone by using the mkdir command in the Cygwin bash shell and not using Windows Explorer. This ensures that it will have proper Cygwin attributes, and that its children will inherit those attributes.

📝 OpenSSL support: If you want to build an OpenJDK with OpenJ9 binary with OpenSSL support and you do not have a built version of OpenSSL v3.x available locally, you must specify -openssl-branch=<branch> where <branch> is an OpenSSL branch (or tag) like openssl-3.0.13. If the specified version of OpenSSL is already available in the standard location (SRC_DIR/openssl), get_source.sh uses it. Otherwise, the script deletes the content and downloads the specified version of OpenSSL source to the standard location and builds it. If you already have the version of OpenSSL in the standard location but you want a fresh copy, you must delete your current copy.

3. Configure

📒 When you have all the source files that you need, run the configure script, which detects how to build in the current build environment.

bash configure \
    --with-boot-jdk=<path_to_boot_JDK17> \
    --disable-warnings-as-errors

Note: If you have multiple versions of Visual Studio installed, you can enforce a specific version to be used by setting --with-toolchain-version, i.e., by including --with-toolchain-version=2019 option in the configure command.

📝 Configuring and building is not specific to OpenJ9 but uses the OpenJDK build infrastructure with OpenJ9 added. Many other configuration options are available, including options to increase the verbosity of the build output to include command lines (LOG=cmdlines), more info or debug information. For more information see OpenJDK build troubleshooting.

📝 Mixed and compressed references support: Different types of 64-bit builds can be created:

  • compressed references (only)
  • non-compressed references (only)
  • mixed references, either compressed or non-compressed references is selected when starting Java

Mixed references is the default to build when no options are specified. Note that --with-cmake=no cannot be used to build mixed references. configure options include:

  • --with-mixedrefs create a mixed references static build (equivalent to --with-mixedrefs=static)
  • --with-mixedrefs=no create a build supporting compressed references only
  • --with-mixedrefs=dynamic create a mixed references build that uses runtime checks
  • --with-mixedrefs=static (this is the default) create a mixed references build which avoids runtime checks by compiling source twice
  • --with-noncompressedrefs create a build supporting non-compressed references only

📝 OpenSSL support: If you want to build an OpenJDK that includes OpenSSL, you must specify --with-openssl={fetched|path_to_library}

where:

  • fetched uses the OpenSSL source downloaded by get-source.sh in step 2. Get the source.
  • path_to_library uses a custom OpenSSL library that's already built.

If you want to include the OpenSSL cryptographic library in the OpenJDK binary, you must include --enable-openssl-bundling.

📝 When building using --with-cmake=no, you must specify freemarker.jar with an absolute path, such as --with-freemarker-jar=/cygdrive/c/temp/freemarker.jar.

4. build

📒 Now you're ready to build OpenJDK with OpenJ9:

make all

⚠️ If you just type make, rather than make all your build will be incomplete, because the default make target is exploded-image. If you want to specify make instead of make all, you must add --default-make-target=images when you run the configure script.

A binary for the full developer kit (jdk) is built and stored in the following directory:

  • build/windows-x86_64-server-release/images/jdk

📝 If you want a binary for the runtime environment (jre), you must run make legacy-jre-image, which produces a jre build in the build/windows-x86_64-server-release/images/jre directory.

📝 One of the images created with make all is the debug-image. This directory contains files that provide debug information for executables and shared libraries when using native debuggers. To use it, copy the contents of debug-image over the jdk before using the jdk with a native debugger. Another image created is the test image, which contains executables and native libraries required when running some functional and OpenJDK testing. For local testing set the NATIVE_TEST_LIBS environment variable to the test image location, see the OpenJ9 test user guide.

5. Test

📒 For a simple test, try running the java -version command. Change to the jdk directory:

cd build/windows-x86_64-server-release/images/jdk

Run:

./bin/java -version

Here is some sample output:

openjdk version "17-internal" 2021-09-14
OpenJDK Runtime Environment (build 17-internal+0-adhoc.userid.jdk17)
Eclipse OpenJ9 VM (build v0.28.0-release-58b3fc7e628, JRE 17 Windows Server 2016 amd64-64-Bit Compressed References 20210907_17 (JIT enabled, AOT enabled)
OpenJ9   - 58b3fc7e628
OMR      - 6b8136da4f3
JCL      - b6c1a570c77 based on jdk-17+35)

📝 OpenSSL support: If you built an OpenJDK with OpenJ9 that includes OpenSSL v1.x support, the following acknowledgments apply in accordance with the license terms:

  • This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (https://www.openssl.org/).
  • This product includes cryptographic software written by Eric Young ([email protected]).

📒 Congratulations! 🎉

macOS

🍎 The following instructions guide you through the process of building a macOS OpenJDK V17 binary that contains Eclipse OpenJ9. This process can be used to build binaries for macOS 10.

1. Prepare your system

🍎 You must install a number of software dependencies to create a suitable build environment on your system (the specified versions are minimums):

The following dependencies can be installed by using Homebrew (the specified versions are minimums):

Only when building with --with-cmake=no, Freemarker V2.3.8 is also required, which can be obtained and installed with the following commands:

wget https://sourceforge.net/projects/freemarker/files/freemarker/2.3.8/freemarker-2.3.8.tar.gz/download -O freemarker.tgz
gtar -xzf freemarker.tgz freemarker-2.3.8/lib/freemarker.jar --strip-components=2
rm -f freemarker.tgz

Bash version 4 is required by the get_source.sh script that you will use in step 2, which is installed to /usr/local/bin/bash. To prevent problems during the build process, make Bash v4 your default shell by typing the following commands:

# Find the <CURRENT_SHELL> for <USERNAME>
dscl . -read <USERNAME> UserShell

# Change the shell to Bash version 4 for <USERNAME>
dscl . -change <USERNAME> UserShell <CURRENT_SHELL> /usr/local/bin/bash

# Verify that the shell has been changed
dscl . -read <USERNAME> UserShell

2. Get the source

🍎 First you need to clone the Extensions for OpenJDK for OpenJ9 project. This repository is a git mirror of OpenJDK without the HotSpot JVM, but with an openj9 branch that contains a few necessary patches.

Run the following command:

git clone https://github.com/ibmruntimes/openj9-openjdk-jdk17.git

Cloning this repository can take a while because OpenJDK is a large project! When the process is complete, change directory into the cloned repository:

cd openj9-openjdk-jdk17

Now fetch additional sources from the Eclipse OpenJ9 project and its clone of Eclipse OMR:

bash get_source.sh

📝 OpenSSL support: If you want to build an OpenJDK with OpenJ9 binary with OpenSSL support and you do not have a built version of OpenSSL v3.x available locally, you must specify -openssl-branch=<branch> where <branch> is an OpenSSL branch (or tag) like openssl-3.0.13. If the specified version of OpenSSL is already available in the standard location (SRC_DIR/openssl), get_source.sh uses it. Otherwise, the script deletes the content and downloads the specified version of OpenSSL source to the standard location and builds it. If you already have the version of OpenSSL in the standard location but you want a fresh copy, you must delete your current copy.

3. Configure

🍎 When you have all the source files that you need, run the configure script, which detects how to build in the current build environment.

bash configure --with-boot-jdk=<path_to_boot_JDK17>

📝 Configuring and building is not specific to OpenJ9 but uses the OpenJDK build infrastructure with OpenJ9 added. Many other configuration options are available, including options to increase the verbosity of the build output to include command lines (LOG=cmdlines), more info or debug information. For more information see OpenJDK build troubleshooting.

📝 Mixed and compressed references support: Different types of 64-bit builds can be created:

  • compressed references (only)
  • non-compressed references (only)
  • mixed references, either compressed or non-compressed references is selected when starting Java

Mixed references is the default to build when no options are specified. Note that --with-cmake=no cannot be used to build mixed references. configure options include:

  • --with-mixedrefs create a mixed references static build (equivalent to --with-mixedrefs=static)
  • --with-mixedrefs=no create a build supporting compressed references only
  • --with-mixedrefs=dynamic create a mixed references build that uses runtime checks
  • --with-mixedrefs=static (this is the default) create a mixed references build which avoids runtime checks by compiling source twice
  • --with-noncompressedrefs create a build supporting non-compressed references only

📝 AArch64 macOS only:

  • Please specify --with-noncompressedrefs because compressed references are not supported on AArch64 macOS yet.
  • --with-cmake=no is not supported on AArch64 macOS. Please use cmake.

📝 OpenSSL support: If you want to build an OpenJDK that includes OpenSSL, you must specify --with-openssl={fetched|path_to_library}

where:

  • fetched uses the OpenSSL source downloaded by get-source.sh in step 2. Get the source.
  • path_to_library uses a custom OpenSSL library that's already built.

If you want to include the OpenSSL cryptographic library in the OpenJDK binary, you must include --enable-openssl-bundling.

📝 When building using --with-cmake=no, you must specify freemarker.jar with an absolute path, such as --with-freemarker-jar=<path_to>/freemarker.jar, where <path_to> is the location where you stored freemarker.jar.

4. build

🍎 Now you're ready to build OpenJDK with OpenJ9:

make all

⚠️ If you just type make, rather than make all your build will be incomplete, because the default make target is exploded-image. If you want to specify make instead of make all, you must add --default-make-target=images when you run the configure script.

Two builds of OpenJDK with Eclipse OpenJ9 are built and stored in the following directories:

  • build/macosx-x86_64-server-release/images/jdk

  • build/macosx-x86_64-server-release/images/jdk-bundle

    📝 For running applications such as Eclipse, use the -bundle version.

📝 If you want a binary for the runtime environment (jre), you must run make legacy-jre-image, which produces a jre build in the build/macosx-x86_64-server-release/images/jre directory.

📝 One of the images created with make all is the debug-image. This directory contains files that provide debug information for executables and shared libraries when using native debuggers. To use it, copy the contents of debug-image over the jdk before using the jdk with a native debugger. Another image created is the test image, which contains executables and native libraries required when running some functional and OpenJDK testing. For local testing set the NATIVE_TEST_LIBS environment variable to the test image location, see the OpenJ9 test user guide.

5. Test

🍎 For a simple test, try running the java -version command. Change to the jdk directory:

cd build/macosx-x86_64-server-release/images/jdk

Run:

./bin/java -version

Here is some sample output:

openjdk version "17-internal" 2021-09-14
OpenJDK Runtime Environment (build 17-internal+0-adhoc.userid.jdk17)
Eclipse OpenJ9 VM (build v0.28.0-release-58b3fc7e628, JRE 17 Mac OS X amd64-64-Bit Compressed References 20210907_17 (JIT enabled, AOT enabled)
OpenJ9   - 58b3fc7e628
OMR      - 6b8136da4f3
JCL      - b6c1a570c77 based on jdk-17+35)

📝 OpenSSL support: If you built an OpenJDK with OpenJ9 that includes OpenSSL v1.x support, the following acknowledgments apply in accordance with the license terms:

  • This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (https://www.openssl.org/).
  • This product includes cryptographic software written by Eric Young ([email protected]).

📒 Congratulations! 🎉

AArch64

🐧 The following instructions guide you through the process of building an OpenJDK V17 binary that contains Eclipse OpenJ9 for AArch64 (ARMv8 64-bit) Linux.

1. Prepare your system

The binary can be built on your AArch64 Linux system, or in a Docker container 🐳 on x86-64 Linux.

2. Get the source

🐧 First you need to clone the Extensions for OpenJDK for OpenJ9 project. This repository is a git mirror of OpenJDK without the HotSpot JVM, but with an openj9 branch that contains a few necessary patches. Run the following command:

git clone https://github.com/ibmruntimes/openj9-openjdk-jdk17.git

Cloning this repository can take a while because OpenJDK is a large project! When the process is complete, change directory into the cloned repository:

cd openj9-openjdk-jdk17

Now fetch additional sources from the Eclipse OpenJ9 project and its clone of Eclipse OMR:

bash get_source.sh

📝 OpenSSL support: On an AArch64 Linux system if you want to build an OpenJDK with OpenJ9 binary with OpenSSL support and you do not have a built version of OpenSSL v3.x available locally, you must specify -openssl-branch=<branch> where <branch> is an OpenSSL branch (or tag) like openssl-3.0.13. If the specified version of OpenSSL is already available in the standard location (SRC_DIR/openssl), get_source.sh uses it. Otherwise, the script deletes the content and downloads the specified version of OpenSSL source to the standard location and builds it. If you already have the version of OpenSSL in the standard location but you want a fresh copy, you must delete your current copy.

3. Prepare for build on AArch64 Linux

You must install a number of software dependencies to create a suitable build environment on your AArch64 Linux system:

See Setting up your build environment without Docker in Linux section for other dependencies to be installed.

4. Create the Docker image

If you build the binary on x86-64 Linux, run the following commands to build a Docker image for AArch64 cross-compilation, called openj9aarch64:

cd openj9/buildenv/docker/aarch64-linux_CC
docker build -t openj9aarch64 -f Dockerfile .

Start a Docker container from the openj9aarch64 image with the following command, where <host_directory> is the directory that contains openj9-openjdk-jdk17 in your local system:

docker run -v <host_directory>/openj9-openjdk-jdk17:/root/openj9-openjdk-jdk17 -it openj9aarch64

Then go to the openj9-openjdk-jdk17 directory:

cd /root/openj9-openjdk-jdk17

5. Configure

🐧 When you have all the source files that you need, run the configure script, which detects how to build in the current build environment.

For building on AArch64 Linux:

bash configure --with-boot-jdk=<path_to_boot_JDK> \
               --disable-warnings-as-errors

For building in the Docker container:

bash configure --openjdk-target=${OPENJ9_CC_PREFIX} \
               --with-x=${OPENJ9_CC_DIR}/${OPENJ9_CC_PREFIX}/ \
               --with-freetype-include=${OPENJ9_CC_DIR}/${OPENJ9_CC_PREFIX}/libc/usr/include/freetype2 \
               --with-freetype-lib=${OPENJ9_CC_DIR}/${OPENJ9_CC_PREFIX}/libc/usr/lib \
               --with-boot-jdk=/root/bootjdk17 \
               --with-build-jdk=/root/bootjdk17 \
               --disable-warnings-as-errors \
               --disable-ddr

📝 Configuring and building is not specific to OpenJ9 but uses the OpenJDK build infrastructure with OpenJ9 added. Many other configuration options are available, including options to increase the verbosity of the build output to include command lines (LOG=cmdlines), more info or debug information. For more information see OpenJDK build troubleshooting.

📝 Mixed and compressed references support: Different types of 64-bit builds can be created:

  • compressed references (only)
  • non-compressed references (only)
  • mixed references, either compressed or non-compressed references is selected when starting Java

Mixed references is the default to build when no options are specified. Note that --with-cmake=no cannot be used to build mixed references. configure options include:

  • --with-mixedrefs create a mixed references static build (equivalent to --with-mixedrefs=static)
  • --with-mixedrefs=no create a build supporting compressed references only
  • --with-mixedrefs=dynamic create a mixed references build that uses runtime checks
  • --with-mixedrefs=static (this is the default) create a mixed references build which avoids runtime checks by compiling source twice
  • --with-noncompressedrefs create a build supporting non-compressed references only

📝 OpenSSL support: If you want to build an OpenJDK that uses OpenSSL, you must specify --with-openssl={fetched|system|path_to_library}

where:

  • fetched uses the OpenSSL source downloaded by get-source.sh in step 2. Get the source. Using --with-openssl=fetched will fail during the build in the Docker environment.
  • system uses the package installed OpenSSL library in the system. Use this option when you build on your AArch64 Linux system.
  • path_to_library uses an OpenSSL v3.x library that's already built. You can use ${OPENJ9_CC_DIR}/${OPENJ9_CC_PREFIX}/libc/usr as path_to_library when you are configuring in the Docker container.

If you want to include the OpenSSL cryptographic library in the OpenJDK binary, you must include --enable-openssl-bundling.

📝 DDR support: You can build DDR support only on AArch64 Linux. If you are building in a cross-compilation environment, you need the --disable-ddr option.

📝 CUDA support: You can enable CUDA support if you are building on NVIDIA Jetson Developer Kit series. Add --enable-cuda --with-cuda=/usr/local/cuda when you run configure. The path /usr/local/cuda may be different depending on the version of JetPack.

📝 You may need to add --disable-warnings-as-errors-openj9 depending on the toolchain version.

📝 When building using --with-cmake=no, you must specify freemarker.jar with an absolute path, such as --with-freemarker-jar=<path_to>/freemarker.jar, where <path_to> is the location where you stored freemarker.jar.

6. Build

🐧 Now you're ready to build OpenJDK with OpenJ9:

make all

⚠️ If you just type make, rather than make all your build will be incomplete, because the default make target is exploded-image. If you want to specify make instead of make all, you must add --default-make-target=images when you run the configure script.

A binary for the full developer kit (jdk) is built and stored in the following directory:

  • build/linux-aarch64-normal-server-release/images/jdk

Copy its contents to your AArch64 Linux device.

📝 If you want a binary for the runtime environment (jre), you must run make legacy-jre-image, which produces a jre build in the build/linux-aarch64-normal-server-release/images/jre directory.

📝 One of the images created with make all is the debug-image. This directory contains files that provide debug information for executables and shared libraries when using native debuggers. To use it, copy the contents of debug-image over the jdk before using the jdk with a native debugger. Another image created is the test image, which contains executables and native libraries required when running some functional and OpenJDK testing. For local testing set the NATIVE_TEST_LIBS environment variable to the test image location, see the OpenJ9 test user guide.

6. Test

🐧 For a simple test, try running the java -version command. Change to your jdk directory on AArch64 Linux:

cd build/linux-aarch64-normal-server-release/images/jdk

Run:

./bin/java -version

Here is some sample output:

openjdk version "17-internal" 2021-09-14
OpenJDK Runtime Environment (build 17-internal+0-adhoc.userid.jdk17)
Eclipse OpenJ9 VM (build v0.28.0-release-58b3fc7e628, JRE 17 Linux aarch64-64-Bit Compressed References 20210907_17 (JIT enabled, AOT enabled)
OpenJ9   - 58b3fc7e628
OMR      - 6b8136da4f3
JCL      - b6c1a570c77 based on jdk-17+35)

📝 OpenSSL support: If you built an OpenJDK with OpenJ9 that includes OpenSSL v1.x support, the following acknowledgments apply in accordance with the license terms:

  • This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (https://www.openssl.org/).
  • This product includes cryptographic software written by Eric Young ([email protected]).

🐧 Congratulations! 🎉