JDK-8201524 : [AIX] Don't link libfontmanager against libawt_headless
- Type: Bug
- Component: client-libs
- Sub-Component: java.awt
- Affected Version: 11
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- OS: aix
- Submitted: 2018-04-13
- Updated: 2018-05-11
- Resolved: 2018-04-16
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 11 |
|---|
11 b13Fixed  |
Related Reports
|
Relates :
|
Description
This is a follow up change of JDK-8196516 which discovered that on AIX libfontmanager is always linked against libawt_headless at build time. If we are running in a headfull environemnt, libfontmanager will dynamically load libawt_xawt which is not good because libawt_headless and libawt_xawt define some common symbols. If we're running in a headless environment, libawt_headless may be loaded a second time (at least on Linux/Solaris) which isn't good either. Both of these scenarios haven't caused any problems on AIX yet, but I think it's good to cleanup the AIX implementation as well and don't link libfontmanager against libawt_headless anymore. In order to achieve this, we have to allow unresolved symbols during the linking of libfontmanager. This can be easily achieved by adding the additions linker flag "-Wl$(COMMA)-berok" through LDFLAGS_aix.