From: Guillaume Le Vaillant <glv@posteo.net>
To: Charles <charles.b.jackson@protonmail.com>
Cc: 49965@debbugs.gnu.org
Subject: [bug#49965] Correct Input type for Common Lisp packages
Date: Fri, 13 Aug 2021 07:33:36 +0000 [thread overview]
Message-ID: <87mtplre7j.fsf@kitej> (raw)
In-Reply-To: <i6MG5M5U3WDXyk-AsCo7aaTvT8BX_ohrXXgotK9xHDkS4NQ4tVQFee572PqE-pfc_VXM95jBF8muDPFBSu6kPjhkL2nd-cW1wS4YMHeMc3c=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 789 bytes --]
Charles <charles.b.jackson@protonmail.com> skribis:
> Thank you for the valuble information. There is a small misunderstanding:
> the console log is from my pure guix system; I just needed to do a guix
> upgrade sbcl. Never-the-less, common lisp packages added in an ad-hoc
> environment can't be found.
It looks like "$GUIX_ENVIRONMENT/etc" does not get added to
XDG_CONFIG_DIRS in an ad-hoc environment when sbcl is not in the list
of ad-hoc packages, which is why it fails to find some Lisp libraries.
In other words, this works:
guix environment --ad-hoc sbcl sbcl-cl-str --
sbcl --eval '(require :asdf)' --eval '(asdf:load-system "str")'
But this doesn't work:
guix environment --ad-hoc sbcl-cl-str --
sbcl --eval '(require :asdf)' --eval '(asdf:load-system "str")'
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2021-08-13 7:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-09 17:19 [bug#49965] Correct Input type for Common Lisp packages Charles via Guix-patches via
2021-08-09 20:30 ` Guillaume Le Vaillant
2021-08-09 20:58 ` Charles via Guix-patches via
2021-08-10 8:10 ` Guillaume Le Vaillant
2021-08-11 23:39 ` Charles via Guix-patches via
2021-08-12 8:51 ` Guillaume Le Vaillant
2021-08-12 13:47 ` Charles via Guix-patches via
2021-08-13 7:33 ` Guillaume Le Vaillant [this message]
2021-08-14 0:38 ` Charles via Guix-patches via
2021-08-14 9:48 ` bug#49965: " 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=87mtplre7j.fsf@kitej \
--to=glv@posteo.net \
--cc=49965@debbugs.gnu.org \
--cc=charles.b.jackson@protonmail.com \
/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).