unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: guile-devel <guile-devel@gnu.org>
Subject: guile 2.2 will require libgc 7.2
Date: Sun, 20 Jan 2013 12:47:11 +0100	[thread overview]
Message-ID: <87vcasaxfk.fsf@pobox.com> (raw)

Hi,

After talking with Ludovic in IRC, I updated the dependency on libgc in
"master" to require libgc 7.2, released in its final version on March
2012.  The ifdeffery was making it difficult to make needed changes, as
the older versions were lacking some needed interfaces, and making stubs
was introducing bugs.  Libgc 7.2 also seems to have fewer bugs when run
in a multi-threaded mode.

Debian users will probably want to install libgc by hand.  I am a
terrible person and just install it over my system's copy, as they are
binary-compatible.  Hopefully someone packages it soon, though I dispair
a bit:

    http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673965

Users of other platforms mostly have the newer libgc already.

This does not affect the 2.0.x release series.

Regards,

Andy
-- 
http://wingolog.org/



                 reply	other threads:[~2013-01-20 11:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=87vcasaxfk.fsf@pobox.com \
    --to=wingo@pobox.com \
    --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).