unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Wil deBeest <bovid-19@4tii.de>
To: Benjamin Slade <beoram@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: stumpwm on guix - "sb-cltl2" issues
Date: Tue, 3 May 2022 16:35:49 +0200	[thread overview]
Message-ID: <8840696C-4023-4DCD-9CDE-21A7FAED3AD1@4tii.de> (raw)


Wil deBeest <bovid-19@4tii.de> writes:

> 
> Benjamin Slade <beoram@gmail.com> writes:
> 
>> 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
> 
> I used to have the same problem, but I don't remember what fixed it.
> 
> SBCL_HOME isn't set at all, I only have `exec /home/bovid-19/.guix-profile/bin/stumpwm' in my
> `~/.xinitrc', and my stumpwm init file starts like this:
> 
> (in-package :stumpwm)
> (require 'sb-cltl2)
> 
> 
> I'm not sure what else I can look for.

I have probably found the solution: in addition to stumpwm, I also have
`cl-trivial-cltl2' and `cl-asdf' (and sbcl) in my system configuration.
If you can confirm that those two packages are what was missing, we
should add them to the stumpwm package as inputs.


             reply	other threads:[~2022-05-03 14:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-03 14:35 Wil deBeest [this message]
2022-05-06 14:44 ` stumpwm on guix - "sb-cltl2" issues Katherine Cox-Buday
2022-05-13 19:09   ` Benjamin Slade
2022-07-03  1:31     ` Benjamin Slade
  -- strict thread matches above, loose matches on Subject: below --
2022-05-03 14:18 Wil deBeest
2022-04-16  0:29 Benjamin Slade
2022-04-16 17:40 ` Guillaume Le Vaillant

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8840696C-4023-4DCD-9CDE-21A7FAED3AD1@4tii.de \
    --to=bovid-19@4tii.de \
    --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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).