From: Caleb Ristvedt <caleb.ristvedt@cune.org>
To: Matt Wette <matt.wette@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: Running guile single-threaded?
Date: Sun, 17 May 2020 11:58:40 -0500 [thread overview]
Message-ID: <87o8qmlcqn.fsf@cune.org> (raw)
In-Reply-To: <d226c8a3-f66c-b47a-8802-c3972de6c417@gmail.com> (Matt Wette's message of "Sun, 17 May 2020 08:39:54 -0700")
> I don't this is possible without building guile using --without-threads
> argument to configure. Otherwise, the mutl-threaded gc is included.
Good to know, thanks. I'll have to figure out a way to use clone+exec
safely, then (calling process is multi-threaded), probably by writing an
extension in C.
- reepca
next prev parent reply other threads:[~2020-05-17 16:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-17 15:27 Running guile single-threaded? Caleb Ristvedt
2020-05-17 15:39 ` Matt Wette
2020-05-17 16:58 ` Caleb Ristvedt [this message]
2020-05-30 21:27 ` Ludovic Courtès
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=87o8qmlcqn.fsf@cune.org \
--to=caleb.ristvedt@cune.org \
--cc=guile-user@gnu.org \
--cc=matt.wette@gmail.com \
/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).