From: jgart via Guix-patches via <guix-patches@gnu.org>
To: Guillaume Le Vaillant <glv@posteo.net>
Cc: 52045@debbugs.gnu.org
Subject: [bug#52045] [PATCH] gnu: Add cl-clm.
Date: Tue, 12 Apr 2022 12:28:51 -0400 [thread overview]
Message-ID: <20220412122851.GB4449@gac.attlocal.net> (raw)
In-Reply-To: <877d7uwkyo.fsf@kitej>
On Tue, 12 Apr 2022 12:15:27 +0000 Guillaume Le Vaillant <glv@posteo.net> wrote:
> jgart <jgart@dismail.de> skribis:
>
> > On Sat, 09 Apr 2022 18:31:38 -0400 jgart <jgart@dismail.de> wrote:
> >
> > And that sbcl-clm and cl-clm are now in Guix 'R Us:
> >
> > https://git.sr.ht/~whereiseveryone/guixrus/tree/master/item/guixrus/packages/lisp.scm#L2371
>
> After entering the :clm package and trying some simple examples using the
> "v.ins" instrument, it failed because of some missing ".so" shared library.
> Does it work for you?
It fails because of the missing ".so" shared library for me also.
Here are some notes from the author of clm:
Try this:
```
(compile-file "v.ins")
(load "v")
```
``
> I had also experienced this error when first running `(require :clm)`
> in a sbcl repl:
It looks like you're running pulse audio and need something from alsa?
Maybe it's related to the code that builds sndplay in initmus.lisp.
``
The above is from Bill regarding the shared library code.
all best,
jgart
next prev parent reply other threads:[~2022-04-12 16:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 20:45 [bug#52045] [PATCH] gnu: Add cl-clm jgart via Guix-patches via
2021-11-23 13:00 ` Guillaume Le Vaillant
2022-04-09 22:18 ` jgart via Guix-patches via
2022-04-09 22:31 ` jgart via Guix-patches via
2022-04-09 22:33 ` jgart via Guix-patches via
2022-04-12 12:15 ` Guillaume Le Vaillant
2022-04-12 16:28 ` jgart via Guix-patches via [this message]
2022-07-07 18:23 ` Maxim Cournoyer
2022-07-08 0:16 ` jgart via Guix-patches via
2022-07-09 1:38 ` bug#52045: " Maxim Cournoyer
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=20220412122851.GB4449@gac.attlocal.net \
--to=guix-patches@gnu.org \
--cc=52045@debbugs.gnu.org \
--cc=glv@posteo.net \
--cc=jgart@dismail.de \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).