Skip to content
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

dlopen image not found #156

Closed
FranPrin opened this issue Jan 10, 2020 · 8 comments
Closed

dlopen image not found #156

FranPrin opened this issue Jan 10, 2020 · 8 comments

Comments

@FranPrin
Copy link

Using openjdk14 I get a "dlopen(jre/lib/jli/libjli.dylib): image not found" error which fails the launch of the jvm.

I think this is an error specifically for later jre's because when I look back at my jre 1.7.x it contains the file specified.

Any thoughts for solving this? Thanks

@SakiiCode
Copy link

SakiiCode commented Jan 14, 2020

I suggest using my fork of packr as it has up-to-date jre paths and compiled binaries for java 8-13, you can let me know if it doesn't work.

Java 14 hasn't even been released yet, but I hope it will be fine.

@FranPrin
Copy link
Author

FranPrin commented Feb 6, 2020

Thank you! I will give it a try

@karlsabo
Copy link
Member

karlsabo commented May 8, 2020

I forked the project as well, looks like a lot of us fixed the issue. I also applied other patches to make sure the executable works in the macOS hardened runtime on Catalina.

https://github.com/karlsabo/packr/releases

@Frotty
Copy link

Frotty commented May 15, 2020

@SakiiCode @karlsabo Hi, i have this error too, but I actually package a version 8 JDK.
It seems that the mac uses its system JRE instead of the packaged JRE when I run the executable from the "MacOS" folder. Is this intentional? Do I need to package it as .app to use packaged jre?

@karlsabo
Copy link
Member

karlsabo commented May 15, 2020

@Frotty No, it doesn't need to be in an app bundle. The executable and "jre" need to be in the same parent directory:

./
-your-executable
-config.json
-jre/
-some-assets/
-maybe-your-app.jar

Technically, it's the working directory that matters. However you launch "your-executable" it needs to find a directory called "jre" relative to its working directory. E.g., the code looks for ./jre.

Edit: Really it's the working directory

@Frotty
Copy link

Frotty commented May 15, 2020

My bad I misread the comment.

@nedtwigg
Copy link
Contributor

I have no relation to libgdx or karlsabo. I stepped through all the changes in karlsabo's fork, and there's a lot of great improvements to various things, and best of all public CI running on win/mac/linux. Packr is a great project, very happy to see an active fork with cross-platform CI.

@karlsabo
Copy link
Member

This issue has been resolved with recent merges. Thanks everyone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants