From: <tomas@tuxteam.de>
To: guile-user@gnu.org
Subject: Re: [EXT] Option to create statically linked binaries
Date: Wed, 29 Dec 2021 22:22:56 +0100 [thread overview]
Message-ID: <YczRsMzGFTV4dNIV@tuxteam.de> (raw)
In-Reply-To: <CAJ=RwfYMmz_YrsBJ6jB517C26+Ks7J8b7MNrVYvTphwCjhiukg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 893 bytes --]
On Wed, Dec 29, 2021 at 02:52:20PM -0500, Thompson, David wrote:
> Hi Sai,
>
> On Wed, Dec 29, 2021 at 1:14 PM Sai Karthik <kskarthik@disroot.org> wrote:
> >
> > Hello everyone! I'm new to guile. I am exploring the language since a
> > couple of days. It would be nice to have option to produce such binaries
> > for programs built using guile (like with golang & some more langs).
>
> That is not possible. Guile is currently dependent upon having a
> bytecode interpreter installed on the machine that is running Guile
> programs. The good news is that native compilation is something that
> the Guile maintainers have planned for the future, which would enable
> things like self-contained binaries.
On top of that, GNU libc is (at least in parts, libnss I think)
dynamically linked anyway, AFAIK.
My hunch is that Guile's core depends on GNU libc.
Cheers
--
t
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2021-12-29 21:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-29 17:29 Option to create statically linked binaries Sai Karthik
2021-12-29 19:27 ` James Crake-Merani
2021-12-29 20:08 ` Keith Wright
2021-12-30 6:28 ` Sai Karthik
2021-12-29 19:52 ` [EXT] " Thompson, David
2021-12-29 21:22 ` tomas [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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YczRsMzGFTV4dNIV@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=guile-user@gnu.org \
/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.
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).