-
Bug
-
Resolution: Fixed
-
P3
-
12
-
b12
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8238255 | 11.0.8-oracle | Magnus Ihse Bursie | P3 | Resolved | Fixed | b01 |
JDK-8225735 | 11.0.5 | Magnus Ihse Bursie | P3 | Resolved | Fixed | b01 |
There's a bunch of interrelated smelly code regarding static libraries on macosx.
I started by turning libfdlibm into a static library on macosx, as on all other platforms. It turned out that we don't have proper support for static libraries on macosx, so I fixed this too.
Secondly, I removed the libjli_static.a for macosx. There is no good reason to have it. It's probably just a left-over from the old Apple port to macosx. This in turn prompted some additional related cleanup in LauncherCommon.gmk.
I started by turning libfdlibm into a static library on macosx, as on all other platforms. It turned out that we don't have proper support for static libraries on macosx, so I fixed this too.
Secondly, I removed the libjli_static.a for macosx. There is no good reason to have it. It's probably just a left-over from the old Apple port to macosx. This in turn prompted some additional related cleanup in LauncherCommon.gmk.
- backported by
-
JDK-8225735 Clean up macosx static library handling
-
- Resolved
-
-
JDK-8238255 Clean up macosx static library handling
-
- Resolved
-
- relates to
-
JDK-8211136 [macosx] Some of our jtreg tests fail in macosx with error "dyld: Library not loaded: @rpath/libjli.dylib" randomly
-
- Closed
-