From: Rob Browning <rlb@defaultvalue.org>
To: guile-devel@gnu.org
Subject: Re: scm_cell vs threads build option
Date: Mon, 03 Sep 2007 22:22:57 -0700 [thread overview]
Message-ID: <87fy1v2edq.fsf@raven.defaultvalue.org> (raw)
In-Reply-To: 87ps10ryvi.fsf@laas.fr
ludovic.courtes@laas.fr (Ludovic Courtès) writes:
> 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.
That doesn't really help unless it's handled officially upstream.
i.e. I believe a given SONAME for a given library name on a given
platform should always produce the exact same ABI.
>> 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?
If I recall correctly, the problem was that "make check" was failing
when threads were enabled. I re-enabled threads because it looked
like the problem may have been fixed (perhaps indirectly) in 1.8,.2,
and I wanted to test that in unstable.
--
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2007-09-04 5:22 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
2007-09-04 5:22 ` Rob Browning [this message]
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=87fy1v2edq.fsf@raven.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=guile-devel@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).