From: Kevin Ryde <user42@zip.com.au>
Cc: guile-user@gnu.org
Subject: Re: guile-gnome and guile-gtk
Date: Wed, 22 Feb 2006 08:44:24 +1100 [thread overview]
Message-ID: <87wtfojsjr.fsf@zip.com.au> (raw)
In-Reply-To: <1140493679.29123.31.camel@vandvndr.physics.uiuc.edu> (Aaron VanDevender's message of "Mon, 20 Feb 2006 21:47:59 -0600")
Aaron VanDevender <sig@netdot.net> writes:
>
> I should have qualified that to say that guile-gtk doesn't build due to
> the autoconf thing.
If that's guile gtk 1.2 then bug reports to the mailing list please.
I don't think anything has changed in gtk 1.2 for a long time, it's
supposed to all go.
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2006-02-21 21:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-20 18:20 guile-gnome and guile-gtk Aaron VanDevender
2006-02-21 3:47 ` Aaron VanDevender
2006-02-21 10:59 ` Bill Schottstaedt
2006-02-21 13:35 ` Greg Troxel
2006-02-21 21:44 ` Kevin Ryde [this message]
2006-02-21 11:31 ` David Pirotte
2006-02-28 11:05 ` Andy Wingo
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=87wtfojsjr.fsf@zip.com.au \
--to=user42@zip.com.au \
--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).