[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Common Lisp executables: purging spurious reference to libraries?
From: |
Pierre Neidhardt |
Subject: |
Common Lisp executables: purging spurious reference to libraries? |
Date: |
Sun, 02 Dec 2018 12:45:15 +0100 |
User-agent: |
mu4e 1.0; emacs 26.1 |
Hi Guix!
I'm packaging the new rewrite of Next (https://next.atlas.engineer).
It's a Common Lisp application and the executable should be
self-contained, it does not need to depend on SBCL or the like.
However, `guix size next` return the full dependency tree of Common Lisp
libraries.
If I inspect the executable, I see that it contains a bunch of references:
--8<---------------cut here---------------start------------->8---
> strings next | grep sbcl
sbcl_home
sbcl_fallback_sigsegv_handler
sbcl_main
/sbcl.core
Usage: sbcl [runtime-options] [toplevel-options] [user-options]
website <http://www.sbcl.org/>.
More information about SBCL is available at <http://www.sbcl.org/>.
/gnu/store/bbjhsli5dssp2wh9gi9749c9mny46lcy-sbcl-1.4.13/lib/sbcl/
sbcl_home
sbcl_fallback_sigsegv_handler
sbcl_main
to sbcl-devel.~
sbcl_fallback_sigsegv_handler
sbcl_home
sbcl_main
/gnu/store/7jvzkfcjxr6cqb9hvqv2rdcvr18fp7yd-sbcl-next-1.0.0-1.b889934/bin/next-exec.lisp
/gnu/store/n4l31ls9s50v5plws4yq7wq75c9hahm4-sbcl-next-1.0.0-1.b889934-lib/share/common-lisp/sbcl-source/next/source/package.lisp
/gnu/store/dxx2i719izq7jmxxj31c3pxcnhvkfwx6-sbcl-unix-opts-0.1.7/share/common-lisp/sbcl-source/unix-opts/unix-opts.lisp
...
--8<---------------cut here---------------end--------------->8---
I think this is why Guix keeps the Common Lisp libraries in the
closure.
Any idea how to remove them?
--
Pierre Neidhardt
https://ambrevar.xyz/
signature.asc
Description: PGP signature
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Common Lisp executables: purging spurious reference to libraries?,
Pierre Neidhardt <=