Bug 140692 – gnome-python-desktop fails to compile.

• Status: RESOLVED INVALID
• Product: Gentoo Linux

[Description Paul Giblock 2006-07-16 13:05:28 UTC]

This bug follows from the issue originally posted on the gentoo forums at: http://forums.gentoo.org/viewtopic-p-3452576.html#3452576 

emerge gnome fails on gnome-python-desktop. 

My emerge --info:

Gentoo Base System version 1.12.1
Portage 2.1.1_pre2-r8 (default-linux/amd64/2006.0, gcc-3.4.4/amd64-vanilla, glibc-2.4-r3, 2.6.15-gentoo-r8 x86_64)
=================================================================
                       System Settings
=================================================================
System uname: 2.6.15-gentoo-r8 x86_64 AMD Athlon(tm) 64 Processor 3500+
app-admin/eselect-compiler: 2.0.0_rc2-r1
dev-lang/python:     2.4.3-r1
dev-python/pycrypto: 2.0.1-r5
dev-util/ccache:     [Not Present]
dev-util/confcache:  [Not Present]
sys-apps/sandbox:    1.2.12
sys-devel/autoconf:  2.13, 2.60
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2
sys-devel/binutils:  2.17
sys-devel/gcc-config: 2.0.0_rc1
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.16
ACCEPT_KEYWORDS="amd64 ~amd64"
AUTOCLEAN="yes"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=athlon64 -O3 -pipe -msse -msse2 -mmmx -m3dnow"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/share/X11/xkb"
CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/eselect/compiler /etc/gconf /etc/java-config/vms/ /etc/terminfo"
CXXFLAGS="-march=athlon64 -O3 -pipe -msse -msse2 -mmmx -m3dnow"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distlocks metadata-transfer sandbox sfperms strict"
GENTOO_MIRRORS="http://adelie.polymtl.ca/ http://mirrors.tds.net/gentoo ftp://mirrors.tds.net/gentoo http://gentoo.osuosl.org http://www.ibiblio.org/pub/Linux/distributions/gentoo"
PKGDIR="/usr/portage/packages"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude='/distfiles' --exclude='/local' --exclude='/packages'"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/portage/local/layman/portage-xgl"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="amd64 X alsa avi berkdb bitmap-fonts cairo cdr cli crypt cups dlloader dri dvd dvdr eds emboss encode esd foomaticdb fortran freetype gif gnome gpm gstreamer gtk gtk2 imlib ipv6 isdnlog joystick jpeg kde lzw lzw-tiff mp3 mpeg ncurses nls nptl nptlonly nvidia ogg opengl pam pcre pdflib perl png pppd python qt qt3 qt4 quicktime readline reflection sdl session spell spl ssl tcpd tiff truetype truetype-fonts type1-fonts usb vcd vorbis xmms xorg xpm xv zlib elibc_glibc input_devices_keyboard input_devices_mouse input_devices_evdev input_devices_joystick kernel_linux userland_GNU video_cards_nv video_cards_nvidia video_cards_vesa"
Unset:  CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, MAKEOPTS, PORTAGE_RSYNC_EXTRA_OPTS

[Comment 1 Paul Giblock 2006-07-16 13:07:54 UTC]

Created attachment 91926 [details]
My stdout and stderr output of the compile

Seems to fail in metacity.

[Comment 2 Paul Giblock 2006-07-16 19:33:15 UTC]

Comment on attachment 91926 [details]
My stdout and stderr output of the compile

Removing the two troubled lines avoids the problems. Looks like those two symbols are just not declared for whatever reason.

[Comment 3 William Keaney 2006-07-16 19:45:31 UTC]

(In reply to comment #2)
> (From update of attachment 91926 [details] [edit])
> Removing the two troubled lines avoids the problems. Looks like those two
> symbols are just not declared for whatever reason.
> 

What version of metacity are you using?  It has been suggested in the above-referenced forum thread that the version from coffee's xgl overlay is to blame.  If you're using that, try emerging the stable version from portage.

[Comment 4 Erik Andrén 2006-07-20 09:55:40 UTC]

(In reply to comment #3)
> (In reply to comment #2)
> > (From update of attachment 91926 [details] [edit] [edit])
> > Removing the two troubled lines avoids the problems. Looks like those two
> > symbols are just not declared for whatever reason.
> > 
> 
> What version of metacity are you using?  It has been suggested in the
> above-referenced forum thread that the version from coffee's xgl overlay is to
> blame.  If you're using that, try emerging the stable version from portage.
> 

I can confirm that you need to emerge the regular metacity to emerge the gnome-python-desktop and not the portage-xgl overlay.

[Comment 5 Saleem Abdulrasool (RETIRED) 2006-12-01 01:46:01 UTC]

We do not support the overlay ebuilds.