Errors loading CFFI: BAD-SYSTEM-NAME, missing Maven executable

[Mark Evenson]

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.

-- 
"A screaming comes across the sky.  It has happened before, but there
is nothing to compare to it now."