JOGL works on JDK 17 but not on JDK 18

What the topic says. I have a demo program that I am running on Linux Mint 19. JDK 17 works fine, JDK 18 gives:

FAIL: java.lang.UnsatisfiedLinkError: /tmp/jogamp_0000/file_cache/jln5860679930746491415/jln3657902754341439289/natives/linux-amd64/libnativewindow_awt.so: /home/stefan/dev/jdk-18/lib/libjawt.so: version `SUNWprivate_1.1' not found (required by /tmp/jogamp_0000/file_cache/jln5860679930746491415/jln3657902754341439289/natives/linux-amd64/libnativewindow_awt.so)

What to do?

Also... is the last released version really from 2015? Is anything newer available?

PS: I'm making an image recognizer in Java and I want to throw in some GPU calculations/renderings, that's why JOGL interests me.

Many greetings,
Stefan
Gaz.AI

Hi Stefan,

The last version is from 2021 and number is 2.4-rc4.

I encountered something similar to you on Ubuntu 18 and haven't seen it again on Ubuntu 20 (but maybe my evaluation was not reliable and the problem came from varying JDK version as you mention).

Hello

I had the same problem:
https://forum.jogamp.org/Oracle-Java-13-Linux-version-SUNWprivate-1-1-not-found-td4040172.html

You're already using Temurin, I don't reproduce your problem :s

This problem is a bit mysterious but seams to be out of JOGL : it occurs on LWJGL, SWT, and other software.

The JDK has references to this keyword but not as java nor native source file.

The SWT discussion has links that may be instructive to fix the problem :
https://docs.oracle.com/cd/E23824_01/html/821-1602/solarisabi-6.html
https://bugzilla.redhat.com/show_bug.cgi?id=1590796
https://stackoverflow.com/questions/5790085/linux-library-problem

Hey Martin, thanks for your input... but why exactly are we talking about JDK 13?

Actually I might ask the JVM devs if they have any idea why JOGL breaks on JDK 18. It did work before after all...

The problem you reported already occured with Java 13 and as far as I know, I succeed in running JOGL with Java 18 under GNU Linux, I don't think your problem has something to do with Java 18.

OK I see what you're saying. But on my machine, the exact same program runs without error with JDK 17 but produces the error on JDK 18. I'd say that pretty much means it's gotta be a change in the JDK, no?

There is this Oracle doc mentioning SUNWprivate_1.1, the .1 part of the name being possibly a datastructure or library versioning. I agree that discussing this with OpenJDK team is a good idea. Let us know what they suggest!