However, I don't know exactly from where your error comes, dl-lookup contains internal functions of the glibc C runtime library. I remind you that Java3D >= 1.6 has no native pipeline (I removed the native OpenGL pipeline several years ago, Java3D has used only the JOGL pipeline from this moment) and I don't see how it could come from any JogAmp API.
If I were you, I would check whether the problem comes from JSSC. I can build Java projects under Mageia Linux 7 using JogAmp APIs (JOAL, JOGL, GlueGen, ...) with both Maven and Gradle without such problems. I use both the build-in OpenJDK 8 JDK and AdoptOpenJDK 11.
Reminder: The latest version of Java3D is Java3D 1.7.0 and it doesn't use the same package names.
To be sure I understand: you mean that my java3d dependencies (1.6.2 and gluegen and jogl) are pure Java, and therefore this ld.so call comes from something else?
I had compiled a 1.7.0 version of Java3D, but I am having a hard time finding the dependencies on maven repositories, and also knowing which repos are official or not (because it seems like they generally live in personal forks).
Java3D is pure Java, JogAmp APIs aren't. If you really suspect a problem with JOGL or GlueGen, try to build something with them with Gradle without Java3D. I see JSSC in your dependencies and I'm 100% sure that it's not pure Java.
Please ask Phil to upload Java3D 1.7 on Maven Central.
Do you reproduce this problem with some builds provided by AdoptOpenJDK? I use OpenJDK 8 (provided by the distro) and OpenJDK 11 (provided by AdoptOpenJDK) under Mageia Linux and I don't have this problem.