Hi there,
I have a Java project (https://github.com/johhnry/2I002_mini_projet) where I am using the Processing library (https://processing.org/) and jogl to display 3d shapes. It used to work back in april when I finished the project and now when I try to compile it (I am using eclipse), this is the output : WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by com.jogamp.common.os.NativeLibrary$3 (file:/home/josephhenry/Documents/eclipse_workspace/2I002_mini_projet/libraries/gluegen-rt.jar) to method java.lang.ClassLoader.findLibrary(java.lang.String) WARNING: Please consider reporting this to the maintainers of com.jogamp.common.os.NativeLibrary$3 WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release Inconsistency detected by ld.so: dl-lookup.c: 111: check_match: Assertion `version->filename == NULL || ! _dl_name_match_p (version->filename, map)' failed! These are the libraries that I added to the build path : I tried to download the latest libraries but it still doesn't work. Anyone have an idea? Thanks |
Administrator
|
On 12/17/19 12:10 PM, johhnry [via jogamp] wrote:
> Hi there, > Hi J.., the WARNING has been removed in our latest tip of the master branch. What remains might be: > Inconsistency detected by ld.so: dl-lookup.c: 111: check_match: Assertion > `version->filename == NULL || ! _dl_name_match_p (version->filename, map)' > failed! Looks like an assertion got hit within the native 'dlsym(..)' implementation: 'void *dlsym(void *handle, const char *symbol);' This might be related to using a pseudo symbol like RTLD_DEFAULT or RTLD_NEXT? Interesting. Which libc and Linux distribution are you using? Cheers, Sven > I have a Java project (https://github.com/johhnry/2I002_mini_projet) where I > am using the Processing library (https://processing.org/) and jogl to display > 3d shapes. > > It used to work back in april when I finished the project and now when I try > to compile it (I am using eclipse), this is the output : > > /WARNING: An illegal reflective access operation has occurred > WARNING: Illegal reflective access by com.jogamp.common.os.NativeLibrary$3 > (file:/home/josephhenry/Documents/eclipse_workspace/2I002_mini_projet/libraries/gluegen-rt.jar) > to method java.lang.ClassLoader.findLibrary(java.lang.String) > WARNING: Please consider reporting this to the maintainers of > com.jogamp.common.os.NativeLibrary$3 > WARNING: Use --illegal-access=warn to enable warnings of further illegal > reflective access operations > WARNING: All illegal access operations will be denied in a future release > Inconsistency detected by ld.so: dl-lookup.c: 111: check_match: Assertion > `version->filename == NULL || ! _dl_name_match_p (version->filename, map)' > failed! > / > > These are the libraries that I added to the build path : > > > > I tried to download the latest libraries but it still doesn't work. > > Anyone have an idea? > > Thanks |
Hi,
Thanks for your answer. I am currently using Pop!_OS (Linux pop-os 5.3.0-7625-generic), which is very close to Ubuntu. My version of glibc is Ubuntu GLIBC 2.30-0ubuntu2. I am going to try with the latest release from the master branch. Have a great day Joseph |
This post was updated on .
In reply to this post by johhnry
This has shown up before. See This thread
Seems to be isolated to recent builds of openjdk >10, from about midyear 2019. Affects jogl, as well as lwjgl2 (not encountered on lwgl3 yet) (I know that lwjgl is a different, parallel project with a different design philosophy. This data point makes it seem that the issue is not _directly_ jogl's fault) The error has been seen on: - Ubuntu derivatives - Arch Reviewing the package definition file shows that Arch, at least, is *EDIT: they're building from source, monkeying with the build options a bit. * Interestingly, I have not seen this reproduced with adoptopenjdk binaries, even on the same system/glibc. I wonder if this indicates that the openjdk codebase staticly links it's own glibc? |
Hi,
Thanks for the information, so if I really need to compile it, I can use a version of openjdk < 10 is that right? Joseph |
Administrator
|
Please use AdoptOpenJDK to work around this problem.
Julien Gouesse | Personal blog | Website
|
Free forum by Nabble | Edit this page |