unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Keith Wright <kwright@keithdiane.us>
To: Jean Abou Samra <jean@abou-samra.fr>
Cc: r.herdt@posteo.de, guile-user@gnu.org
Subject: What is needed to compile Guile?
Date: Wed, 22 Nov 2023 20:09:13 -0500	[thread overview]
Message-ID: <87sf4xl1hi.fsf@keithdiane.us> (raw)
In-Reply-To: <BA318183-0369-4714-A4DE-A9D587BE9524@abou-samra.fr> (message from Jean Abou Samra on Mon, 20 Nov 2023 18:46:36 +0100)

Jean Abou Samra <jean@abou-samra.fr> writes:

>> and  have no idea how to set LIBFFI
>> to avoid the need to call it.
>
> Don't, this is too complicated.

Thank you for your consise and correct advice.

I have compiled Guile 3 from tarball and verified that
it can still evaluate the program I was working on last year.

I have put that program on a web page:

  http://www.free-comp-shop.com/texscm.html

I also wrote some notes on what it took to compile Guile.
Maybe parts of it could be copied into the README or INSTALL
files.  Please copy what you need; don't link.  I have nothing
to sell and don't need traffic.

  http://www.free-comp-shop.com/guile.html

Hope this helps.

  -- Keith
  



      reply	other threads:[~2023-11-23  1:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-20  3:01 What libunistring does guile need? Keith Wright
2023-11-20 10:28 ` Ricardo G. Herdt
2023-11-20 17:17   ` What does Guile need to compile? (What libunistring does guile need?) Keith Wright
2023-11-20 17:46     ` Jean Abou Samra
2023-11-23  1:09       ` Keith Wright [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=87sf4xl1hi.fsf@keithdiane.us \
    --to=kwright@keithdiane.us \
    --cc=guile-user@gnu.org \
    --cc=jean@abou-samra.fr \
    --cc=r.herdt@posteo.de \
    /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).