unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Andrew Bernard <andrew.bernard@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: SLIB and guile 2
Date: Thu, 31 Jan 2013 19:01:08 -0500	[thread overview]
Message-ID: <87mwvogawr.fsf@tines.lan> (raw)
In-Reply-To: <510B0124.9050204@gmail.com> (Andrew Bernard's message of "Fri, 01 Feb 2013 10:41:24 +1100")

Hi Andrew,

Andrew Bernard <andrew.bernard@gmail.com> writes:
> Does SLIB work with guile 2?
>
> With guile 2.0.7 and slib 3b3 on Linux there appear to be
> incompatibilities. Are there releases that work together?

Andy Wingo recently posted a patch to get slib working with Guile 2.0.
Hopefully a variant of it will be accepted upstream soon.

http://lists.gnu.org/archive/html/guile-user/2013-01/msg00014.html

     Mark



  reply	other threads:[~2013-02-01  0:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-31 23:41 SLIB and guile 2 Andrew Bernard
2013-02-01  0:01 ` Mark H Weaver [this message]
2013-02-01 13:57   ` Andy Wingo
2013-02-01  4:09 ` Jay Sulzberger

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=87mwvogawr.fsf@tines.lan \
    --to=mhw@netris.org \
    --cc=andrew.bernard@gmail.com \
    --cc=guile-user@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).