From: Romel Sandoval <romel@lavabit.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-user@gnu.org
Subject: Re: Failing to build g-wrap for guile 1.9.10
Date: Wed, 02 Jun 2010 19:06:10 -0500 [thread overview]
Message-ID: <1275523570.3984.2.camel@romel-compaq> (raw)
In-Reply-To: <87d3wa8kcg.fsf@gnu.org>
I'm trying to build G-Wrap because guile-gnome depends on it.
El mié, 02-06-2010 a las 00:21 +0200, Ludovic Courtès escribió:
> Hi,
>
> This won’t answer your question, but if you’re using 1.9, you may want
> to look at the dynamic FFI in (system foreign) instead of G-Wrap.
>
> Thanks,
> Ludo’.
next prev parent reply other threads:[~2010-06-03 0:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-31 23:38 Failing to build g-wrap for guile 1.9.10 Romel Sandoval
2010-06-01 9:20 ` Andy Wingo
2010-06-01 18:44 ` Romel Sandoval
2010-06-01 22:21 ` Ludovic Courtès
2010-06-03 0:06 ` Romel Sandoval [this message]
2010-06-02 7:31 ` Andy Wingo
2010-06-02 19:29 ` Andreas Rottmann
2010-06-03 0:18 ` Romel Sandoval
2010-06-03 12:00 ` Andreas Rottmann
2010-06-03 13:57 ` Romel Sandoval
2010-06-03 14:36 ` Andreas Rottmann
2010-06-03 16:19 ` Romel Sandoval
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=1275523570.3984.2.camel@romel-compaq \
--to=romel@lavabit.com \
--cc=guile-user@gnu.org \
--cc=ludo@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).