JDK-8275703: System.loadLibrary fails on Big Sur for libraries hidden from filesystem #6127
@mlchung 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:
At the time when this comment was updated there had been 15 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.
➡️ To integrate this PR with the above commit message to the
There was a problem hiding this comment.
I?m curious about this issue.
I never load system libraries directly. I load my own libraries (that support JNI entry points) and the system loader loads the necessary system frameworks that they were linked against.
What?s different in this case that motivates loading system libraries directly from Java?
Panama would be the right place to provide the support of loading system libraries directly from Java and enhance the interconnection between JVM and native code.
The bug report is an example showing that developers want to load a system library for their native code to use. It's not surprise that they use
Going to push as commit 309acbf.
Your commit was automatically rebased without conflicts.