Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8273201 | jfx11.0.13 | Johan Vos | P3 | Resolved | Fixed |
libjavafx_iio.so contains a copy of libjpeg7 (soon to be libjpeg9)
and since we are exporting all the libjpeg symbols these may
clash with some other libjpeg on a system.
We should restrict the export to just the JNI interfaces as the
JDK does in similar situations.
See https://bugs.openjdk.java.net/browse/JDK-8200178 and
http://mail.openjdk.java.net/pipermail/build-dev/2018-March/021306.html
The gist of the fix there is to add a JNIEXPORT directive to the declarations of the JNI functions in the JDK's own source files
which are compiled into the library and to update the makefile
so that all symbols not explicitly exported are internal.
and since we are exporting all the libjpeg symbols these may
clash with some other libjpeg on a system.
We should restrict the export to just the JNI interfaces as the
JDK does in similar situations.
See https://bugs.openjdk.java.net/browse/JDK-8200178 and
http://mail.openjdk.java.net/pipermail/build-dev/2018-March/021306.html
The gist of the fix there is to add a JNIEXPORT directive to the declarations of the JNI functions in the JDK's own source files
which are compiled into the library and to update the makefile
so that all symbols not explicitly exported are internal.
- backported by
-
JDK-8273201 Restrict export of libjpeg symbols from libjavafx_iio.so
- Resolved
- relates to
-
JDK-8203884 Update libjpeg to version 9c
- Resolved
- links to
-
Commit openjdk/jfx11u/319d2f09
-
Commit openjdk/jfx/ed5cfe72
-
Review openjdk/jfx11u/51
-
Review openjdk/jfx/442
(1 links to)