From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) Subject: bug#22571: Acknowledgement (Guix on Debian Testing sbcl package needs warning to set SBCL_HOME) Date: Wed, 10 Feb 2016 22:32:07 +0100 Message-ID: <87d1s4i754.fsf@gnu.org> References: <87y4aycs21.fsf@mordocai.net> <878u2tpbt4.fsf@mordocai.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:49657) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aTcNn-0004KN-3z for bug-guix@gnu.org; Wed, 10 Feb 2016 16:33:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aTcNi-0000N7-5t for bug-guix@gnu.org; Wed, 10 Feb 2016 16:33:07 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:54494) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aTcNi-0000N3-1T for bug-guix@gnu.org; Wed, 10 Feb 2016 16:33:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84) (envelope-from ) id 1aTcNh-0004Pb-Tg for bug-guix@gnu.org; Wed, 10 Feb 2016 16:33:01 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <878u2tpbt4.fsf@mordocai.net> (Christopher W. Carpenter's message of "Tue, 09 Feb 2016 19:57:11 -0600") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org To: Christopher W Carpenter Cc: 22571-done@debbugs.gnu.org Christopher W Carpenter skribis: > 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! Indeed, thanks for letting us know! Ludo=E2=80=99.