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.