| Summary: | gconf-2.14.0 fails to build with glib and GTK+ version conflicts | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Romain Guillebert <hardshooter> |
| Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | eva, srikantmarakani, syslock |
| Priority: | High | ||
| Version: | 2006.0 | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 119872 | ||
|
Description
Romain Guillebert
2006-03-19 08:54:46 UTC
Portage 2.0.54 (default-linux/x86/2006.0, gcc-3.4.5, glibc-2.3.5-r2, 2.6.15-gentoo-r1 i686) ================================================================= System uname: 2.6.15-gentoo-r1 i686 AMD Athlon(tm) processor Gentoo Base System version 1.6.14 dev-lang/python: 2.4.2 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.16.1 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O0 -march=athlon -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O0 -march=athlon -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/" LANG="fr_FR.iso-8859-15" LC_ALL="fr_FR.iso-8859-15" LINGUAS="fr" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 X alsa apache2 apm audiofile avi berkdb bitmap-fonts bzip2 cdr cli crypt ctype cups curl dba dri dvd eds emboss encode esd expat fastbuild foomaticdb force-cgi-redirect fortran ftp gd gdbm gif gnome gpm gstreamer gtk gtk2 imlib ipv6 jpeg libg++ libwww mad memlimit mikmod motif mp3 mpeg msn ncurses nls nptl nptlonly ogg opengl oss pam pcre pdflib perl png posix python quicktime readline sdl session simplexml soap sockets spell spl ssl tcltk tcpd tiff tokenizer truetype truetype-fonts type1-fonts udev vorbis w32codecs xml xml2 xmms xsl xv zlib linguas_fr userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LDFLAGS, PORTDIR_OVERLAY During the compilation of gconf-2.14.0 : /usr/include/gtk-2.0/gtk/gtkstatusbar.h:68: erreur: erreur de syntaxe avant « GMemChunk » /usr/include/gtk-2.0/gtk/gtkstatusbar.h:68: attention : pas de point virgule à la fin de la structure ou de l'union /usr/include/gtk-2.0/gtk/gtkstatusbar.h:82: erreur: erreur de syntaxe avant un élément lexical « } » make[2]: *** [basic-gconf-app.o] Erreur 1 make[2]: *** Attente des tâches non terminées.... make[2]: Leaving directory `/var/tmp/portage/gconf-2.14.0/work/GConf-2.14.0/examples' make[1]: *** [all-recursive] Erreur 1 make[1]: Leaving directory `/var/tmp/portage/gconf-2.14.0/work/GConf-2.14.0' make: *** [all] Erreur 2 !!! ERROR: gnome-base/gconf-2.14.0 failed. !!! Function gnome2_src_compile, Line 56, Exitcode 2 !!! compile failure !!! If you need support, post the topmost build error, NOT this status message. i can't read what it says, but i'm willing to bet you are using an older gtk version ( like 2.8.6 ). First update gtk and try again. Thanks please also report what version of gtk+ you are using now. I was using gtk+-2.8.8 I'm trying with the last version Thx i have updated gtk+ and that work not fixed until the gtk dep is updated. However it seems those bits need a glib-2.10, so the real issue probably is you had glib-2.10 but gtk+ wasn't updated yet. Can you post (relevant bits) of /var/log/emerge.log ? The glib dep was updated, and the GTK+ dep had to be updated as a result. Marking this as fixed. well.. it is not that simple, the error stems from a discrepancy between glib and gtk+ versions afaics. Just updating the deps is not the correct solution. *** Bug 131923 has been marked as a duplicate of this bug. *** well, how is this going ? Not the esthetical correct solution, but it works in all common use cases apparently. We'll stick with it. *** Bug 145275 has been marked as a duplicate of this bug. *** |
