From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@openembedded.org,
"Michael 'Mickey' Lauer" <mickey@vanille-media.de>
Subject: Re: Gtk+ 2.6.10 w/ newer Glibs
Date: Sat, 13 Jan 2007 09:52:39 +0000 [thread overview]
Message-ID: <1168681959.5868.4.camel@localhost.localdomain> (raw)
In-Reply-To: <1888834532.20070112204308@vanille-media.de>
On Fri, 2007-01-12 at 20:43 +0100, Michael 'Mickey' Lauer wrote:
> Since .dev upgraded gnome-vfs and removed gnome-vfs-dbus, gnome-vfs is
> no longer buildable against an old (<= 2.9.4) glib. Gtk+ 2.6.10 (which is still
> in wide use today) again is not buildable against newer glib variants.
>
> Any glib / Gtk+ experts to fix the problem? The first issue out is
> here:
I asked someone:
> | arm-linux-gcc ... -DG_DISABLE_DEPRECATED
G_DISABLE_DEPRECATED tells GLib to hide all deprecated functions. They
still exist in the library, but they are hidden in the headers. It's
considered bad form to do this in release code, because sometimes people
want to run older apps against newer libraries.
> | ../../../gtk/gtkstatusbar.h:68: error: expected
specifier-qualifier-list before 'GMemChunk'
GMemChunk was deprecated in GLib 2.10.
To fix this there needs to be a patch that removes
-DG_DISABLE_DEPRECATED from every Makefile.am.
Cheers,
Richard
next prev parent reply other threads:[~2007-01-13 9:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-12 19:43 Gtk+ 2.6.10 w/ newer Glibs Michael 'Mickey' Lauer
2007-01-12 20:25 ` Koen Kooi
2007-01-13 0:13 ` Michael 'Mickey' Lauer
2007-01-13 9:52 ` Richard Purdie [this message]
2007-01-13 16:15 ` Koen Kooi
[not found] ` <200701132239.31919.alban@mycroft1.plus.com>
2007-01-13 23:35 ` Angstrom cannot buile portabase Holger Freyther
2007-01-14 0:12 ` Koen Kooi
2007-01-14 9:15 ` GoXbox Live
2007-01-14 10:16 ` Koen Kooi
2007-01-14 10:42 ` GoXbox Live
2007-01-14 9:55 ` Paul Sokolovsky
2007-01-25 23:24 ` Gtk+ 2.6.10 w/ newer Glibs Michael 'Mickey' Lauer
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=1168681959.5868.4.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=mickey@vanille-media.de \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.