Gentoo Archives: gentoo-desktop

From: "V. Ram" <vramml0@××××××××.fm>
To: gentoo-desktop@l.g.o
Subject: [gentoo-desktop] kde-sunset: gtk-engines-qt build failure
Date: Thu, 13 Oct 2011 22:06:40
Message-Id: 1318543566.3346.140660985677485@webmail.messagingengine.com
1 I finally got KDE 3.5.10 built and installed, after keywording kdelibs,
2 kcontrol, gdk-pixbuf, and libpng. Revdep-rebuild appears to have done
3 the trick with the upgrade to libpng.
4
5 Now I'm trying to install gtk-engines-qt, whose build fails with the
6 indicated error:
7
8 In file included from /usr/include/glib-2.0/gio/gio.h:54:0,
9 from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
10 from /usr/include/gtk-2.0/gdk/gdk.h:32,
11 from /usr/include/gtk-2.0/gdk/gdkprivate.h:30,
12 from /usr/include/gtk-2.0/gdk/gdkx.h:30,
13 from
14 /tmp/portage/x11-themes/gtk-engines-qt-0.8-r4/work/gtk-qt-engine/src/qt_qt_wrapper.cpp:18:
15 /usr/include/glib-2.0/gio/gdbusintrospection.h: At global scope:
16 /usr/include/glib-2.0/gio/gdbusintrospection.h:151:25: error: expected
17 unqualified-id before ‘protected’
18 /usr/include/glib-2.0/gio/gdbusintrospection.h:151:25: error: expected
19 ‘;’ before ‘protected’
20
21 The system glib is 2.28.8 and gtk+ is at 2.24.4 .
22
23 I think this may be due to a conflicting use of the keyword "signals"
24 between Qt and GLib (or gtk).
25
26 Nokia (for now) has a guide on what to do about this:
27
28 http://www.developer.nokia.com/Community/Wiki/How_to_prevent_symbol_collisions_between_GTK%2B_and_Qt
29
30 There are a couple of bug reports along similar lines in the Debian bug
31 tracker:
32
33 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627016
34 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614436
35
36 kde-sunset devs: could you please address this in a subsequent rev of
37 the theming engine package?
38
39 Thank you very much.
40
41 --
42 http://www.fastmail.fm - Accessible with your email software
43 or over the web

Replies

Subject Author
Re: [gentoo-desktop] kde-sunset: gtk-engines-qt build failure "V. Ram" <vramml0@××××××××.fm>