bug#22571: Guix on Debian Testing sbcl package needs warning to set SBCL_HOME

bug#22571: Guix on Debian Testing sbcl package needs warning to set SBCL_HOME

[Christopher W Carpenter]

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


I talked with mark weaver about this on #guix and he asked me to send a
mail.

When doing guix package -i sbcl on my newly setup debian testing + guix
machine and then attempting to run sbcl I got the error:

fatal error encountered in SBCL pid 7492(tid 140737354086144):
can't find core file at /usr/lib64/sbcl/sbcl.core

Exporting SBCL_HOME=$HOME/.guix-profile/lib/sbcl fixes this for me. The
way this seems to be handled other places is by printing a message after
the package install explaining that this may be needed.

This seems like the appropriate thing to do to me. I'd love to submit a
patch if someone can guide me through it, I just started seriously
trying guix out today.

Thanks,
Christopher Carpenter

P.S. Please make sure to CC me in replies, I have not joined the mailing
list (yet).

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

bug#22571: Guix on Debian Testing sbcl package needs warning to set SBCL_HOME

[Leo Famulari]

On Fri, Feb 05, 2016 at 11:40:02PM -0600, Christopher W Carpenter wrote:
> 
> I talked with mark weaver about this on #guix and he asked me to send a
> mail.
> 
> When doing guix package -i sbcl on my newly setup debian testing + guix
> machine and then attempting to run sbcl I got the error:
> 
> fatal error encountered in SBCL pid 7492(tid 140737354086144):
> can't find core file at /usr/lib64/sbcl/sbcl.core
> 
> Exporting SBCL_HOME=$HOME/.guix-profile/lib/sbcl fixes this for me. The
> way this seems to be handled other places is by printing a message after
> the package install explaining that this may be needed.

There is a pretty good description of search-paths here:
https://www.gnu.org/software/guix/manual/guix.html#Invoking-guix-package

Basically, you can list the environment variables needed by the package
in the package definition. Then, users can view them or set them
automatically. There are some examples in the package tree.

> 
> This seems like the appropriate thing to do to me. I'd love to submit a
> patch if someone can guide me through it, I just started seriously
> trying guix out today.

I hope this helps. Feel free to ask for more help!

> 
> Thanks,
> Christopher Carpenter
> 
> P.S. Please make sure to CC me in replies, I have not joined the mailing
> list (yet).

bug#22571: Guix on Debian Testing sbcl package needs warning to set SBCL_HOME

[Ludovic Courtès]

Christopher W Carpenter <mordocai@mordocai.net> skribis:

> When doing guix package -i sbcl on my newly setup debian testing + guix
> machine and then attempting to run sbcl I got the error:
>
> fatal error encountered in SBCL pid 7492(tid 140737354086144):
> can't find core file at /usr/lib64/sbcl/sbcl.core

Are you sure you were running ~/.guix-profile/bin/sbcl?

I’ve just tried this on GuixSD, to check whether sbcl systematically
looks for things in /usr:

--8<---------------cut here---------------start------------->8---
$ strace -f -o ,,s $(guix build sbcl | head -1)/bin/sbcl 
This is SBCL 1.2.8, an implementation of ANSI Common Lisp.
More information about SBCL is available at <http://www.sbcl.org/>.

SBCL is free software, provided as is, with absolutely no warranty.
It is mostly in the public domain; some portions are provided under
BSD-style licenses.  See the CREDITS and COPYING files in the
distribution for more information.
* (+ 2 3)

5
*
$ grep /usr ,,s
[ nothing ]
--8<---------------cut here---------------end--------------->8---

However, it loads /etc/sbclrc.  Could it be that your host distro
provides such a file, which tweaks sbcl into reading from /usr/lib64?

Thanks for the report,
Ludo’.

bug#22571: Acknowledgement (Guix on Debian Testing sbcl package needs warning to set SBCL_HOME)

[Christopher W Carpenter]

[-- 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 --]

bug#22571: Acknowledgement (Guix on Debian Testing sbcl package needs warning to set SBCL_HOME)

[Alex Kost]

Christopher W Carpenter (2016-02-10 04:57 +0300) wrote:

> 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.

Oh, cool, I also use stumpwm but I've never noticed it because I compile
stumpwm using sbcl from Guix, so my value of SBCL_HOME is:

"/gnu/store/qkrqqb81hs6nypvzbgi8ixrrza78gvlb-sbcl-1.2.8/lib/sbcl"

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

Thanks for discovering it!  It's good to know this thing (just in case).

-- 
Alex

bug#22571: Acknowledgement (Guix on Debian Testing sbcl package needs warning to set SBCL_HOME)

[Ludovic Courtès]

Christopher W Carpenter <mordocai@mordocai.net> 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’.