all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Christopher W Carpenter <mordocai@mordocai.net>
To: 22571@debbugs.gnu.org
Subject: bug#22571: Acknowledgement (Guix on Debian Testing sbcl package needs warning to set SBCL_HOME)
Date: Tue, 09 Feb 2016 19:57:11 -0600	[thread overview]
Message-ID: <878u2tpbt4.fsf@mordocai.net> (raw)
In-Reply-To: <handler.22571.B.145473745812398.ack@debbugs.gnu.org> (GNU bug Tracking System's message of "Sat, 06 Feb 2016 05:45:02 +0000")

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


I found the problem, and this can be closed IMHO.

I use StumpWM, which is written in common lisp and I use sbcl to run it.
It appears that when the stumpwm image is created the SBCL_HOME
environment variable's state at that time is stored. In addition, for
whatever reason, any processes started from stumpwm will have a
SBCL_HOME environment variable with that same value.

Therefore, my issue was that my stumpwm that was starting my
processes(and the processess themselves)
had an old, incorrect value for SBCL_HOME which would then cause this
error.

Interesting "bug" to find! Thanks for the help!

Christopher Carpenter

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

  parent reply	other threads:[~2016-02-10  1:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-06  5:40 bug#22571: Guix on Debian Testing sbcl package needs warning to set SBCL_HOME Christopher W Carpenter
2016-02-06  8:49 ` Leo Famulari
2016-02-06 13:06 ` Ludovic Courtès
2016-02-06 22:59   ` Christopher W Carpenter
2016-02-07 12:43     ` Taylan Ulrich Bayırlı/Kammer
     [not found] ` <handler.22571.B.145473745812398.ack@debbugs.gnu.org>
2016-02-10  1:57   ` Christopher W Carpenter [this message]
2016-02-10 10:20     ` bug#22571: Acknowledgement (Guix on Debian Testing sbcl package needs warning to set SBCL_HOME) Alex Kost
2016-02-10 21:32     ` Ludovic Courtès

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=878u2tpbt4.fsf@mordocai.net \
    --to=mordocai@mordocai.net \
    --cc=22571@debbugs.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.