From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libglib2: bump version number to 2.22
Date: Tue, 24 Nov 2009 19:55:18 +0100 [thread overview]
Message-ID: <877htfda7d.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1259073157-19511-1-git-send-email-daniel@caiaq.de> (Daniel Mack's message of "Tue\, 24 Nov 2009 15\:32\:37 +0100")
>>>>> "Daniel" == Daniel Mack <daniel@caiaq.de> writes:
Daniel> When building gvfs, I encountered the following error:
Daniel> checking for GLIB... configure: error: Package requirements (glib-2.0 >= 2.21.2 gthread-2.0 gobject-2.0 gmodule-no-export-2.0 gio-unix-2.0 gio-2.0 ) were not met:
Daniel> Requested 'glib-2.0 >= 2.21.2' but version of GLib is 2.20.5
Thanks, but the new libglib2 version needs ipv6 support to build and
might cause other problems, so I'm selecting the safe option and simply
revert the gvfs update for now.
We can do the update after 2009.11.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-11-24 18:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-24 14:32 [Buildroot] [PATCH] libglib2: bump version number to 2.22 Daniel Mack
2009-11-24 18:55 ` Peter Korsgaard [this message]
2009-12-26 16:00 ` [Buildroot] [PATCH] libglib2: bump to 2.22.3 Lionel Landwerlin
2010-01-28 16:08 ` Peter Korsgaard
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877htfda7d.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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