dump-image should not make CLISP images executable
Robert Goldman
rpgoldman at sift.info
Wed Dec 2 16:54:40 UTC 2020
I have posted your response onto the Gitlab merge request.
https://gitlab.common-lisp.net/asdf/asdf/-/merge_requests/155
On 2 Dec 2020, at 3:54, Pierre Neidhardt wrote:
> Thanks!
>
> I can't login on the Common Lisp GitLab because of the
> 2-factor-authentication.
> Since I can't answer Fare there, I'll do it here :)
>
> As far as I understand, CLISP does not behave the same way as SBCL;
> while SBCL supports images that are both executable and loadable with
> --core, it's not the case for CLISP where `-M` fails to load an
> executable image.
>
> Besides this change does alter the behaviour of `:executable t`, so
> the
> `uiop:dump-image ... :executable t` still generates an executable for
> CLISP.
>
> Maybe there is a misunderstanding? :)
>
> P.S.: What is `lisp-invocation`?
>
> --
> Pierre Neidhardt
> https://ambrevar.xyz/
More information about the asdf-devel
mailing list