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
8300111: Add rpath for common lib locations for jpackageapplauncher #11922
Conversation
Hi @davidgiga1993, welcome to this OpenJDK project and thanks for contributing! We do not recognize you as Contributor and need to ensure you have signed the Oracle Contributor Agreement (OCA). If you have not signed the OCA, please follow the instructions. Please fill in your GitHub username in the "Username" field of the application. Once you have signed the OCA, please let us know by writing If you already are an OpenJDK Author, Committer or Reviewer, please click here to open a new issue so that we can record that fact. Please use "Add GitHub user davidgiga1993" as summary for the issue. If you are contributing this work on behalf of your employer and your employer has signed the OCA, please let us know by writing |
To avoid this situation, create a new branch for your changes and reset the
Then proceed to create a new pull request with |
@davidgiga1993 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. |
What additional paths except "@executable_path/../Frameworks/" your application requires? If you just need @executable_path/../Frameworks/, then I think we should just add this to rpath permanently, instead of using -headerpad_max_install_names and install_name_tool. "Frameworks" and "PlugIns" are two standard folders to keep additional dynamic libraries, so I think we need to add both of them and do not use -headerpad_max_install_names. |
For my specific use case it would just be Frameworks. But I agree that adding both of them would be an option as well which should cover most/all use cases. I've adjusted the pr |
/signed |
You are already a known contributor! |
Looks good. You will need to file a JBS issue for this. |
@davidgiga1993 Please do not rebase or force-push to an active PR as it invalidates existing review comments. Note for future reference, the bots always squash all changes into a single commit automatically as part of the integration. See OpenJDK Developers’ Guide for more information. |
Since I'm not a member of any JDK project, I've used https://bugreport.java.com/, thus the ID starts with a 9. Is that fine or should I wait until this gets transferred to an |
Hi David, I updated the title of the JBS bug issue to match this PR (matching titles is a requirement, and the PR had a more descriptive title). The change itself look sane to me, but I'd like for @alexeysemenyukoracle to have a look at it as well. Also, if you ever is going to want to contribute additional PRs to OpenJDK, please see the bot's advice above. Otherwise you are entering a world of pain. /reviewers 2 |
Thanks for your feedback! |
|
@davidgiga1993 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 222 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 (@magicus, @alexeysemenyukoracle, @sashamatveev) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
It might even be missing from the contribution guide. Updating and expanding it is an ever ongoing project. checking It says: "The recommendation is to always create a new branch for any change you intend to implement. By doing that you can easily work on many different changes in parallel in the same code repository." The recommendation is correct, but should be worded more definitely: Things will break if you do not create a branch. I'll propose an update to the guide. Thanks for your assistance in making OpenJDk more approachable for new developers. |
Looks good. |
@davidgiga1993 Do you have JBS account, so https://bugs.openjdk.org/browse/JDK-8300111 can be assign to you? |
@sashamatveev No since this is my first contribution (I assume) the account creation/password reset doesn't work. Thus I don't have one :) |
The JBS assignment is not important. |
/integrate |
@davidgiga1993 |
/sponsor |
@alexeysemenyukoracle @davidgiga1993 Unable to acquire the integration lock; aborting sponsored integration. The error has been logged and will be investigated. |
Something is causing high contention in the bot, it's under investigation. In the meantime, all you can do is retry this /sponsor command until it goes through. |
/sponsor |
Going to push as commit 937ba1c.
Your commit was automatically rebased without conflicts. |
@alexeysemenyukoracle @davidgiga1993 Pushed as commit 937ba1c. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
This patch adds the
-headerpad_max_install_names
linker argument to the build of thejpackageapplauncher
binary (osx only)Adding this argument allows the user to use the
install_name_tool
to add search paths for the dynamic linker to the launcher binary. This is required for certain use cases where a native library loads other dynamic native libraries viadlopen
.The change has been successfully tested on osx on aarch64:
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/11922/head:pull/11922
$ git checkout pull/11922
Update a local copy of the PR:
$ git checkout pull/11922
$ git pull https://git.openjdk.org/jdk pull/11922/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 11922
View PR using the GUI difftool:
$ git pr show -t 11922
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/11922.diff