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

archive extraction bug on Mac #356

Closed
tony-- opened this issue Dec 4, 2018 · 2 comments
Closed

archive extraction bug on Mac #356

tony-- opened this issue Dec 4, 2018 · 2 comments

Comments

@tony--
Copy link

tony-- commented Dec 4, 2018

After installing jabba and [email protected] on Mac, eclipse would not start.
A dialog was displayed with a message similar to "JVM Shared library does not contain the JNI_CreateJavaVM symbol".
In terminal, an error message indicated that ".jabba/jdk/[email protected]/Contents/MacOS/libjli.dylib: file too short".

This SO answer pointed me to the root cause.
For Java 11, Contents/MacOS/libjli.dylib should be a symbolic link pointing to ../Home/lib/jli/libjli.dylib (for Java 8 it should link to ../Home/jre/lib/jli/libjli.dylib), but instead it is a zero-length file. This was the case for the 3 JDKs I installed on Mac using jabba:
[email protected]
[email protected]
[email protected]

I directly downloaded [email protected] from the url listed in index.json and extracted it using archive utility. Contents/MacOS/libjli.dylib was a valid symbolic link.

Based on this, jabba's tar.gz extraction on Mac is not preserving symbol links.

@evacchi
Copy link

evacchi commented Dec 13, 2018

I think I can reproduce this on Linux when I install graal. The bin/native-image executable extracted by jabba is an empty file, but if I extract a tgz I downloaded manually it's a symlink

Any workaround, beside installing manually?

Thanks!

EDIT: version tested 0.9.2 upgraded to 0.11.0 same outcome

shyiko pushed a commit that referenced this issue Dec 18, 2018
@shyiko
Copy link
Owner

shyiko commented Dec 18, 2018

My sincere apologies for the delayed response (for some reason "Notifications" were set to "Not Watching" and so I wasn't getting any messages for over 3 weeks).

Fixed in 0.11.1.

@shyiko shyiko closed this as completed Dec 18, 2018
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

3 participants