Loading CFFI, I get BAD-SYSTEM-NAME errors related to followed by a huge stack dump, and then debugger related to the Maven executable.
I tested this with --noinit.
Thanks for your help.
Here are more details:
Starting ABCL on Windows 10 like so:
/c/Windows/SysWOW64/java.exe -jar
/c/mv-program-files/abcl-bin-1.4.0/abcl.jar Armed Bear Common Lisp 1.4.0 Java 1.7.0_51 Oracle Corporation Java HotSpot(TM) Client VM Low-level initialization completed in 0.23 seconds.
Now I try to load cffi with quicklisp. Following quickload, I get many style-warnings about redefining UIOP:
CL-USER(1): (ql:quickload :cffi) To load "cffi": Load 1 ASDF system: cffi ; Loading "cffi" .................................................. .................................................. .................................................. .................................................. .................................... ; Caught STYLE-WARNING: ; redefining UIOP/PACKAGE:FIND-PACKAGE* in #P"C:/mv-program-files/my-lisp-libraries/asdf/uiop/package.lisp" (previously defined in #P"C:/Users/977315/asdf.3.1.7.43.lisp")
; Caught STYLE-WARNING: ; redefining UIOP/PACKAGE:FIND-SYMBOL* in #P"C:/mv-program-files/my-lisp-libraries/asdf/uiop/package.lisp" (previously defined in #P"C:/Users/977315/asdf.3.1.7.43.lisp")
.... many such warnings ...
After finishing the style-warning messages, come ASDF load messages, the BAD-SYSTEM-NAME messages, followed by a long java stack dump:
Using probed value of abcl-contrib: 'C:/mv-program-files/abcl-bin-1.4.0/abcl-contrib.jar'. Added jar:file:C:/mv-program-files/abcl-bin-1.4.0/abcl-contrib.jar!/quicklisp/ to ASDF. Added jar:file:C:/mv-program-files/abcl-bin-1.4.0/abcl-contrib.jar!/mvn/ to ASDF. Added jar:file:C:/mv-program-files/abcl-bin-1.4.0/abcl-contrib.jar!/jss/ to ASDF. Added jar:file:C:/mv-program-files/abcl-bin-1.4.0/abcl-contrib.jar!/jfli/ to ASDF. Added jar:file:C:/mv-program-files/abcl-bin-1.4.0/abcl-contrib.jar!/asdf-jar/ to ASDF. Added jar:file:C:/mv-program-files/abcl-bin-1.4.0/abcl-contrib.jar!/abcl-asdf/ to ASDF. . ; Caught BAD-SYSTEM-NAME: ; System definition file #P"jar:file:C:/mv-program-files/abcl-bin-1.4.0/abcl-contrib.jar!/jss/jss.asd" contains definition for system "jss-tests". Please only define "jss" and secondary systems with a name starting with "jss/" (e.g. "jss/test") in that file.
; Caught BAD-SYSTEM-NAME: ; System definition file #P"jar:file:C:/mv-program-files/abcl-bin-1.4.0/abcl-contrib.jar!/abcl-asdf/abcl-asdf.asd" contains definition for system "abcl-asdf-test". Please only define "abcl-asdf" and secondary systems with a name starting with "abcl-asdf/" (e.g. "abcl-asdf/test") in that file.
java.lang.ExceptionInInitializerError at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at java.lang.Class.newInstance(Unknown Source) at org.armedbear.lisp.FaslClassLoader.loadFunction(FaslClassLoader.java:130) at org.armedbear.lisp.FaslClassLoader$pf_get_fasl_function.execute(FaslClassLoader.ja
va:165) at org.armedbear.lisp.LispThread.execute(LispThread.java:832) ...
At the end I get into the ABCL debugger:
Caused by: org.armedbear.lisp.Go ; Caught SIMPLE-WARNING: ; Unable to locate Maven executable to find Maven Aether adaptors.
jnaASDF could not load because Java exception 'java.lang.ClassNotFoundException: com.sun.jna
.Native'.. #<THREAD "interpreter" {472108}>: Debugger invoked on condition of type JAVA-EXCEPTION Java exception 'java.lang.ClassNotFoundException: com.sun.jna.Native'. Restarts: 0: RETRY Retry completing load for #<ASDF/SYSTEM:SYSTEM "jna">. 1: ACCEPT Continue, treating completing load for #<ASDF/SYSTEM:SYSTE M "jna"> as having been successful. 2: RETRY Retry compiling #<ASDF/LISP-ACTION:CL-SOURCE-FILE "cffi" " src" "cffi-abcl">. 3: ACCEPT Continue, treating compiling #<ASDF/LISP-ACTION:CL-SOURCE- FILE "cffi" "src" "cffi-abcl"> as having been successful. 4: RETRY Retry ASDF operation. 5: CLEAR-CONFIGURATION-AND-RETRY Retry ASDF operation after resetting the configuration. 6: TOP-LEVEL Return to top level.
On 1/3/17 04:56, Mirko Vukovic wrote:
Loading CFFI, I get BAD-SYSTEM-NAME errors related to followed by a huge stack dump, and then debugger related to the Maven executable.
I tested this with --noinit.
Thanks for your help.
Here are more details:
Starting ABCL on Windows 10 like so:
/c/Windows/SysWOW64/java.exe -jar
/c/mv-program-files/abcl-bin-1.4.0/abcl.jar Armed Bear Common Lisp 1.4.0 Java 1.7.0_51 Oracle Corporation Java HotSpot(TM) Client VM Low-level initialization completed in 0.23 seconds.
Now I try to load cffi with quicklisp. Following quickload, I get many style-warnings about redefining UIOP:
These aren't errors, per se, but warnings. The system is attempting to load your local version of ASDF from file:C:/mv-program-files/my-lisp-libraries/asdf/. Unless there is a compelling reason to try to change the ASDF definition at runtime, I would remove your local ASDF version and stick to the one that ABCL ships with.
CL-USER(1): (ql:quickload :cffi) To load "cffi": Load 1 ASDF system: cffi ; Loading "cffi" .................................................. .................................................. .................................................. .................................................. .................................... ; Caught STYLE-WARNING: ; redefining UIOP/PACKAGE:FIND-PACKAGE* in #P"C:/mv-program-files/my-lisp-libraries/asdf/uiop/package.lisp" (previously defined in #P"C:/Users/977315/asdf.3.1.7.43.lisp")
; Caught STYLE-WARNING: ; redefining UIOP/PACKAGE:FIND-SYMBOL* in #P"C:/mv-program-files/my-lisp-libraries/asdf/uiop/package.lisp" (previously defined in #P"C:/Users/977315/asdf.3.1.7.43.lisp")
.... many such warnings ...
After finishing the style-warning messages, come ASDF load messages, the BAD-SYSTEM-NAME messages, followed by a long java stack dump:
Using probed value of abcl-contrib: 'C:/mv-program-files/abcl-bin-1.4.0/abcl-contrib.jar'. Added jar:file:C:/mv-program-files/abcl-bin-1.4.0/abcl-contrib.jar!/quicklisp/ to ASDF. Added jar:file:C:/mv-program-files/abcl-bin-1.4.0/abcl-contrib.jar!/mvn/ to ASDF. Added jar:file:C:/mv-program-files/abcl-bin-1.4.0/abcl-contrib.jar!/jss/ to ASDF. Added jar:file:C:/mv-program-files/abcl-bin-1.4.0/abcl-contrib.jar!/jfli/ to ASDF. Added jar:file:C:/mv-program-files/abcl-bin-1.4.0/abcl-contrib.jar!/asdf-jar/ to ASDF. Added jar:file:C:/mv-program-files/abcl-bin-1.4.0/abcl-contrib.jar!/abcl-asdf/ to ASDF. . ; Caught BAD-SYSTEM-NAME: ; System definition file #P"jar:file:C:/mv-program-files/abcl-bin-1.4.0/abcl-contrib.jar!/jss/jss.asd" contains definition for system "jss-tests". Please only define "jss" and secondary systems with a name starting with "jss/" (e.g. "jss/test") in that file.
; Caught BAD-SYSTEM-NAME: ; System definition file #P"jar:file:C:/mv-program-files/abcl-bin-1.4.0/abcl-contrib.jar!/abcl-asdf/abcl-asdf.asd" contains definition for system "abcl-asdf-test". Please only define "abcl-asdf" and secondary systems with a name starting with "abcl-asdf/" (e.g. "abcl-asdf/test") in that file.
[…]
At the end I get into the ABCL debugger:
Caused by: org.armedbear.lisp.Go ; Caught SIMPLE-WARNING: ; Unable to locate Maven executable to find Maven Aether adaptors.
jnaASDF could not load because Java exception 'java.lang.ClassNotFoundException: com.sun.jna
.Native'.. #<THREAD "interpreter" {472108}>: Debugger invoked on condition of type JAVA-EXCEPTION Java exception 'java.lang.ClassNotFoundException: com.sun.jna.Native'.
Do you have a version of Maven installed locally? ABCL-ASDF uses the Maven Aether library to locate and download jna-4.2.2.jar, which provides the necessary JNI voodoo for CFFI to work.
This message in a known obscurity in ABCL that should be corrected.
On Tue, Jan 3, 2017 at 6:55 AM Mark Evenson evenson@panix.com wrote:
On 1/3/17 04:56, Mirko Vukovic wrote:
Loading CFFI, I get BAD-SYSTEM-NAME errors related to followed by a huge stack dump, and then debugger related to the Maven executable.
No progress after installing Maven & Aether Core. Do I need to install something else?
Details:
I installed JDK (needed for Maven), and Maven, and Aether Core Now I have Java 1.8.0_0112. I have updated Windows' PATH to include all three (so that maven -v gives the expected output:
C:>mvn -v C:\ Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T11:41:47-05:00) Maven home: C:\Program Files\apache-maven-3.3.9\bin.. Java version: 1.8.0_112, vendor: Oracle Corporation Java home: C:\Program Files\Java\jdk1.8.0_112\jre Default locale: en_US, platform encoding: Cp1252 OS name: "windows 10", version: "10.0", arch: "amd64", family: "dos"
Excerpt of error message:
at org.armedbear.lisp.Interpreter.run(Interpreter.java:361) at org.armedbear.lisp.Main$1.run(Main.java:48) at java.lang.Thread.run(Unknown Source) Caused by: org.armedbear.lisp.Go ; Caught SIMPLE-WARNING: ; Unable to locate Maven executable to find Maven Aether adaptors.
jnaASDF could not load because Java exception 'java.lang.ClassNotFoundException: com.sun.jna.Native'.. #<THREAD "interpreter" {3A0BDDFA}>: Debugger invoked on condition of type JAVA-EXCEPTION Java exception 'java.lang.ClassNotFoundException: com.sun.jna.Native'.
I tested this with --noinit.
Thanks for your help.
Here are more details:
Starting ABCL on Windows 10 like so:
/c/Windows/SysWOW64/java.exe -jar
/c/mv-program-files/abcl-bin-1.4.0/abcl.jar Armed Bear Common Lisp 1.4.0 Java 1.7.0_51 Oracle Corporation Java HotSpot(TM) Client VM Low-level initialization completed in 0.23 seconds.
Now I try to load cffi with quicklisp. Following quickload, I get many style-warnings about redefining UIOP:
These aren't errors, per se, but warnings. The system is attempting to load your local version of ASDF from file:C:/mv-program-files/my-lisp-libraries/asdf/. Unless there is a compelling reason to try to change the ASDF definition at runtime, I would remove your local ASDF version and stick to the one that ABCL ships with.
OK, I will try that.
Caused by: org.armedbear.lisp.Go
; Caught SIMPLE-WARNING: ; Unable to locate Maven executable to find Maven Aether adaptors.
jnaASDF could not load because Java exception 'java.lang.ClassNotFoundException: com.sun.jna
.Native'.. #<THREAD "interpreter" {472108}>: Debugger invoked on condition of type JAVA-EXCEPTION Java exception 'java.lang.ClassNotFoundException: com.sun.jna.Native'.
Do you have a version of Maven installed locally? ABCL-ASDF uses the Maven Aether library to locate and download jna-4.2.2.jar, which provides the necessary JNI voodoo for CFFI to work.
This message in a known obscurity in ABCL that should be corrected.
-- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now."
On 1/3/17 18:07, Mirko Vukovic wrote: […]
On 1/3/17 04:56, Mirko Vukovic wrote:
Loading CFFI, I get BAD-SYSTEM-NAME errors related to followed by a huge stack dump, and then debugger related to the Maven executable.
No progress after installing Maven & Aether Core. Do I need to install something else?
Details:
I installed JDK (needed for Maven), and Maven, and Aether Core Now I have Java 1.8.0_0112. I have updated Windows' PATH to include all three (so that maven -v gives the expected output:
C:>mvn -v C:\ Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
[…]
Excerpt of error message:
at org.armedbear.lisp.Interpreter.run(Interpreter.java:361) at org.armedbear.lisp.Main$1.run(Main.java:48) at java.lang.Thread.run(Unknown Source)Caused by: org.armedbear.lisp.Go ; Caught SIMPLE-WARNING: ; Unable to locate Maven executable to find Maven Aether adaptors.
jnaASDF could not load because Java exception 'java.lang.ClassNotFoundException: com.sun.jna.Native'.. #<THREAD "interpreter" {3A0BDDFA}>: Debugger invoked on condition of type JAVA-EXCEPTION Java exception 'java.lang.ClassNotFoundException: com.sun.jna.Native'.
it now."
It looks as if ABCL can't find the Maven exectuable, as maybe it has a different notion of the Windows System PATH.
Two ideas:
1) Figure out why ABCL can't find Maven:
CL-USER> (uiop/run-program:run-program "where.exe mvn.bat" :output :string)
2) Set ABCL-ASDF:*MVN-LIBS-DIRECTORY* to the location of the Maven jar files.
Progress - I got CFFI to load. I had to copy mvn.cmd to mvn.bat.
I think that closes this issue for me.
But I am not sure how to generate a fix for other users. Who should know about mvn.cmd vs mvn.bat?
On Wed, Jan 4, 2017 at 7:24 AM Mark Evenson evenson@panix.com wrote:
On 1/3/17 18:07, Mirko Vukovic wrote: […]
On 1/3/17 04:56, Mirko Vukovic wrote:
Loading CFFI, I get BAD-SYSTEM-NAME errors related to followed by a huge stack dump, and then debugger related to the Maven executable.
No progress after installing Maven & Aether Core. Do I need to install something else?
Details:
I installed JDK (needed for Maven), and Maven, and Aether Core Now I have Java 1.8.0_0112. I have updated Windows' PATH to include all three (so that maven -v gives the expected output:
C:>mvn -v C:\ Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
[…]
Excerpt of error message:
at org.armedbear.lisp.Interpreter.run(Interpreter.java:361) at org.armedbear.lisp.Main$1.run(Main.java:48) at java.lang.Thread.run(Unknown Source)Caused by: org.armedbear.lisp.Go ; Caught SIMPLE-WARNING: ; Unable to locate Maven executable to find Maven Aether adaptors.
stuff deleted
It looks as if ABCL can't find the Maven exectuable, as maybe it has a different notion of the Windows System PATH.
Two ideas:
Figure out why ABCL can't find Maven:
CL-USER> (uiop/run-program:run-program "where.exe mvn.bat" :output
:string)
- Set ABCL-ASDF:*MVN-LIBS-DIRECTORY* to the location of the Maven jar
files.
-- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now."
armedbear-devel@common-lisp.net
-
Mark Evenson -
Mirko Vukovic