Using MAKEOPTS="-j3" in make.conf, emerging erlang-10.2.7 just stops at this point: ... === Entering application gs make[3]: Entering directory `/var/tmp/portage/erlang-10.2.10/work/otp_src_R10B-10/lib/gs/src' erlc -W +debug_info -o../ebin gs.erl ...[snip]... erlc -W +debug_info -o../ebin gse.erl erl -pa ../ebin -s gs_make -s erlang halt -noshell There is no error message, the compile just does not proceed (at least for ~10h, this is how long I waited). However, removing the "MAKEOPTS" line in make.conf, the merge finishes successfully. -- Here is my emerge --info: Portage 2.0.54 (default-linux/amd64/2005.1, gcc-3.4.5, glibc-2.3.5-r2, 2.6.14-gentoo-r5 x86_64) ================================================================= System uname: 2.6.14-gentoo-r5 x86_64 AMD Opteron(tm) Processor 252 Gentoo Base System version 1.6.14 dev-lang/python: 2.3.5-r2, 2.4.2 dev-util/ccache: [Not Present] dev-util/confcache: [Not Present] 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="amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=opteron -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/eselect/compiler /etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=opteron -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://128.213.5.34/gentoo http://www.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="amd64 X alsa arts audiofile avi berkdb bitmap-fonts bzip2 cdr cli crypt cups curl dri dv dvd dvdr dvdread eds emacs emboss encode exif expat fam ffmpeg flash font-server foomaticdb fortran gd gdbm gif glut gpm gstreamer gtk gtk2 idn ieee1394 imagemagick imap imlib ipv6 isdnlog java jpeg kde lcms libwww live lua lzw lzw-tiff mad mjpeg mng motif mp3 mpeg ncurses nls nptl odbc ogg opengl pam pcre pdflib perl plotutils png postgres ppds pppd python qt quicktime readline reflection samba sdl session smp spell spl ssl svg tcpd tetex threads tiff truetype truetype-fonts type1-fonts udev usb vorbis wmf xine xinerama xml2 xorg xpm xv zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS
Try the latest please.
(In reply to comment #1) > Try the latest please. > I emerged the latest via a routine emerge -uD world without problems. In fact, please consider moving to the stable amd64 keyword. For me, this bug is obsolete.
(In reply to comment #2) > (In reply to comment #1) > > Try the latest please. > I emerged the latest via a routine emerge -uD world without problems. In fact, > please consider moving to the stable amd64 keyword. For me, this bug is > obsolete. This will be requested (I can't do that, architecture teams are responsible) on 07 Dec, see bug 151612. Thank you, for your feedback.
all relevant arches stabled
