johnthad / zipeg

Automatically exported from code.google.com/p/zipeg
0 stars 0 forks source link

Zipeg doesn't work with Java7 on OSX #44

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
# What steps will reproduce the problem?
Run Zipeg (2.9.4.1316) on OSX (10.9.1) without Java 6 (but JDK 1.7u45 & JRE 
7u51) 
Note: other Java Apps work just fine...

# What is the expected output?
Zipeg runs without Legacy Java 6

# What do you see instead?
/Applications/Zipeg.app/Contents/MacOS/JavaApplicationStubα
[JavaAppLauncher] Requested [1.5*], launching in [1.7] instead.
JavaVM: Failed to load JVM: 
/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home/bundle/Libraries
/libserver.dylib
JavaVM: Failed to load JVM: 
/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home/bundle/Libraries
/libserver.dylib
JavaVM FATAL: Failed to load the jvm library.
[JavaAppLauncher Error] JNI_CreateJavaVM() failed, error: -1

# Please provide any additional information below.
Correct path is probably one of these:
- 
/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home/jre/lib/server/l
ibjvm.dylib
- /Library/Internet\ 
Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/lib/server/libjvm.dylib

running the jar manually obviously gives: 
$ java -jar /Applications/Zipeg.app/Contents/Resources/Java/zipeg.jar 
Zipeg: /Applications/Zipeg.app/Contents/Resources/Java/lib7za-osx-i386.jnilib: 
dlopen(/Applications/Zipeg.app/Contents/Resources/Java/lib7za-osx-i386.jnilib, 
1): no suitable image found.  Did find:
    /Applications/Zipeg.app/Contents/Resources/Java/lib7za-osx-i386.jnilib: mach-o, but wrong architecture

Original issue reported on code.google.com by clauden...@gmail.com on 30 Mar 2014 at 3:47

GoogleCodeExporter commented 8 years ago
i guess this will be fixed when zipeg goes 64bit...

Original comment by clauden...@gmail.com on 30 Mar 2014 at 3:58

GoogleCodeExporter commented 8 years ago
OSX 10.9.x only has 64bit java available, from oracle. No legacy java code.

Can this program possibly be updated to not rely on Legacy Java code to run?

Original comment by ATho...@lbl.gov on 16 Oct 2014 at 10:24