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.

Sign up for GitHub

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

Jump to bottom

Failure loading frameworks on macOS 11 #1215

Closed
dkocher opened this issue Jun 28, 2020 · 0 comments · Fixed by #1216
Closed

Failure loading frameworks on macOS 11 #1215

dkocher opened this issue Jun 28, 2020 · 0 comments · Fixed by #1216

Comments

@dkocher
Copy link
Contributor

dkocher commented Jun 28, 2020

See the following note in the macOS 11 beta release notes

New in macOS Big Sur 11 beta, the system ships with a built-in dynamic linker cache of all system-provided libraries. As part of this change, copies of dynamic libraries are no longer present on the filesystem. Code that attempts to check for dynamic library presence by looking for a file at a path or enumerating a directory will fail. Instead, check for library presence by attempting to dlopen() the path, which will correctly check for the library in the cache. (62986286)

Thus loading frameworks using Native.loadLibrary("Foundation") no longer works because the code has checks using java.io.File.exists to locate the framework.
dkocher added a commit to iterate-ch/jna that referenced this issue Jun 28, 2020
@dkocher
Try all frameworks paths regardless of file exist check.
70e8cda 
> New in macOS Big Sur 11 beta, the system ships with a built-in dynamic linker cache of all system-provided libraries. As part of this change, copies of dynamic libraries are no longer present on the filesystem. Code that attempts to check for dynamic library presence by looking for a file at a path or enumerating a directory will fail. Instead, check for library presence by attempting to dlopen() the path, which will correctly check for the library in the cache. (62986286)

Fix java-native-access#1215.

Signed-off-by: David Kocher <dkocher@iterate.ch>
@dkocher dkocher mentioned this issue Jun 28, 2020
Merged
dkocher added a commit to iterate-ch/jna that referenced this issue Jun 30, 2020
@dkocher
Try all frameworks paths regardless of file exist check.
3452531 
> New in macOS Big Sur 11 beta, the system ships with a built-in dynamic linker cache of all system-provided libraries. As part of this change, copies of dynamic libraries are no longer present on the filesystem. Code that attempts to check for dynamic library presence by looking for a file at a path or enumerating a directory will fail. Instead, check for library presence by attempting to dlopen() the path, which will correctly check for the library in the cache. (62986286)

Fix java-native-access#1215.

Signed-off-by: David Kocher <dkocher@iterate.ch>
dbwiddis pushed a commit to dbwiddis/jna that referenced this issue Jul 15, 2020
@dkocher @dbwiddis
Try all frameworks paths regardless of file exist check.
b3fd65d 
> New in macOS Big Sur 11 beta, the system ships with a built-in dynamic linker cache of all system-provided libraries. As part of this change, copies of dynamic libraries are no longer present on the filesystem. Code that attempts to check for dynamic library presence by looking for a file at a path or enumerating a directory will fail. Instead, check for library presence by attempting to dlopen() the path, which will correctly check for the library in the cache. (62986286)

Fix java-native-access#1215.

Signed-off-by: David Kocher <dkocher@iterate.ch>
facebook-github-bot pushed a commit to facebook/buck that referenced this issue Sep 29, 2020
@milend @facebook-github-bot
Update packages for compatibility with macOS 11 Big Sur
a2912b9 
Summary:
# Context

macOS 11 adopts the [dyld shared cache](https://iphonedevwiki.net/index.php/Dyld_shared_cache) which means that the system libraries do not actually exist on the filesystem. This broke JNA and it was fixed in late June 2020 ([issue#1215](java-native-access/jna#1215)).

# Changes

Because we have other third-party JARs which depend on JNA, we had to update those. In summary, we updated all of the following modules:

- JNA
- nailgun
- NuProcess
- oshi
- Java Obj-C Bridge

Reviewed By: blackm00n

fbshipit-source-id: f29c775912ac3a84ec5615f6999b7bccf212ead7
@turesheim turesheim mentioned this issue Nov 15, 2020
Closed
jasonnam added a commit to jasonnam/buck that referenced this issue Jan 10, 2021
@jasonnam
Update JNA to resolve framework loading issue on Big Sur
5d49d58 
java-native-access/jna#1215
@jasonnam jasonnam mentioned this issue Jan 10, 2021
Merged
rajyengi pushed a commit to facebook/buck that referenced this issue Jan 12, 2021
@jasonnam
Update dependencies for Big Sur (#2580)
2f85dfc 
* Update JNA to resolve framework loading issue on Big Sur

java-native-access/jna#1215

* Remove workaround initializing JNA early

java-native-access/jna#652

This issue was resolved and property SIZE does not exist with JNA version 5.6.0.

* Update NuProcess to 2.0.1 for compatibility with JNA

* Build NuProcess with openjdk version "1.8.0_275"

jetty/jetty.project#3244

* Cherry pick a2912b9

a2912b9
Bencodes pushed a commit to lyft/buck that referenced this issue Feb 10, 2021
@jasonnam @Bencodes
Update dependencies for Big Sur (facebook#2580)
e38a850 
* Update JNA to resolve framework loading issue on Big Sur

java-native-access/jna#1215

* Remove workaround initializing JNA early

java-native-access/jna#652

This issue was resolved and property SIZE does not exist with JNA version 5.6.0.

* Update NuProcess to 2.0.1 for compatibility with JNA

* Build NuProcess with openjdk version "1.8.0_275"

jetty/jetty.project#3244

* Cherry pick a2912b9

facebook@a2912b9
@farion farion mentioned this issue Apr 9, 2021
Closed
shepting pushed a commit to airbnb/buck that referenced this issue Nov 11, 2021
@jasonnam @shepting
Update dependencies for Big Sur (facebook#2580)
a541e93 
* Update JNA to resolve framework loading issue on Big Sur

java-native-access/jna#1215

* Remove workaround initializing JNA early

java-native-access/jna#652

This issue was resolved and property SIZE does not exist with JNA version 5.6.0.

* Update NuProcess to 2.0.1 for compatibility with JNA

* Build NuProcess with openjdk version "1.8.0_275"

jetty/jetty.project#3244

* Cherry pick a2912b9

facebook@a2912b9
shepting pushed a commit to airbnb/buck that referenced this issue Nov 11, 2021
@jasonnam @shepting
Update dependencies for Big Sur (facebook#2580)
28b5ea0 
* Update JNA to resolve framework loading issue on Big Sur

java-native-access/jna#1215

* Remove workaround initializing JNA early

java-native-access/jna#652

This issue was resolved and property SIZE does not exist with JNA version 5.6.0.

* Update NuProcess to 2.0.1 for compatibility with JNA

* Build NuProcess with openjdk version "1.8.0_275"

jetty/jetty.project#3244

* Cherry pick a2912b9

facebook@a2912b9
shepting pushed a commit to airbnb/buck that referenced this issue Nov 12, 2021
@jasonnam @shepting
Update dependencies for Big Sur (facebook#2580)
36ce5a1 
* Update JNA to resolve framework loading issue on Big Sur

java-native-access/jna#1215

* Remove workaround initializing JNA early

java-native-access/jna#652

This issue was resolved and property SIZE does not exist with JNA version 5.6.0.

* Update NuProcess to 2.0.1 for compatibility with JNA

* Build NuProcess with openjdk version "1.8.0_275"

jetty/jetty.project#3244

* Cherry pick a2912b9

facebook@a2912b9
@thurka thurka mentioned this issue Dec 16, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Try all frameworks paths regardless of file exist check. iterate-ch/jna
1 participant
@dkocher