From: David Pirotte <david@altosw.be>
To: Aljosha Papsch <lists@rpapsch.de>
Cc: guile-user@gnu.org
Subject: Re: guile-gnome and guile 2
Date: Sun, 11 Aug 2013 12:53:28 -0300 [thread overview]
Message-ID: <20130811125328.2df1daf7@capac> (raw)
In-Reply-To: <1376148116.2142.3.camel@creek.rivers>
> This is due to recent Glib only allowing glib.h to be included directly.
> Any old program which does this will get this compilation error. So, the
> solution for you would be to find all occurences in guile-gnome where
> another Glib header is included and remove it (or replace it with glib.h
> if needed). But maybe this was already done in Git?
yes, it has been fixed in git, see f37f03bb957701d80a1c3977b3f0f3995b6ec655
prev parent reply other threads:[~2013-08-11 15:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-09 17:26 guile-gnome and guile 2 Diogo F. S. Ramos
2013-08-09 17:40 ` David Pirotte
2013-08-09 17:57 ` Diogo F. S. Ramos
2013-08-09 18:31 ` David Pirotte
2013-08-09 18:51 ` Diogo F. S. Ramos
2013-08-09 20:20 ` David Pirotte
2013-08-10 15:21 ` Aljosha Papsch
2013-08-11 15:53 ` David Pirotte [this message]
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=20130811125328.2df1daf7@capac \
--to=david@altosw.be \
--cc=guile-user@gnu.org \
--cc=lists@rpapsch.de \
/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).