Hi Jack, Ludo',

On Mon, 06 Mar 2017 11:53:26 +0100
ludo@gnu.org (Ludovic Courtès) wrote:

> Hello,
> 
> Jack Lucas <silverbeard@protonmail.com> skribis:
> 
> > I really don't know how to describe this issue. I can't actually
> > pinpoint where the problem is even though I've spent almost all day
> > pulling my hair out over it.
> >
> > When installing CCL guix will pull version 1.11 from the server to
> > install. Version 1.11 is built with ASDF3.1.5 but after installing
> > and loading it up using (require "asdf"), (in-package :asdf) and
> > finally *asdf-version* it says it has ASDF 2.26.

Huh. Way back when I started working on CL in guix, I wondered why
the ccl package didn't include asdf. Now I have a reason to investigate
it.

> >
> > So I guess what I am asking for help with is I have poured over the
> > CCL definition in guix, and every single asdf related file in the
> > guix tree. I see absolutely no reasoning for this would change from
> > 3.1.5 -> 2.26. 
> >
> > I've tried grepping for any other LISP directories or asfd.lisp's.
> > And nothing exists.
> >
> > I'm fine with trying to work around it I just want to make sure
> > guix isn't doing some backround magic to force ASDF 2.26 on
> > everything.  

Guix isn't doing anything special. After having investigated, my guess
is that CCL_DEFAULT_DIRECTORY is set in your environment. This variable
determines how ccl looks up pathnames with the 'ccl:' prefix. You can
check '*module-search-path*' to see which pathnames are being searched
for asdf. The other possibilities are that you have asdf in
$HOME/openmcl/modules, or that you've extended '*module-search-path*'
in your initialization file, and placed asdf somewhere there.

If you'd like to see how the guix ccl package acts in the absence of
your environment, you can run it like this:

$ guix environment --pure --container --ad-hoc ccl -- ccl

> 
> I don’t know what the problem is, but Andy (Cc’d) may have an answer.
> Andy?

The attached patches aim to address the problems. The first is that our
ccl package was not installing any libraries. I'm not sure if we should
be trying to compile these libraries first; I wasn't able to find
anything in the build system to suggest such. The second patch ensures
that the environment always points toward the executed ccl image's
directory, which I believe is in line with the guix philosophy of
"static" package behaviour.

> 
> Thanks for reporting the issue.
> 
> Ludo’.

Thanks!

--
Andy