Also, how about other ABCL version, e.g. 1.2.1? Does it work?

27.04.2014, 00:37, "Anton Vodonosov" avodonosov@yandex.ru:

As far as I understand, it tries to fetch jna from maven, using maven API. I guess the maven API is changed again, so in your maven class AETHER.GRAPH.DEPENDENCY' is not found.

Trying with different maven may verify this.

Best regards,

• Anton

26.04.2014, 20:21, "Timo Myyrä" timo.myyra@wickedbsd.net:

...

Hi,

There seems to be some issues loading java dependencies on OpenBSD.  I got following when trying to load hunchentoot system from quicklisp.

[1] CL-USER(7): (ql:quickload 'hunchentoot)  To load "hunchentoot":    Load 1 ASDF system:      hunchentoot  ; Loading "hunchentoot"  ..............  Using probed value of abcl-contrib:  '/usr/local/abcl/abcl-contrib.jar'.  Added jar:file:/usr/local/abcl/abcl-contrib.jar!/quicklisp/ to ASDF.  Added jar:file:/usr/local/abcl/abcl-contrib.jar!/mvn/ to ASDF.  Added jar:file:/usr/local/abcl/abcl-contrib.jar!/jss/ to ASDF.  Added jar:file:/usr/local/abcl/abcl-contrib.jar!/jfli/ to ASDF.  Added jar:file:/usr/local/abcl/abcl-contrib.jar!/asdf-jar/ to ASDF.  Added jar:file:/usr/local/abcl/abcl-contrib.jar!/asdf-install/ to ASDF.  Added jar:file:/usr/local/abcl/abcl-contrib.jar!/abcl-asdf/ to ASDF.  jnaASDF could not load  because Java exception 'java.lang.ClassNotFoundException: AETHER.GRAPH.DEPENDENCY'..  #<THREAD "interpreter" {435DFB5F}>: Debugger invoked on condition of type JAVA-EXCEPTION    Java exception 'java.lang.ClassNotFoundException: AETHER.GRAPH.DEPENDENCY'.  Restarts:    0: ABORT     Return to debug level 1.    1: RETRY     Retry compiling #<ASDF/INTERFACE:MVN "jna" "net.java.dev.jna/jna/4.0.0">.    2: ACCEPT    Continue, treating compiling #<ASDF/INTERFACE:MVN "jna" "net.java.dev.jna/jna/4.0.0"> as having been successful.    3: RETRY     Retry compiling #<ASDF/LISP-ACTION:CL-SOURCE-FILE "cffi" "src" "cffi-abcl">.    4: ACCEPT    Continue, treating compiling #<ASDF/LISP-ACTION:CL-SOURCE-FILE "cffi" "src" "cffi-abcl"> as having been successful.    5: ABORT     Give up on "hunchentoot"    6: ABORT     Give up on "asdf-test"    7: TOP-LEVEL Return to top level.  [2] CL-USER(8):

Here's some package version info:  abcl-1.3.0

zmyrgel:13280$ ls -l /usr/local/abcl/  total 20788  -r--r--r--  1 root  bin       75337 Mar 16 18:15 abcl-contrib.jar  -r--r--r--  1 root  bin    10414020 Mar 16 18:15 abcl.jar  -r--r--r--  1 root  bin      128156 Mar 16 18:15 abcl_completions  drwxr-xr-x  4 root  wheel       512 Apr 26 18:50 src/

zmyrgel:13279$ mvn --version  Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9; 2014-02-14T19:37:52+02:00)  Maven home: /usr/local/maven  Java version: 1.7.0_21, vendor: Oracle Corporation  Java home: /usr/local/jdk-1.7.0/jre  Default locale: en_US, platform encoding: UTF-8  OS name: "openbsd", version: "5.5", arch: "amd64", family: "unix"

I had little debugging help via irc but that didn't lead to any results and I've  already forgot the steps tried.  So here's an another attempt to solve this and hopefully get this resolved.

Any ideas what to try to get this resolved?

Timo

_______________________________________________  Armedbear-devel mailing list  Armedbear-devel@common-lisp.net  http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel

---

Armedbear-devel mailing list Armedbear-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel

_______________________________________________ Armedbear-devel mailing list Armedbear-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel

On 27 Apr 2014, at 08:47, Timo Myyrä timo.myyra@wickedbsd.net wrote:

Ha, found the problem here... and before getting my first cup of morning coffee. The problem is in the contrib/abcl-asdf/maven-embedder.lisp. The maven library path is wrong so abcl won't find maven libraries. OpenBSD port of maven installs itself under /usr/local/maven. I've made simple patch for testing and with it loading of hunchentoot worked fine.

$OpenBSD$ fix maven lib location for openbsd

I’ve patched [ABCL trunk with a slightly more involved version of your patch][1]. I *think* you could have gotten away with setting the ABCL-ASDF:*MVN-LIBS-DIRECTORY* before the initialization routine ABCL-ASDF:INIT was run, but admit that such a step is certainly not clear from the current state of the documentation.

I removed the explicit conditionalization on OpenBSD to check this path, as it might well be the case for other OS choices.

Please let me know if this doesn’t work for you for some reason, and thanks for your patch.

[1]: http://abcl.org/trac/changeset/14696

On 27 Apr 2014, at 11:13, Timo Myyrä timo.myyra@wickedbsd.net wrote:

[…]

Yeah, I just wanted quick and easy way to test that problem is in the maven libs. I hoped for a cleaner version.

I’m probably a thousand more times likely to respond to problems with patches than without, so such effort is never wasted (at least with me!)

I tested you fix and it works for me.

Thanks for the test.

Any estimate when 1.3.1 would get released? I'm just wondering on should I update OpenBSD port to 1.3.0 + backport this patch or just wait for the 1.3.1.

“Soon”? Maybe later today if I get the moxie…

I still have to back port a few patches (like “yours”) to make a new release candidate. That part will definitely happen today.