From: Andy Wingo <wingo@pobox.com>
To: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: Thread+GC issues on ARM
Date: Wed, 16 Jan 2013 11:28:00 +0100 [thread overview]
Message-ID: <87a9s9jubz.fsf@pobox.com> (raw)
In-Reply-To: <87mx8qghsc.fsf@trouble.defaultvalue.org> (Rob Browning's message of "Fri, 10 Feb 2012 21:39:31 -0600")
Hi Rob,
On Sat 11 Feb 2012 04:39, Rob Browning <rlb@defaultvalue.org> writes:
> Neil Jerram <neil@ossau.homelinux.net> writes:
>
>> Rob Browning <rlb@defaultvalue.org> writes:
>
>>> So do I understand correctly that in order for this to work, we'll first
>>> need an updated libgc in Debian unstable?
>>
>> Yes.
>
> Great. If we can get this and the s390 problem fixed, I'll be able to
> see about removing 1.8 from Debian testing (which I'd love to do soon --
> I'd really like to drop 1.8 from the upcoming release).
What happened here? I see that the libgc in the upcoming release is
still 7.1, released in 2008, whereas 7.2 was released in May 2012. It's
really unfortunate, given the large number of threading-related problems
fixed by a non-ancient libgc.
See also: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673965
Regards,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2013-01-16 10:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-24 12:50 Thread+GC issues on ARM Neil Jerram
2012-01-07 1:39 ` Andy Wingo
2012-01-07 3:32 ` Rob Browning
2012-01-07 12:01 ` Neil Jerram
2012-01-07 12:35 ` Neil Jerram
2012-01-07 17:52 ` Rob Browning
2012-01-08 10:28 ` Neil Jerram
2012-02-11 3:39 ` Rob Browning
2012-02-11 9:58 ` Neil Jerram
2012-02-11 13:10 ` Neil Jerram
2012-02-11 17:39 ` Rob Browning
2012-02-13 22:22 ` Neil Jerram
2012-02-11 17:38 ` Rob Browning
2013-01-16 10:28 ` Andy Wingo [this message]
2012-01-07 16:48 ` Rob Browning
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=87a9s9jubz.fsf@pobox.com \
--to=wingo@pobox.com \
--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).