-
Notifications
You must be signed in to change notification settings - Fork 220
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.
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
libfreetype.dylib is incorrectly packaged #6
Comments
Thank you for reporting this issue to us. The Corretto engineering team is looking at it and we will post updates here. |
Clean install on OS X, trying to run jmeter trigger this which I think is the same issue:
|
The libfontmanager in Corretto is linked to the libfreetype in X11 and breaks when X11 is not installed. The libfreetype is actually bundled with Corretto so relinking libfontmanager to the bundled libfreetype will fix this issue. We plan to address this in the next release. Until then, here’s a simple workaround on your own mac:
|
FWIW, I hit this from Swing code --
... and @ziyiluo's workaround worked. |
Any update on below error... java -version
ERROR
|
Hi @krishnamanchikalapudi , have you tried the workaround in my previous comment? |
@ziyiluo thank you!... Solution worked for MAC 10.14.3 |
This issue is fixed in the new Corretto preview release (1.8.0_192-amazon-corretto-preview2-b12). Change log of this release is now available. You can find the builds in the Corretto download page. Please let us know if you have any further questions. We appreciate your report! |
@ziyiluo You saved my day :) |
Describe the bug
When using AWT fonts, initializing
sun.font.CFontManager
fails with the following error:Looking in
/Library/Java/JavaVirtualMachines/amazon-corretto-8.jdk/Contents/Home/jre/lib
shows there's a misnamedlibfreetype.dylib.6
(should belibfreetype.6.dylib
), but even fixing that name doesn't allow AWT to initialize successfully because it's explicitly looking in/opt/X11/lib
.This appears to be quite similar to adoptium/temurin-build#202, but not quite the same. With AdoptOpenJDK, the issue can be fixed simply by renaming
libfreetype.dylib.6
tolibfreetype.6.dylib
while leaving the library injre/lib
.To Reproduce
Expected behavior
CFontManager
initializes successfully and AWT fonts work.Platform information
Additional context
I got this failure from the (defunct, but still generally functional) JCaptcha library, but it's not unique to JCaptcha (as shown by my simple reproduction, which uses nothing but standard Java).
The text was updated successfully, but these errors were encountered: