From: Guillaume Le Vaillant <glv@posteo.net>
To: Benjamin Slade <beoram@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: stumpwm on guix - "sb-cltl2" issues
Date: Sat, 16 Apr 2022 17:40:45 +0000 [thread overview]
Message-ID: <87mtgkvrli.fsf@kitej> (raw)
In-Reply-To: <87wnfpq10p.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1158 bytes --]
Benjamin Slade <beoram@gmail.com> skribis:
> I'm trying to run my long-standing stumpwm init.lisp on a recent Guix install,
> using the packaged stumpwm, however when it launches, it fails to process the
> init.lisp and gives me an "Don't know how to REQUIRE sb-cltl2." error.
>
> I've set the SBCL_HOME variable both in .xprofile and in the init.lisp itself [via `(sb-posix:putenv "SBCL_HOME=/run/current-system/profile/lib/sbcl/")' ], but this doesn't seem to help.
>
> Is there a good way around this? (On my other system I just compile stumpwm from source and install; I don't know if that makes a difference here.)
>
> —Ben
Instead of setting SBCL_HOME, could you try adding something like
'(push "/path/to/lib/sbcl/contrib/" asdf:*central-registry*)'
at the beginning of your "init.lisp" file?
As stumpwm doesn't use the sb-cltl2 contrib, it is not included in the
stumpwm compiled binary. But telling ASDF where it can find it and then
using '(asdf:load-system :sb-cltl2)' or '(require :sb-cltl2)' should
work.
If it doesn't, you could also try loading it directly with
'(load "/path/to/lib/sbcl/contrib/sb-cltl2.fasl")'.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2022-04-16 17:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-16 0:29 stumpwm on guix - "sb-cltl2" issues Benjamin Slade
2022-04-16 17:40 ` Guillaume Le Vaillant [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-05-03 14:18 Wil deBeest
2022-05-03 14:35 Wil deBeest
2022-05-06 14:44 ` Katherine Cox-Buday
2022-05-13 19:09 ` Benjamin Slade
2022-07-03 1:31 ` Benjamin Slade
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mtgkvrli.fsf@kitej \
--to=glv@posteo.net \
--cc=beoram@gmail.com \
--cc=help-guix@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.