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

[Mirko Vukovic]

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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/armedbear-devel/attachments/20170103/49939dcc/attachment.html>