JDK-8071710 : [solaris] libfontmanager should be linked against headless awt library
  • Type: Bug
  • Component: client-libs
  • Sub-Component: 2d
  • Affected Version: 8u60,9
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: solaris
  • CPU: generic
  • Submitted: 2015-01-27
  • Updated: 2018-03-14
  • Resolved: 2015-01-29
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.
JDK 8 JDK 9
8u60Fixed 9 b52Fixed
Related Reports
Relates :  
Relates :  
Relates :  
Description
Since JDK on Solaris has always had a separate "headless" AWT library which does not load X11
libraries, the fontmanager library has been linked against that library to make sure it has no runtime
dependency on X11 libraries that it does not need. This is important to running in an environment
where X11 is not needed or perhaps not installed - as is frequently the case with server apps
that make use of Java 2D.

However the following JDK 8 b25 fix for jigsaw/modularisation 
unintentionally caused libfontmanager to link against the headful AWT
because xawt was now being found on the link path
https://bugs.openjdk.java.net/browse/JDK-7110002

Although that fix pre-dated the new build system the bug was propagated there
most likely trying to preserve exactly what happened before the new build.

So the problem is there in JDK 8 updates and still today in JDK 9.

The closed source t2k part of the font library also has the same issue.

-phil. 
Comments
After this fix some (not all) Solaris builds fail. It turns out the dependency checking relies on the order of declarations in the makefile. https://bugs.openjdk.java.net/browse/JDK-8072116 is submitted to fix that.
02-02-2015