Created attachment 145209 [details]
patch to update
Patch to update it.
maintainer timed out, moving to patch-ready
(In reply to John Marino from comment #1)
> maintainer timed out, moving to patch-ready
Last time I checked, it did not compile on i386.
I am sorry for the late response.
Building on i386 leads to:
libtool: link: cc -I/usr/local/lib/libffi-3.0.13/include -I/usr/local/lib/libffi-3.0.13/include -O2 -pipe -fno-strict-aliasing -o jamvm jam.o -L/usr/local/lib ./.libs/libcore.a -lffi -lz -lm -lrt -lthr
./.libs/libcore.a(dll.o): In function `setJNIMethod':
dll.c:(.text+0xe73): undefined reference to `convertSig2Simple'
dll.c:(.text+0xe84): undefined reference to `jni_static_stubs'
dll.c:(.text+0xe8d): undefined reference to `jni_static_stubs'
dll.c:(.text+0xebd): undefined reference to `jni_stubs'
dll.c:(.text+0xec6): undefined reference to `jni_stubs'
cc: error: linker command failed with exit code 1 (use -v to see invocation)
convertSig2Simple is found in src/stubs.c, but not used because
USE_MD_STUBS is defined.
Created attachment 179542 [details]
jamvm 2.0.0 patch with openjdk support
Here's my patch, with OpenJDK support. I've been able to run a Jetty server with /usr/local/openjdk7/jre/bin/java -XXaltjvm=jamvm -jar … !
Current updates of OpenJDK 8 don't work with JamVM 2.0.0, so it's commented out.
thanks for the patch, testbuilds on 12a, 11a are fine.
testbuild on 10i still fails, see
Do you have an idea on how to fix this ? I'm testbuilding 10.3a right now.
and testbuilding on 11i to see if it's a 10 or a i386 issue.
Result: It's an i386 issue. Any ideas ?
FYI the port has been deprecated in ports r483960.
Expired port removed.