This is my first bug post (so this might not be the right place for it). Here goes. I'm trying to update gnome-2.8.2 to gnome-2.10-r1. The first seven packages emerged successfully. At this point gnome-session-2.10.0-r2 files during the ./configure process. I saw some error message related to looking for the disable-esd flag. As a result of this I went and added the "-esd" USE flag... but with the same results. Reproducible: Always Steps to Reproduce: 1. emerge gnome-session 2. 3. Actual Results: The ./configure stage of the ebuild fails: Expected Results: Compilation should of completed swamp gnome-session-2.10.0 # emerge info Portage 2.0.51.22-r2 (default-linux/x86/2005.0, gcc-3.3.5, glibc-2.3.4.20041102-r1, 2.4.28-gentoo-r8 i686) ================================================================= System uname: 2.4.28-gentoo-r8 i686 AMD Athlon(tm) XP 1800+ Gentoo Base System version 1.4.16 dev-lang/python: 2.3.4-r1 sys-apps/sandbox: 1.2.10 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.4 sys-devel/binutils: 2.15.92.0.2-r7 sys-devel/libtool: 1.5.10-r4 virtual/os-headers: 2.6.8.1-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O3 -mcpu=athlon-xp -march=athlon-xp -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/sha re/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -mcpu=athlon-xp -march=athlon-xp -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 3dnow X alsa apm avi berkdb bitmap-fonts cdr crypt cups curl eds emboss encode esd fam flac foomaticdb fortran gd g dbm gif gnome gphoto2 gpm gstreamer gtk gtk2 imlib ipv6 java jpeg libg++ libwww mad mikmod mmx motif mozilla mp3 mpeg ncurse s nfs nls ogg oggvorbis opengl oss pam pdflib perl png postgres python quicktime readline samba sdl shorten slang slp speex spell sse ssl svga tcpd tiff truetype truetype-fonts type1-fonts vorbis xml2 xmms xprint xv zlib userland_GNU kernel_linux e libc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
Created attachment 64012 [details] The config.log of the failed build attempt This is the config.log file from a result os using the following command: 'USE="-esd" emerge -v gnome-session'. The same results happen if I leave the esd USE field enabled.
I have gone through the config.log and the console output. and have found the following error is what is causing it to fail: ./configure: line 20694: syntax error near unexpected token `echo' ./configure: line 20694: `echo "$as_me:$LINENO: checking whether ESounD support is requested" >&5' Here's what the code looks like: 20694 PKG_PROG_PKG_CONFIG() 20695 20696 20697 echo "$as_me:$LINENO: checking whether ESounD support is requested" >&5 20698 echo $ECHO_N "checking whether ESounD support is requested... $ECHO_C" >&6 20699 # Check whether --enable-esd or --disable-esd was given. 20700 if test "${enable_esd+set}" = set; then 20701 enableval="$enable_esd" 20702 enable_esd=$enableval 20703 else 20704 enable_esd=yes 20705 fi; 20706 echo "$as_me:$LINENO: result: $enable_esd" >&5 20707 echo "${ECHO_T}$enable_esd" >&6 *IF* I comment out lines 20697 and 20698 the ./configure process finishes normally! I'm not a programmer... so I'm not sure how to resolve this issue or how to file a patch (though I've applied patches before).
I had searched the bugzilla site here but could not find any other matches. I went to forums.gentoo.org and found one person with a similar issue to mine... but with a different error -- see bug 99559. I used some advise found in this forum posting to resolve my problem. Here's what I did: 1. Started emerge using 'emerge -v gnome-session' 2. Waiting until just prior to ./configure to be run and then hit CTRL+Z (to stop/pause the process. 3. Went and edited the configure file in /var/tmp/portage/gnome-session-2.10.0-r2/work/gnome-session-2.10.0-r2/ and commented out lines 20697 and 20698. 4. Typed 'fg' to continue the emerge. 5. Gnome-session is now emerged and installed!
Thank you for reporting this issue. The information given on comment #2 was very helpful. However, this bug has already been reported, so please follow the discussion on bug #99580. *** This bug has been marked as a duplicate of 99580 ***
