I've been unable to get openmotif-2.1.30-r4, and now 2.1.30-r5 to emerge on my main PC, however, I was able to get it to emerge on my laptop - and I'm unable to spot what difference is causing this behaviour. My system was originally an 'x86' arch system, hence trying to emerge 2.1.30-r4, but after I was unsuccsessful in emerging this I re-emerged the entire system to '~x86' and tried again. Still, 2.1.30-r5 would not emerge with an identical problem. I've tried with various USE flags so far - going as far as having no USE flags at all, as well as trying disabling distcc, ccache, sandbox & userprivs, but none of this has any effect. Several emerge sync's have been done since I started having the problem to update the portage tree, and I've removed the downloaded openmotif source tarball to force a redownload to no effect. Any ideas gratefully received at this point :) Reproducible: Always Steps to Reproduce: 1. Built system (see attached world file) 2. Tried to emerge opera (openmotif was a dependency) - failed 3. Tried to emerge openmotif on its own - failed Actual Results: The emerge always fails - see attached logfile (apologies for the ANSI codes in the log, it was produced with nohup) Portage 2.0.50-r1 (default-x86-2004.0, gcc-3.3.3, glibc-2.3.3_pre20040207-r0, 2.6.3-gentoo-r1) ================================================================= System uname: 2.6.3-gentoo-r1 i686 AMD Athlon(tm) XP 3200+ Gentoo Base System version 1.4.3.13p1 distcc 2.13 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] Autoconf: sys-devel/autoconf-2.59-r3 Automake: sys-devel/automake-1.8.3 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-march=athlon-xp -O3 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=athlon-xp -O3 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache distcc sandbox" GENTOO_MIRRORS="ftp://ftp.easynet.nl/mirror/gentoo ftp://ftp.gentoo.skynet.be/pub/gentoo/ ftp://trumpetti.atm.tut.fi/gentoo/ ftp://ftp.uni-erlangen.de/pub/mirrors/gentoo ftp://ftp.mirror.ac.uk/sites/www.ibiblio.org/gentoo/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://oracle/gentoo-portage" USE="3dnow X acpi apache2 apm arts avi berkdb cdr crypt cups directfb distcc dvd dvdr encode esd foomaticdb freetype gdbm gif gnome gpm gtk gtk2 imlib java jpeg kde libg++ libwww mad mikmod motif mozilla mpeg mysql ncurses nls oggvorbis opengl oss pam pdflib perl png ppds python qt quicktime readline scanner sdl slang spell ssl svga tcpd truetype usb v4l x86 xml2 xmms xv zlib"
Created attachment 28672 [details] Full emerge output from 'emerge -v openmotif' This is the full output of `emerge -v openmotif` captured by nohup - apologies for the ANSI gunk at the beginning.
Created attachment 28673 [details] Worldfile from the machine where compilation *fails*
Well now I'm very confused.. and feeling mighty silly for raising a bug :/ Since the last compilation that failed (which was after setting ACCEPT_KEYWORDS="~x86" and `emerge -uUD world`) I've: Re-set MAKEOPTS to ="j4" Rebooted Switched to a 2.6.4-gentoo-r1 kernel & modules Rebuilt nvidia-kernel & nvidia-glx And then did an `emerge openmotif` and guess what? It worked.. I'm thoroughly confused now, although I have a working openmotif-2.1.30-r5 install.. Odd.. Any clues? I know at least one other person was having the 'same' problem on the forums - and I'm sure he won't want to upgrade to an ~x86 system if he can avoid it..
The problem is solved by commenting out the MAKE_OPTS option in make.conf (or changing it to somthing bogus like you did, thank god for that mistake :), it's gotta be "-j4'. I don't know about gentoo, I don't know about bugzilla and I don't know about this horrid ncurses webbrowsing, somebody else find out the source of problem ;o)
i will close this until anybody has this problem again ;)
This bug still exists. I have encountered it starting with 2004.3 + GRP and using "emerge world." In this case, it was openmotif-2.1.30-r6. The work-around in comment #4 worked for me; I commented out the MAKE_OPTS in /etc/make.conf and it merged.
