On 10/7/2010 12:44 PM, Cyrus Harmon wrote: A trivial rename of the .asd file (and the contained system) to, say, clssl, allows ABCL to get past this, so it looks like the + in the file name (or ASDF system name) is causing the problem.

Of course the trivial fix doesn't really fix things as there's still a CFFI problem, but that's for another email....

Cyrus,

I myself need cl+ssl for our project and was thinking of wrapping the CFFI calls to openssl with a layer that calls java crypto APIs instead.

There is more to do, but I can give that particular problem some attention, mostly because we need it for work.

Regards.

- mahmud

On Oct 7, 2010, at 18:44 , Cyrus Harmon wrote:

Dear ABCL Developers,

Attempting to asdf:load cl+ssl gives the following error:

Loadable FASL not found for '/Users/sly/.cache/common-lisp/armedbear-0.23.0-dev-fasl36-darwin-java-1.6/Users/sly/src/clbuild/source/cl+ssl/package.abcl' in 'jar:file:/Users/sly/.cache/common-lisp/armedbear-0.23.0-dev-fasl36-darwin-java-1.6/Users/sly/src/clbuild/source/cl ssl/package.abcl!/package._' [Condition of type FILE-ERROR]

Filed as [ticket #110][1] fixed in [svn r13024][2]. Thanks for the bug report!

[1]: http://trac.common-lisp.net/armedbear/ticket/110 [2]: http://trac.common-lisp.net/armedbear/changeset/13024

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