%general-entities; ]> $LastChangedBy: pierre $ $Date: 2015-03-04 17:17:44 -0500 (Wed, 04 Mar 2015) $ OpenJDK OpenJDK is an open-source implementation of Oracle's Java Standard Edition platform. OpenJDK is useful for developing Java programs, and provides a complete runtime environment to run Java programs. &lfs77_checked; A browser plugin and webstart implementation, as well as a pulseaudio sound backend are provided by the Icedtea project. To provide a complete implementation, you will need to later install and . OpenJDK is GPL'd code, with a special exception made for non-free projects to use these classes in their proprietary products. In similar fashion to the LGPL, which allows non-free programs to link to libraries provided by free software, the GNU General Public License, version 2, with the Classpath Exception allows third party programs to use classes provided by free software without the requirement that the third party software also be free. As with the LGPL, any modifications made to the free software portions of a third party application, must also be made freely available. The OpenJDK source includes a very thorough, open source test suite using the JTreg test harness. The testing instructions below allow to test the just built JDK for reasonable compatibility with the proprietary Oracle JDK. However, in order for an independent implementation to claim compatibility, it must pass a proprietary JCK/TCK test suite. No claims of compatibility, even partial compatibility, may be made without passing an approved test suite. Oracle does provide free community access, on a case by case basis, to a closed toolkit to ensure 100% compatibility with its proprietary JDK. Neither the binary version provided on the page nor the JVM built with the instructions below have been tested against the TCK. Any version that is built using the instructions given, cannot claim to be compatible with the proprietary JDK, without the user applying for, and completing the compatibility tests themselves. With that in mind, the binaries produced using this build method are regularly tested against the TCK by the members listed on the site above. In addition to the community license above, an educational, non-commercial license for the TCK can be obtained from here. Source Package Information OpenJDK Root Package Download: Download MD5 sum: &ojdk-md5sum; Download Size: &ojdk-size; The following files may be downladed from the OpenJDK mercurial repository using the addresses , where <component> is the name of the JVM component (corba, hostspot, and so on), but that involves renaming the downloaded files, and renaming the extracted directories. For convenience, the BLFS editors have made the files available in an LFS website. Corba Source Download: Download MD5 sum: &corba-md5sum; Download Size: &corba-size; Hotspot Source Download: Download MD5 sum: &hotspot-md5sum; Download Size: &hotspot-size; JAXP Source Download: Download MD5 sum: &jaxp-md5sum; Download Size: &jaxp-size; JAXWS Source Download: Download MD5 sum: &jaxws-md5sum; Download Size: &jaxws-size; Langtools Source Download: Download MD5 sum: &langtools-md5sum; Download Size: &langtools-size; JDK Source Download: Download MD5 sum: &jdk-md5sum; Download Size: &jdk-size; Nashorn Source Download: Download MD5 sum: &nashorn-md5sum; Download Size: &nashorn-size; Estimated disk space required: &ojdk-buildsize; Estimated build time: &ojdk-time; Additional Downloads Optional package (to get an icon for the openjdk-8-policytool.desktop file): Optional test harness: OpenJDK Dependencies Required Dependencies An existing binary ( or an earlier built version of this package), , , , , , , and Recommended and Optional and (for the tests) User Notes: Unlike other packages in BLFS, the OpenJDK source packages are distributed in multiple tar balls. You need to first extract the source root from &ojdk-tarball;, change into the extracted directory, then proceed with the following instructions: tar -xf ../corba.tar.xz && tar -xf ../hotspot.tar.xz && tar -xf ../jaxp.tar.xz && tar -xf ../jaxws.tar.xz && tar -xf ../jdk.tar.xz && tar -xf ../langtools.tar.xz && tar -xf ../nashorn.tar.xz If you have downloaded the test harness, unpack it too: tar -xf ../jtreg&jtreg-version;.tar.gz Fix an issue with the new (since 5.1.0) giflib API: sed -e 's/DGifCloseFile(gif/&, NULL/' \ -e '/DGifOpen/s/c)/c, NULL)/' \ -i jdk/src/share/native/sun/awt/splashscreen/splashscreen_gif.c Fix a bug in a shell script used to set the flags for make: sed 's/\([ \t]\)\]\([^\]\)/\1I]\2/g' \ -i hotspot/make/linux/makefiles/adjust-mflags.sh Before proceeding, you should ensure that your environment PATH variable contains the location of the Java compilers used for bootstrapping OpenJDK. This is the only requirement for the environment. Modern Java installations do not need JAVA_HOME and CLASSPATH is not used here. Furthermore, OpenJDK developers recommand to unset JAVA_HOME. The build system does not support the -j switch in MAKEFLAGS. Configure and build the package with the following commands (--with-milestone value can be modified to fit user preferences): unset JAVA_HOME && sh ./configure \ --with-update-version=&ojdk-upd; \ --with-build-number=&ojdk-bd; \ --with-milestone=BLFS \ --enable-unlimited-crypto \ --with-zlib=system \ --with-giflib=system && make DEBUG_BINARIES=true all It seems that the test infrastructure of OpenJDK is a work in progress, so that testing the newly built JVM involves several steps. First, it is better to run the test suite in a frame buffer on a different display, using Xvfb: if [ -n "$DISPLAY" ]; then OLD_DISP=$DISPLAY fi export DISPLAY=:20 nohup Xvfb $DISPLAY \ -fbdir $(pwd) \ -pixdepths 8 16 24 32 > Xvfb.out 2>&1 & echo $! > Xvfb.pid echo Waiting for Xvfb to initialize; sleep 1 nohup twm -display $DISPLAY \ -f /dev/null > twm.out 2>&1 & echo $! > twm.pid echo Waiting for twm to initialize; sleep 1 xhost + Then, it is necessary to modify some files: echo -e " jdk_all = :jdk_core \\ :jdk_svc \\ :jdk_beans \\ :jdk_imageio \\ :jdk_sound \\ :jdk_sctp \\ com/sun/awt \\ javax/accessibility \\ javax/print \\ sun/pisces \\ com/sun/java/swing" >> jdk/test/TEST.groups && sed -e 's/all:.*jck.*/all: jtreg/' \ -i langtools/test/Makefile Some variables have to be set: JT_JAVA=$(type -p javac | sed 's@/bin.*@@') && JT_HOME=$(pwd)/jtreg && PRODUCT_HOME=$(echo $(pwd)/build/*/images/j2sdk-image) The tests are run as follows: LANG=C make -k -C test \ JT_HOME=${JT_HOME} \ JT_JAVA=${JT_JAVA} \ PRODUCT_HOME=${PRODUCT_HOME} all LANG=C ${JT_HOME}/linux/bin/jtreg -a -v:fail,error \ -dir:$(pwd)/hotspot/test \ -k:\!ignore \ -jdk:${PRODUCT_HOME} \ :jdk The test results can be compared to these results. Finally, stop the virtual frame buffer and clean up: kill -9 `cat twm.pid` && kill -9 `cat Xvfb.pid` && rm -f Xvfb.out twm.out && rm -f Xvfb.pid twm.pid && if [ -n "$OLD_DISP" ]; then DISPLAY=$OLD_DISP fi Install the package with the following commands as the root user: find build/*/images/j2sdk-image -iname \*.jar -exec chmod a+r {} \; && chmod a+r build/*/images/j2sdk-image/lib/ct.sym && find build/*/images/j2sdk-image -iname \*.diz -delete && find build/*/images/j2sdk-image -iname \*.debuginfo -delete && cp -R build/*/images/j2sdk-image /opt/OpenJDK-&openjdk-version; && chown -R root:root /opt/OpenJDK-&openjdk-version; There are now two OpenJDK SDKs installed in /opt. You should decide on which one you would like to use as the default. Normally, you would opt for the just installed OpenJDK. If so, do the following as the root user: ln -v -nsf OpenJDK-&openjdk-version; /opt/jdk If desired, you may install a .desktop file corresponding to an entry in a desktop menu for policytool. First, you need to obtain an icon from : tar -xf ../icedtea-web-&icedtea-web-version;.tar.gz \ icedtea-web-&icedtea-web-version;/javaws.png \ --strip-components=1 Now, as root user: mkdir -pv /usr/share/applications && cat > /usr/share/applications/openjdk-8-policytool.desktop << "EOF" && [Desktop Entry] Name=OpenJDK Java Policy Tool Name[pt_BR]=OpenJDK Java - Ferramenta de Política Comment=OpenJDK Java Policy Tool Comment[pt_BR]=OpenJDK Java - Ferramenta de Política Exec=/opt/jdk/bin/policytool Terminal=false Type=Application Icon=javaws Categories=Settings; EOF install -v -Dm0644 javaws.png /usr/share/pixmaps/javaws.png The choice of pt_BR is just an example. You can add any translation by adding lines corresponding to your locale, e.g. for fr_FR, Name[fr_FR]= and Comment[fr_FR]= with the appropriate text as values. sh configure...: the top level configure is a wrapper around the autotools one. It is not executable and must be run through sh. --with-boot-jdk: This switch provides the location of the temporary JDK. It is normally not needed if java is found in the PATH. --with-update-version: Currently, the build system does not include the update number in the version string. It has to be specified here. --with-build-number: Again, the build system does not include the build number in the version string. It has to be specified here too. --with-milestone: Used to customize the version string. --enable-unlimited-crypto: Because of limitations on the usage of cryptography in some countries, there is the possibility to limit the size of encryption keys and the use of some algorithms in a policy file. This switch allows to ship a policy file with no restriction. It is the responsability of the user to ensure proper adherence to the law. --with-zlib=system, --with-giflib=system: Allows to use the system libraries instead of the bundled ones. --with-jobs=N: Allows to set the number of jobs for make equal to N. The default is the result of a calculation involving the available memory and the number of processors. Note that even if you specify N=1, some parallelization may be used during the build. The SBU given above are with parallel jobs disabled, on a single processor, single core, virtual machine. --with-cacerts-file=...: Specifies where to find a cacerts file. Otherwise, an empty one is created. You can get it from an earlier version of the package, or using the script below to generate one. make DEBUG_BINARIES=true all: The build fails if DEBUG_BINARIES is not set to true. find ... -iname '*.jar' -exec chmod a+r {} \; and following line: Fix permission in some library files, in order to allow all users to access them. find ... -iname '*.diz' -delete: This command and the the next one remove redundant files. Normally, the JAVA environment has been configured after installing the binary version, and can be used with the just built package as well. Review in case you want to modify something. To test if the man pages are correctly installed, issue source /etc/profile and man java to display the respective man page. Use the following procedure to install the cacerts or to generate a new one if have been updated. First, if it is not already present, generate the mkcacerts script as the root user: cat > /opt/jdk/bin/mkcacerts << "EOF" #!/bin/sh # Simple script to extract x509 certificates and create a JRE cacerts file. function get_args() { if test -z "${1}" ; then showhelp exit 1 fi while test -n "${1}" ; do case "${1}" in -f | --cafile) check_arg $1 $2 CAFILE="${2}" shift 2 ;; -d | --cadir) check_arg $1 $2 CADIR="${2}" shift 2 ;; -o | --outfile) check_arg $1 $2 OUTFILE="${2}" shift 2 ;; -k | --keytool) check_arg $1 $2 KEYTOOL="${2}" shift 2 ;; -s | --openssl) check_arg $1 $2 OPENSSL="${2}" shift 2 ;; -h | --help) showhelp exit 0 ;; *) showhelp exit 1 ;; esac done } function check_arg() { echo "${2}" | grep -v "^-" > /dev/null if [ -z "$?" -o ! -n "$2" ]; then echo "Error: $1 requires a valid argument." exit 1 fi } # The date binary is not reliable on 32bit systems for dates after 2038 function mydate() { local y=$( echo $1 | cut -d" " -f4 ) local M=$( echo $1 | cut -d" " -f1 ) local d=$( echo $1 | cut -d" " -f2 ) local m if [ ${d} -lt 10 ]; then d="0${d}"; fi case $M in Jan) m="01";; Feb) m="02";; Mar) m="03";; Apr) m="04";; May) m="05";; Jun) m="06";; Jul) m="07";; Aug) m="08";; Sep) m="09";; Oct) m="10";; Nov) m="11";; Dec) m="12";; esac certdate="${y}${m}${d}" } function showhelp() { echo "`basename ${0}` creates a valid cacerts file for use with IcedTea." echo "" echo " -f --cafile The path to a file containing PEM" echo " formated CA certificates. May not be" echo " used with -d/--cadir." echo "" echo " -d --cadir The path to a directory of PEM formatted" echo " CA certificates. May not be used with" echo " -f/--cafile." echo "" echo " -o --outfile The path to the output file." echo "" echo " -k --keytool The path to the java keytool utility." echo "" echo " -s --openssl The path to the openssl utility." echo "" echo " -h --help Show this help message and exit." echo "" echo "" } # Initialize empty variables so that the shell does not pollute the script CAFILE="" CADIR="" OUTFILE="" OPENSSL="" KEYTOOL="" certdate="" date="" today=$( date +%Y%m%d ) # Process command line arguments get_args ${@} # Handle common errors if test "${CAFILE}x" == "x" -a "${CADIR}x" == "x" ; then echo "ERROR! You must provide an x509 certificate store!" echo "\'$(basename ${0}) --help\' for more info." echo "" exit 1 fi if test "${CAFILE}x" != "x" -a "${CADIR}x" != "x" ; then echo "ERROR! You cannot provide two x509 certificate stores!" echo "\'$(basename ${0}) --help\' for more info." echo "" exit 1 fi if test "${KEYTOOL}x" == "x" ; then echo "ERROR! You must provide a valid keytool program!" echo "\'$(basename ${0}) --help\' for more info." echo "" exit 1 fi if test "${OPENSSL}x" == "x" ; then echo "ERROR! You must provide a valid path to openssl!" echo "\'$(basename ${0}) --help\' for more info." echo "" exit 1 fi if test "${OUTFILE}x" == "x" ; then echo "ERROR! You must provide a valid output file!" echo "\'$(basename ${0}) --help\' for more info." echo "" exit 1 fi # Get on with the work # If using a CAFILE, split it into individual files in a temp directory if test "${CAFILE}x" != "x" ; then TEMPDIR=`mktemp -d` CADIR="${TEMPDIR}" # Get a list of staring lines for each cert CERTLIST=`grep -n "^-----BEGIN" "${CAFILE}" | cut -d ":" -f 1` # Get a list of ending lines for each cert ENDCERTLIST=`grep -n "^-----END" "${CAFILE}" | cut -d ":" -f 1` # Start a loop for certbegin in `echo "${CERTLIST}"` ; do for certend in `echo "${ENDCERTLIST}"` ; do if test "${certend}" -gt "${certbegin}"; then break fi done sed -n "${certbegin},${certend}p" "${CAFILE}" > "${CADIR}/${certbegin}.pem" keyhash=`${OPENSSL} x509 -noout -in "${CADIR}/${certbegin}.pem" -hash` echo "Generated PEM file with hash: ${keyhash}." done fi # Write the output file for cert in `find "${CADIR}" -type f -name "*.pem" -o -name "*.crt"` do # Make sure the certificate date is valid... date=$( ${OPENSSL} x509 -enddate -in "${cert}" -noout | sed 's/^notAfter=//' ) mydate "${date}" if test "${certdate}" -lt "${today}" ; then echo "${cert} expired on ${certdate}! Skipping..." unset date certdate continue fi unset date certdate ls "${cert}" tempfile=`mktemp` certbegin=`grep -n "^-----BEGIN" "${cert}" | cut -d ":" -f 1` certend=`grep -n "^-----END" "${cert}" | cut -d ":" -f 1` sed -n "${certbegin},${certend}p" "${cert}" > "${tempfile}" echo yes | env LC_ALL=C "${KEYTOOL}" -import \ -alias `basename "${cert}"` \ -keystore "${OUTFILE}" \ -storepass 'changeit' \ -file "${tempfile}" rm "${tempfile}" done if test "${TEMPDIR}x" != "x" ; then rm -rf "${TEMPDIR}" fi exit 0 EOF chmod -c 0755 /opt/jdk/bin/mkcacerts Doing a very large copy/paste directly to a terminal may result in a corrupted file. Copying to an editor may overcome this issue. If you need to generate a cacerts file, and there is already one in /opt/jdk/jre/lib/security, it is better to make a backup. Then, you can create a new one, as the root user: /opt/jdk/bin/mkcacerts \ -d "/etc/ssl/certs/" \ -k "/opt/jdk/bin/keytool" \ -s "/usr/bin/openssl" \ -o "/opt/jdk/jre/lib/security/cacerts" Use the following commands to check if the cacerts file has been successfully installed: cd /opt/jdk bin/keytool -list -keystore jre/lib/security/cacerts At the prompt "Enter keystore password:", press the "Enter" key if there is no keystore password defined. If the cacerts file was installed correctly, you will see a list of the certificates with related information for each one. If not, you need to reinstall them. Installed Programs Installed Libraries Installed Directory appletviewer, extcheck, idlj, jar, jarsigner, java, javac, javadoc, javah, javap, java-rmi.cgi, jcmd, jconsole, jdb, jdeps, jhat, jinfo, jjs, jmap, jps, jrunscript, jsadebugd, jstack, jstat, jstatd, keytool, mkcacerts, native2ascii, orbd, pack200, policytool, rmic, rmid, rmiregistry, schemagen, serialver, servertool, tnameserv, unpack200, wsgen, wsimport, and xjc /opt/OpenJDK-&openjdk-version;/lib/*, and /opt/OpenJDK-&openjdk-version;/jre/lib/* /opt/OpenJDK-&openjdk-version; Short Descriptions appletviewer allows to run applets outside of a web browser. appletviewer extcheck checks a specified jar file for title and version conflicts with any extensions installed in the OpenJDK software. extcheck idlj generates Java bindings from a given IDL file. idlj jar combines multiple files into a single jar archive. jar jarsigner signs jar files and verifies the signatures and integrity of a signed jar file. jarsigner java launches a Java application by starting a Java runtime environment, loading a specified class and invoking its main method. java javac reads class and interface definitions, written in the Java programming language, and compiles them into bytecode class files. javac javadoc parses the declarations and documentation comments in a set of Java source files and produces a corresponding set of HTML pages describing the classes, interfaces, constructors, methods, and fields. javadoc javah generates C header and source files that are needed to implement native methods. javah javap disassembles a Java class file. javap java-rmi.cgi is the Java RMI client. java-rmi.cgi jcmd is a utility to send diagnostic command requests to a running Java Virtual Machine. jcmd jconsole is a graphical console tool to monitor and manage both local and remote Java applications and virtual machines. jconsole jdb is a simple command-line debugger for Java classes. jdb jdeps shows the package-level or class-level dependencies of Java class files. jdeps jhat parses a java heap dump file and allows viewing it in a web browser. jhat jinfo prints Java configuration information for a given Java process, core file, or a remote debug server. jinfo jjs is a command-line tool used to invoke the Nashorn engine. It can be used to interpret one or several script files, or to run an interactive shell. jjs jmap prints shared object memory maps or heap memory details of a given process, core file, or a remote debug server. jmap jps lists the instrumented JVMs on the target system. jps jrunscript is a command line script shell. jrunscript jsadebugd attaches to a Java process or core file and acts as a debug server. jsadebugd jstack prints Java stack traces of Java threads for a given Java process, core file, or a remote debug server. jstack jstat displays performance statistics for an instrumented JVM. jstat jstatd is an RMI server application that monitors for the creation and termination of instrumented JVMs. jstatd keytool is a key and certificate management utility. keytool mkcacerts is a simple script to extract x509 certificates and create a JRE cacerts file using keytool. mkcacerts native2ascii converts files that contain non-supported character encoding into files containing Latin-1 or Unicode-encoded characters. native2ascii orbd is used to enable clients to transparently locate and invoke persistent objects on servers in the CORBA environment. orbd pack200 is a Java application that transforms a jar file into a compressed pack200 file using the Java gzip compressor. pack200 policytool creates and manages a policy file graphically. policytool rmic generates stub and skeleton class files for remote objects from the names of compiled Java classes that contain remote object implementations. rmic rmid starts the activation system daemon. rmid rmiregistry creates and starts a remote object registry on the specified port on the current host. rmiregistry schemagen is a Java XML binding schema generator. schemagen serialver returns the serialVersionUID for one or more classes in a form suitable for copying into an evolving class. serialver servertool provides an ease-of-use interface for application programmers to register, unregister, startup and shutdown a server. servertool tnameserv starts the Java IDL name server. tnameserv unpack200 is a native implementation that transforms a packed file produced by pack200 into a jar file. unpack200 wsgen generates JAX-WS portable artifacts used in JAX-WS web services. wsgen wsimport generates JAX-WS portable artifacts. wsimport xjc is a Java XML binding compiler. xjc