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

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

[Christopher W Carpenter]

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

ludo@gnu.org (Ludovic Courtès) writes:

> 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:
>
> $ 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 ]
>
> 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’.

Hey Ludo,

Yes, i was definitely running ~/.guix-profile/bin/sbcl. Not only did I
not have any other sbcl installed, but the guix version (1.2.8) differs
From the debian testing version (1.3.1) and I verified that the correct
version was running.

I also have no /etc/sbclrc for the same reason.

I haven't used guix long but from what I can tell there are a lot of
issues similar to this that only seem to affect non-GuixSD systems.

It appears this problem does not occur if I build sbcl myself rather than using the substitute from
hydra. I am attempting to verify this, as that seems very weird/impossible.

Thanks,
Christopher Carpenter

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

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

[Taylan Ulrich Bayırlı/Kammer]

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

> ludo@gnu.org (Ludovic Courtès) writes:
>
>> 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:
>>
>> $ 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 ]
>>
>> 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’.
>
> Hey Ludo,
>
> Yes, i was definitely running ~/.guix-profile/bin/sbcl. Not only did I
> not have any other sbcl installed, but the guix version (1.2.8) differs
> From the debian testing version (1.3.1) and I verified that the correct
> version was running.
>
> I also have no /etc/sbclrc for the same reason.
>
> I haven't used guix long but from what I can tell there are a lot of
> issues similar to this that only seem to affect non-GuixSD systems.
>
> It appears this problem does not occur if I build sbcl myself rather
> than using the substitute from hydra. I am attempting to verify this,
> as that seems very weird/impossible.
>
> Thanks,
> Christopher Carpenter

Do you have the SBCL_HOME environment variable set while running SBCL?
If so, make sure it's correct, or simply unset it.  (It *should* work
when it's unset.)

I can't reproduce the issue using SBCL 1.2.8 from Hydra, i.e.:

    /gnu/store/2vlqnaj650nr4hv5iq19xf402vc2l60l-sbcl-1.2.8/

I don't have SBCL_HOME set, have no /etc/sbclrc, and have no other
installation of SBCL on my system; when I run .../bin/sbcl from the
above package, it fires up the REPL just fine.  I can also install it
into my profile and run ~/.guix-profile/bin/sbcl.

I also reproduced Ludo's test and similarly had no output from grep.

For the record, someone had raised a similar issue before, and it came
out they had SBCL_HOME set to a wrong value:

    https://gnunet.org/bot/log/guix/2015-11-19#T820295

So either it's that, or something else unusual might be going on in your
system...

To make absolutely sure SBCL_HOME is unset before starting up SBCL, you
can run the command "unset SBCL_HOME" in your shell, and run "sbcl" in
the same shell session right after that.

Hope that helps!
Taylan

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