-
-
Notifications
You must be signed in to change notification settings - Fork 249
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create our own openjdk7 builds for use as boot JDKs #1732
Comments
I'm not sure we'll be able to build these ourselves for all of the platforms. I'm comfortable with standardizing on Zulu for this. Azul is a supporter/sponsor and they are the lead maintainers for 7. |
I'm currently in the process of build JDK7 on CentOS6. I've tracked the process I've gone through , and will update as I go.
Other help: https://hg.openjdk.java.net/jdk7u/jdk7u/raw-file/tip/README-builds.html Current error:
|
@karianna They don't do AIX, and as per original comment I'm struggling to get any Java 7 that works on the AIX 7.1SP5 machine I'm trying to build the OpenJ9 JDK8 on at the moment. For most of the bulid machines (earlier distributions) we're bootstrapping with the 7 that comes with them. We could certainly set up the playbooks with a zulu again (although we removed most of the references to the zulu repos) for the later distros which aren't supplied with a JDK7 from their repositories as an alternative |
Given the problems Will has been having I'm good with using zulu on the newer Linux distributions although I believe it would be useful to be able to reproduce building our own on AIX |
In fact zulu isn't available on any Linux architectures other than x64, so arm32, aarch64, s390x, ppc64le can't be sourced that way on modern distributions. |
It looks like Zulu is now available for other Linux architectures (I've seen BellSoft version is also available for |
Java 8 can be built using JDK8 as the boot JDK but in general the preferred approach is to use the version one level back i.e. Java7.
This leaves us with the problem of sourceing a boot JDK, but for newer operating systems and distributions, a version of openjdk7 is not easily available from the distribution's repositories (e.g. RHEL8, Ubuntu 20.04, Debian10).
Since we try to encourae (or at least make it easy for) people to use our scripts to build their own JDK by providing the
openjdk-infrastructure
ansible scripts, docker files, and the scripts inopenjdk-build
we should also make it easy to source JDK7 on the operating systems/distrubutions that people are using.To this end, we should look at building openjdk7. Even if it is not something we're ever going to properly support it would be useful to have it available for use in the playbooks when the distribution does not provide a JDK7. The alternate option would be to source it elsewhere e.g. [azul's Zulu](https://www.azul.com/downloads/zulu-community/?version=java-7-lts&package=jdk. Neither bellsoft Liberica nor SAPMachine have JDK7 available.
This was triggered by discovering that on the AIX build machines we seem to have a version of openjdk7 used for bootstrapping JDK8 and the new machine I was setting up for build appeared not to have that installed via the playbooks (from discussions it appears it may have been built by us from source at some point). The machine does have a version of IBM Java 7 but that did not appear suitable for bootstrapping openjdk8.
The text was updated successfully, but these errors were encountered: