Skip to content
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

Use gcc7 on all Linux builds (HotSpot-JDK8 specifically!) #1215

Merged
merged 2 commits into from
Nov 2, 2020

Conversation

sxa
Copy link
Member

@sxa sxa commented Aug 13, 2019

Signed-off-by: Stewart Addison [email protected]

Signed-off-by: Stewart Addison <[email protected]>
@adoptopenjdk-github-bot
Copy link
Contributor

Can one of the admins verify this patch?

@karianna karianna added the enhancement Issues that enhance the code or documentation of the repo in any way label Aug 13, 2019
@karianna
Copy link
Contributor

@sxa555 Did you want to take this out of the draft?

@jerboaa
Copy link
Contributor

jerboaa commented Feb 12, 2020

Considering adoptium/infrastructure#1133 we probably should something like this get in.

@sxa
Copy link
Member Author

sxa commented Feb 12, 2020

@jerboaa Slightly curious about this as the existing logic in there does appear to suggest that any version of JDK11+ should already be building with the later GCC. Only JDK8/HotSpot should still be on the earlier GCC.

@karianna Whether this wants to come out of draft depends on whether we want to change all HotSpot JDK releases to run on GCC7. If we decide "yes" then I'm good to take it out of draft

@jerboaa
Copy link
Contributor

jerboaa commented Feb 12, 2020

@sxa555 Right. I was experiencing the GCC version issue on a non-adopt-build-script build. It didn't have the devtoolset-7 magic setting. It does now.

@karianna karianna added this to the February 2020 milestone Feb 17, 2020
@sxa sxa changed the title DONOTMERGE: Use gcc7 on all Linux builds DONOTMERGE: Use gcc7 on all Linux builds (HotSpot-JDK8 specifically!) Mar 3, 2020
@sxa sxa modified the milestones: February 2020, March 2020 Mar 3, 2020
@karianna karianna modified the milestones: March 2020, April 2020 Apr 2, 2020
@karianna karianna modified the milestones: April 2020, May 2020 May 4, 2020
@karianna karianna modified the milestones: May 2020, June 2020 Jun 1, 2020
@karianna karianna modified the milestones: June 2020, July 2020 Jul 1, 2020
@karianna karianna modified the milestones: July 2020, August 2020 Aug 3, 2020
@karianna karianna modified the milestones: August 2020, September 2020 Sep 1, 2020
@sxa sxa marked this pull request as ready for review October 29, 2020 13:20
@sxa
Copy link
Member Author

sxa commented Oct 29, 2020

We should expedite a decion on this particularly since https://openjdk.java.net/groups/build/doc/building.html says The minimum accepted version of gcc is 5.0 and we're currently still using 4.8 for some of our HotSpot builds

@sxa sxa changed the title DONOTMERGE: Use gcc7 on all Linux builds (HotSpot-JDK8 specifically!) Use gcc7 on all Linux builds (HotSpot-JDK8 specifically!) Oct 29, 2020
@sxa
Copy link
Member Author

sxa commented Oct 29, 2020

Old conflicts resolveld (We've switched to GCC7.5 from 7.3 since I originally made this PR) and running through JDK8 at https://ci.adoptopenjdk.net/view/Tooling/job/VagrantPlaybookCheck/919 although the automatic PR tests should pick up any issues

@sxa
Copy link
Member Author

sxa commented Oct 29, 2020

Note to reviewers - only the conditional at the start has been removed - the other changes are purely indentation of the stuff that was inside the conditional.

Copy link
Contributor

@karianna karianna left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@adoptopenjdk-github-bot
Copy link
Contributor

🟢 PR TESTER RESULT 🟢

✅ All pipelines passed! ✅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Issues that enhance the code or documentation of the repo in any way
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants