Compile Windows jdk8+ with VS2022, move jdk17 x,p,zlinux to gcc 11.2 #18135
Conversation
alinux can't move to 11.2 due to eclipse-openj9#15390 Signed-off-by: Peter Shipton <[email protected]>
|
Question for @TobiAjila: Do we still need the |
There was a problem hiding this comment.
I'm satisfied by what I see at https://openj9-jenkins.osuosl.org/job/Pipeline-Build-Test-Personal/431.
as of today we no longer need it |
Ok, I'll create a pull request to remove those redundant specifications. |
|
Doc issue eclipse-openj9/openj9-docs#1168 |
See eclipse-openj9/openj9#18135 Signed-off-by: Peter Shipton <[email protected]>
Affects jdk8, jdk11, jdk17, although jdk17 alinux doesn't change. OpenJ9 jdk8, jdk11 xlinux hasn't switched to gcc 11.2 yet since the container used to compile doesn't yet contain this compiler. See eclipse-openj9/openj9#18135 eclipse-openj9/openj9#18408 Signed-off-by: Peter Shipton <[email protected]>
Affects jdk8, jdk11, jdk17, although jdk17 alinux doesn't change. OpenJ9 jdk8, jdk11 xlinux hasn't switched to gcc 11.2 yet since the container used to compile doesn't yet contain this compiler. See eclipse-openj9/openj9#18135 eclipse-openj9/openj9#18408 Signed-off-by: Peter Shipton <[email protected]>
alinux can't move to 11.2 due to #15390
For testing see the following. Ignore the linux builds on jdk8,11. This build was done with a different commit that modified all versions.
https://openj9-jenkins.osuosl.org/job/Pipeline-Build-Test-Personal/431/
jdk11 will move once we have a new OpenJDK level that compiles, expected in a future 11.0.21 update.
jdk8 will move once Adoptium provides a xlinux centos6 container with the required gcc version, although we can consider moving other platforms earlier. They all work.