Re: clisp executable images fail at startup

[Ludovic Courtès]

Hi!

Ricardo Wurmus <address@hidden> skribis:

> for fun I just ported Yale Haskell to CLISP (it only needed a handful of
> changes).  I’m using EXT:SAVEINITMEM to generate an executable image.
> Building the image outside of Guix I can run the executable and I get a
> Haskell prompt as expected.

Excellent!

> When I packaged it and tried to run the packaged executable, however, I
> got this error:
>
>     module 'syscalls' requires package OS.
>
> (This error is reported by CLISP.)

Could it be a search path issue?  Did you try strace’ing clisp to see
where it’s looking for “OS”?

HTH!
Ludo’.