From: ludovic.courtes@laas.fr (Ludovic Courtès)
To: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: scm_cell vs threads build option
Date: Mon, 03 Sep 2007 09:28:49 +0200 [thread overview]
Message-ID: <87ps10ryvi.fsf@laas.fr> (raw)
In-Reply-To: <87lkbovccu.fsf@raven.defaultvalue.org> (Rob Browning's message of "Sun\, 02 Sep 2007 17\:09\:21 -0700")
Hi,
Rob Browning <rlb@defaultvalue.org> writes:
> This is potentially bad (for Debian at least). I'll have to
> investigate, but it may mean that I will have to revert Debian's build
> for now so that it doesn't enable threads.
Can't you, for instance, change the Libtool interface number for
`libguile'? That's ugly, and would require recompilation of all
packages depending on it, but at least it would allow you to produce
thread-enabled packages for the remainder of 1.8.x.
> The problem is that Guile 1.8 in Etch was compiled without threads
> (due to some serious problems at the time).
OTOH, I don't remember seeing any "serious" thread-related bug fix since
1.8.0. Or did I miss it?
Thanks,
Ludovic.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2007-09-03 7:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-02 0:33 scm_cell vs threads build option Kevin Ryde
2007-09-03 0:09 ` Rob Browning
2007-09-03 7:28 ` Ludovic Courtès [this message]
2007-09-04 5:22 ` Rob Browning
2007-09-04 0:46 ` Kevin Ryde
2007-09-03 7:34 ` 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=87ps10ryvi.fsf@laas.fr \
--to=ludovic.courtes@laas.fr \
--cc=guile-devel@gnu.org \
--cc=rlb@defaultvalue.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).