unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: <tomas@tuxteam.de>
To: guile-user@gnu.org
Subject: Re: Is it possible to write program only in Guile?
Date: Thu, 19 Oct 2023 06:52:40 +0200	[thread overview]
Message-ID: <ZTC2GLwwTd8cPFcP@tuxteam.de> (raw)
In-Reply-To: <rmi7cnkm1o2.fsf@s1.lexort.com>

[-- Attachment #1: Type: text/plain, Size: 1126 bytes --]

On Wed, Oct 18, 2023 at 10:43:25AM -0400, Greg Troxel wrote:
> CToID <funk443@yandex.com> writes:
> 
> > How do I distribute Guile programs to somebody who doesn't have Guile
> > installed on their system?  It does not seem like Guile compiler is
> > able to produce a standalone executable.
> 
> The same way you distribute Java programs, python programs and perl
> programs.  You ask they they install the langauge environment as part of
> your instructions

And -- at the end of the day -- C programs: libc (or equivalent) and
the runtime aren't trivial either. Unless you are doing embedded stuff.

In Linux, for example, a "C executable" (a binary compiled from C)
isn't that different from a shell script, if you squint. While in
a shell script you have that shebang line stating "I want to be
interpreted by /bin/foo", the executable says "I want to be loaded
by /lib/ld-linux.so" (the dynamic loader) or something similar.

Actually, AFAIK, the Guile compiler compiles down to dynamic objects
these days. But you need that pesky runtime...

It's turtles all the way down :-)

Cheers
-- 
t

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  parent reply	other threads:[~2023-10-19  4:52 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-18 10:23 Is it possible to write program only in Guile? CToID
2023-10-18 12:51 ` Basile Starynkevitch
2023-10-18 13:31   ` CToID
2023-10-18 13:36     ` Basile Starynkevitch
2023-10-18 14:43     ` Greg Troxel
2023-10-18 15:06       ` CToID
2023-10-18 15:50         ` Hans Åberg
2023-10-18 20:24           ` Janneke Nieuwenhuizen
2023-10-18 16:11         ` Thompson, David
2023-10-19  4:52       ` tomas [this message]
2023-10-19 11:18         ` wolf
2023-10-20  4:35           ` tomas
2023-10-18 13:10 ` Olivier Dion
2023-10-18 13:32   ` Marc Chantreux
2023-10-18 13:44     ` Olivier Dion
2023-10-18 18:49       ` wolf
2023-10-18 19:14         ` Olivier Dion
2023-10-20 10:19         ` Marc Chantreux
2023-10-18 13:12 ` Zelphir Kaltstahl

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=ZTC2GLwwTd8cPFcP@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).