From: "Ludovic Courtès" <ludo@gnu.org>
To: raingloom <raingloom@riseup.net>
Cc: guix-devel@gnu.org
Subject: Re: initrd: why do we need static linking?
Date: Wed, 06 May 2020 16:13:27 +0200 [thread overview]
Message-ID: <871rnxi22g.fsf@gnu.org> (raw)
In-Reply-To: <20200505215948.3b2c1e2a@riseup.net> (raingloom@riseup.net's message of "Tue, 5 May 2020 21:59:48 +0200")
Hi,
raingloom <raingloom@riseup.net> skribis:
> It'd actually be nice if static linking could be used in places other
> than the initrd. I'm experimenting with some old resource constrained
> machines, and it made me realize just how much space even a basic `guix
> pull` can take up.
That’s an issue in Guile’s compiler that Andy has been working on
recently. Static linking won’t help you.
More generally, shared libraries (dynamic linking) are a way to save
memory: those libraries are shared, meaning they can be loaded only once
in memory even if there are many processes using them.
Ludo’.
prev parent reply other threads:[~2020-05-06 14:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-04 6:34 initrd: why do we need static linking? Ricardo Wurmus
2020-05-05 9:33 ` Ludovic Courtès
2020-05-05 19:59 ` raingloom
2020-05-06 14:13 ` Ludovic Courtès [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871rnxi22g.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=raingloom@riseup.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).