unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Guillaume Le Vaillant <glv@posteo.net>
To: Katherine Cox-Buday <cox.katherine.e@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: stumpwm contrib modules have been broken
Date: Wed, 06 Jan 2021 11:09:33 +0100	[thread overview]
Message-ID: <87k0sq74wy.fsf@yamatai> (raw)
In-Reply-To: <878s97ukes.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1293 bytes --]


Katherine Cox-Buday <cox.katherine.e@gmail.com> skribis:

> Sometime recently, the way Common Lisp code is compiled was changed (for
> the better, I think), and now my StumpWM contrib modules won't load.
> Here's why:
>
> StumpWM looks[1] for .asd files to determine what is a module. Guix's
> Common Lisp build system used to combine an entire system into a single
> .fasl file and then produce a .asd file for loading it. Now -- as far as
> I can tell -- it looks like `lib/common-lisp/sbcl` is more like the
> Common Lisp cache: one .fasl file per .lisp file.
>
> If I point StumpWM at `lib/common-lisp/sbcl` via `set-module-dir`, it
> finds no modules. If I point StumpWM at `share/common-lisp/sbcl`, it
> finds modules, tries to compile them, and then gives me a permissions
> error about writing to the `/gnu` store.
>
> Is anyone using StumpWM contrib modules successfully with Guix's new
> layout? How?
>
> [1] - https://github.com/stumpwm/stumpwm/blob/master/module.lisp#L70

Hi,

In my StumpWM init file, I use '(asdf:load-system ...)' instead of
'(load-module ...)' to load the contrib modules that are installed in my
Guix profile, and it works.

I'll see if I can find a combination 'set-module-dir' and
'add-to-load-path' that makes the 'load-module' function work
correctly...

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  parent reply	other threads:[~2021-01-06 10:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-05 21:46 stumpwm contrib modules have been broken Katherine Cox-Buday
2021-01-06  8:31 ` Pierre Neidhardt
2021-01-06 10:09 ` Guillaume Le Vaillant [this message]
2021-01-06 10:36   ` Guillaume Le Vaillant
2021-01-06 16:08     ` Katherine Cox-Buday
2021-01-06 17:26       ` 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=87k0sq74wy.fsf@yamatai \
    --to=glv@posteo.net \
    --cc=cox.katherine.e@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).