-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
8308544: Fix compilation regression from JDK-8306983 on musl libc #14080
Conversation
👋 Welcome back jankratochvil! A progress list of the required criteria for merging this PR into |
@jankratochvil The following label will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command. |
Webrevs
|
Looks good to me - but @bplb, could you please review? Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks all right.
@jankratochvil This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 28 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@bplb, @tstuefe) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
/integrate |
@jankratochvil |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay. I had a slightly different fix, but I'll close that as duplicate: #14097
/sponsor |
@tstuefe The PR has been updated since the change author (@jankratochvil) issued the |
@jankratochvil can you please repeat the integrate? Thanks. |
I did not want to as I have realized my openjdk commits go with wrong e-mail address (not |
Is this really important? Build fixes are time critical. Let's just hope this skara bug gets resolved quickly. |
/integrate |
It is not important. I rather have not found much urgent the Alpine Linux fix. So I have done the /integrate. |
@jankratochvil |
My e-mail address ticket https://bugs.openjdk.org/browse/SKARA-1915 is now even already resolved. |
@jankratochvil Great, thanks. /sponsor |
Going to push as commit c0c4d77.
Your commit was automatically rebased without conflicts. |
@tstuefe @jankratochvil Pushed as commit c0c4d77. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Since JDK-8306983 compilation on Alpine Linux using musl libc:
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/14080/head:pull/14080
$ git checkout pull/14080
Update a local copy of the PR:
$ git checkout pull/14080
$ git pull https://git.openjdk.org/jdk.git pull/14080/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 14080
View PR using the GUI difftool:
$ git pr show -t 14080
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/14080.diff
Webrev
Link to Webrev Comment