[gentoo-user] gcc build fails during emerge system on new 64-bit install

[gentoo-user] gcc build fails during emerge system on new 64-bit install

[Walter Dnes]

[-- Attachment #1: Type: text/plain, Size: 1087 bytes --]

  This is my first attempt at 64-bit mode.  I have a shiny new Intel i3
with 8 gigs ram on an MSI motherboard.  I got it custom-built locally in
north Toronto, rather than ordering from Dell.  The MSI motherboard has
PS/2 ports (YES!!!) so I don't have to tearfully throw away my genuine
IBM PS/2 "clickety-clack" keyboard.  I selected the profile...

default/linux/amd64/10.0/no-multilib

...to go whole-hog 64-bit.  Does leaving IA32_EMULATION on cause a
problem?

#
# Executable file formats / Emulations
#
CONFIG_BINFMT_ELF=y
CONFIG_COMPAT_BINFMT_ELF=y
CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS=y
# CONFIG_HAVE_AOUT is not set
CONFIG_BINFMT_MISC=y
CONFIG_IA32_EMULATION=y
# CONFIG_IA32_AOUT is not set
CONFIG_COMPAT=y
CONFIG_COMPAT_FOR_U64_ALIGNMENT=y
CONFIG_SYSVIPC_COMPAT=y
CONFIG_NET=y
CONFIG_COMPAT_NETLINK_MESSAGES=y

  I've attached the tail-end of the build log file of gcc-4.4.3-r2, as
well as output from "emerge --info" and "emerge -pqv".  I have a quite
conservative make.conf.  Any ideas about the problem, or even better, a
solution?

-- 
Walter Dnes <waltdnes@waltdnes.org>

[-- Attachment #2: log.txt --]
[-- Type: text/plain, Size: 11715 bytes --]

libtool: compile:  /var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/build/./gcc/gfortran -B/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/build/./gcc/ -B/usr/x86_64-pc-linux-gnu/bin/ -B/usr/x86_64-pc-linux-gnu/lib/ -isystem /usr/x86_64-pc-linux-gnu/include -isystem /usr/x86_64-pc-linux-gnu/sys-include -DHAVE_CONFIG_H -I. -I/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran -I. -iquote/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran/io -I/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran/../gcc -I/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran/../gcc/config -I../.././gcc -D_GNU_SOURCE -I . -Wall -Werror -fimplicit-none -fno-repack-arrays -fno-underscoring -fallow-leading-underscore -c /var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran/generated/_atan_r16.F90  -fPIC -o .libs/_atan_r16.o
libtool: compile:  /var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/build/./gcc/gfortran -B/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/build/./gcc/ -B/usr/x86_64-pc-linux-gnu/bin/ -B/usr/x86_64-pc-linux-gnu/lib/ -isystem /usr/x86_64-pc-linux-gnu/include -isystem /usr/x86_64-pc-linux-gnu/sys-include -DHAVE_CONFIG_H -I. -I/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran -I. -iquote/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran/io -I/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran/../gcc -I/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran/../gcc/config -I../.././gcc -D_GNU_SOURCE -I . -Wall -Werror -fimplicit-none -fno-repack-arrays -fno-underscoring -fallow-leading-underscore -c /var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran/generated/_atan_r16.F90 -o _atan_r16.o >/dev/null 2>&1
/bin/sh ./libtool --tag=FC --mode=compile /var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/build/./gcc/gfortran -B/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/build/./gcc/ -B/usr/x86_64-pc-linux-gnu/bin/ -B/usr/x86_64-pc-linux-gnu/lib/ -isystem /usr/x86_64-pc-linux-gnu/include -isystem /usr/x86_64-pc-linux-gnu/sys-include -DHAVE_CONFIG_H -I. -I/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran -I.  -iquote/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran/io -I/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran/../gcc -I/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran/../gcc/config -I../.././gcc -D_GNU_SOURCE  -I . -Wall -Werror -fimplicit-none -fno-repack-arrays -fno-underscoring -fallow-leading-underscore  -c -o _atanh_r4.lo `test -f '/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran/generated/_atanh_r4.F90' || echo '/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran/'`/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran/generated/_atanh_r4.F90
libtool: compile:  /var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/build/./gcc/gfortran -B/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/build/./gcc/ -B/usr/x86_64-pc-linux-gnu/bin/ -B/usr/x86_64-pc-linux-gnu/lib/ -isystem /usr/x86_64-pc-linux-gnu/include -isystem /usr/x86_64-pc-linux-gnu/sys-include -DHAVE_CONFIG_H -I. -I/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran -I. -iquote/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran/io -I/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran/../gcc -I/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran/../gcc/config -I../.././gcc -D_GNU_SOURCE -I . -Wall -Werror -fimplicit-none -fno-repack-arrays -fno-underscoring -fallow-leading-underscore -c /var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran/generated/_atanh_r4.F90  -fPIC -o .libs/_atanh_r4.o
libtool: compile:  /var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/build/./gcc/gfortran -B/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/build/./gcc/ -B/usr/x86_64-pc-linux-gnu/bin/ -B/usr/x86_64-pc-linux-gnu/lib/ -isystem /usr/x86_64-pc-linux-gnu/include -isystem /usr/x86_64-pc-linux-gnu/sys-include -DHAVE_CONFIG_H -I. -I/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran -I. -iquote/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran/io -I/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran/../gcc -I/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran/../gcc/config -I../.././gcc -D_GNU_SOURCE -I . -Wall -Werror -fimplicit-none -fno-repack-arrays -fno-underscoring -fallow-leading-underscore -c /var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran/generated/_atanh_r4.F90 -o _atanh_r4.o >/dev/null 2>&1
/bin/sh ./libtool --tag=FC --mode=compile /var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/build/./gcc/gfortran -B/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/build/./gcc/ -B/usr/x86_64-pc-linux-gnu/bin/ -B/usr/x86_64-pc-linux-gnu/lib/ -isystem /usr/x86_64-pc-linux-gnu/include -isystem /usr/x86_64-pc-linux-gnu/sys-include -DHAVE_CONFIG_H -I. -I/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran -I.  -iquote/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran/io -I/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran/../gcc -I/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran/../gcc/config -I../.././gcc -D_GNU_SOURCE  -I . -Wall -Werror -fimplicit-none -fno-repack-arrays -fno-underscoring -fallow-leading-underscore  -c -o _atanh_r8.lo `test -f '/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran/generated/_atanh_r8.F90' || echo '/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran/'`/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran/generated/_atanh_r8.F90
libtool: compile:  /var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/build/./gcc/gfortran -B/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/build/./gcc/ -B/usr/x86_64-pc-linux-gnu/bin/ -B/usr/x86_64-pc-linux-gnu/lib/ -isystem /usr/x86_64-pc-linux-gnu/include -isystem /usr/x86_64-pc-linux-gnu/sys-include -DHAVE_CONFIG_H -I. -I/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran -I. -iquote/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran/io -I/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran/../gcc -I/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran/../gcc/config -I../.././gcc -D_GNU_SOURCE -I . -Wall -Werror -fimplicit-none -fno-repack-arrays -fno-underscoring -fallow-leading-underscore -c /var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran/generated/_atanh_r8.F90  -fPIC -o .libs/_atanh_r8.o
libtool: compile:  /var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/build/./gcc/gfortran -B/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/build/./gcc/ -B/usr/x86_64-pc-linux-gnu/bin/ -B/usr/x86_64-pc-linux-gnu/lib/ -isystem /usr/x86_64-pc-linux-gnu/include -isystem /usr/x86_64-pc-linux-gnu/sys-include -DHAVE_CONFIG_H -I. -I/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran -I. -iquote/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran/io -I/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran/../gcc -I/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran/../gcc/config -I../.././gcc -D_GNU_SOURCE -I . -Wall -Werror -fimplicit-none -fno-repack-arrays -fno-underscoring -fallow-leading-underscore -c /var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran/generated/_atanh_r8.F90 -o _atanh_r8.o >/dev/null 2>&1
/bin/sh ./libtool --tag=FC --mode=compile /var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/build/./gcc/gfortran -B/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/build/./gcc/ -B/usr/x86_64-pc-linux-gnu/bin/ -B/usr/x86_64-pc-linux-gnu/lib/ -isystem /usr/x86_64-pc-linux-gnu/include -isystem /usr/x86_64-pc-linux-gnu/sys-include -DHAVE_CONFIG_H -I. -I/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran -I.  -iquote/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran/io -I/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran/../gcc -I/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran/../gcc/config -I../.././gcc -D_GNU_SOURCE  -I . -Wall -Werror -fimplicit-none -fno-repack-arrays -fno-underscoring -fallow-leading-underscore  -c -o _atanh_r10.lo `test -f '/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran/generated/_atanh_r10.F90' || echo '/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran/'`/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran/generated/_atanh_r10.F90
libtool: compile:  /var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/build/./gcc/gfortran -B/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/build/./gcc/ -B/usr/x86_64-pc-linux-gnu/bin/ -B/usr/x86_64-pc-linux-gnu/lib/ -isystem /usr/x86_64-pc-linux-gnu/include -isystem /usr/x86_64-pc-linux-gnu/sys-include -DHAVE_CONFIG_H -I. -I/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran -I. -iquote/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran/io -I/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran/../gcc -I/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran/../gcc/config -I../.././gcc -D_GNU_SOURCE -I . -Wall -Werror -fimplicit-none -fno-repack-arrays -fno-underscoring -fallow-leading-underscore -c /var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran/generated/_atanh_r10.F90  -fPIC -o .libs/_atanh_r10.o
libtool: compile:  /var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/build/./gcc/gfortran -B/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/build/./gcc/ -B/usr/x86_64-pc-linux-gnu/bin/ -B/usr/x86_64-pc-linux-gnu/lib/ -isystem /usr/x86_64-pc-linux-gnu/include -isystem /usr/x86_64-pc-linux-gnu/sys-include -DHAVE_CONFIG_H -I. -I/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran -I. -iquote/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran/io -I/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran/../gcc -I/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran/../gcc/config -I../.././gcc -D_GNU_SOURCE -I . -Wall -Werror -fimplicit-none -fno-repack-arrays -fno-underscoring -fallow-leading-underscore -c /var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/gcc-4.4.3/libgfortran/generated/_atanh_r10.F90 -o _atanh_r10.o >/dev/null 2>&1
make[3]: *** [_atanh_r10.lo] Error 1
make[3]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/build/x86_64-pc-linux-gnu/libgfortran'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/build/x86_64-pc-linux-gnu/libgfortran'
make[1]: *** [all-target-libgfortran] Error 2
make[1]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/build'
make: *** [bootstrap-lean] Error 2
 * ERROR: sys-devel/gcc-4.4.3-r2 failed:
 *   emake failed with bootstrap-lean
 * 
 * Call stack:
 *     ebuild.sh, line   54:  Called src_compile
 *   environment, line 5135:  Called toolchain_src_compile
 *   environment, line 5730:  Called gcc_src_compile
 *   environment, line 3288:  Called gcc_do_make
 *   environment, line 3075:  Called die
 * The specific snippet of code:
 *       emake LDFLAGS="${LDFLAGS}" STAGE1_CFLAGS="${STAGE1_CFLAGS}" LIBPATH="${LIBPATH}" BOOT_CFLAGS="${BOOT_CFLAGS}" ${GCC_MAKE_TARGET} || die "emake failed with ${GCC_MAKE_TARGET}";
 * 
 * If you need support, post the output of 'emerge --info =sys-devel/gcc-4.4.3-r2',
 * the complete build log and the output of 'emerge -pqv =sys-devel/gcc-4.4.3-r2'.
 * The complete build log is located at '/var/log/portage/sys-devel:gcc-4.4.3-r2:20100623-213852.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-devel/gcc-4.4.3-r2/temp/environment'.
 * S: '/var/tmp/portage/sys-devel/gcc-4.4.3-r2/work/build'

[-- Attachment #3: pqv.txt --]
[-- Type: text/plain, Size: 255 bytes --]

[ebuild   R   ] sys-devel/gcc-4.4.3-r2  USE="fortran nptl (-altivec) -bootstrap -build -doc (-fixed-point) -gcj -graphite -gtk (-hardened) (-libffi) -mudflap (-multilib) -multislot (-n32) (-n64) -nls -nocxx -objc -objc++ -objc-gc -openmp -test -vanilla" 

[-- Attachment #4: info.txt --]
[-- Type: text/plain, Size: 3968 bytes --]

Portage 2.1.8.3 (default/linux/amd64/10.0/no-multilib, gcc-4.3.4, glibc-2.11.1-r0, 2.6.32-gentoo-r7 x86_64)
=================================================================
                        System Settings
=================================================================
System uname: Linux-2.6.32-gentoo-r7-x86_64-Intel-R-_Core-TM-_i3_CPU_530_@_2.93GHz-with-gentoo-1.12.13
Timestamp of tree: Wed, 23 Jun 2010 01:15:01 +0000
app-shells/bash:     4.0_p37
dev-lang/python:     2.6.5-r2
sys-apps/baselayout: 1.12.13
sys-apps/sandbox:    1.6-r2
sys-devel/autoconf:  2.65
sys-devel/automake:  1.10.3, 1.11.1
sys-devel/binutils:  2.20.1-r1
sys-devel/gcc:       4.3.4, 4.4.3-r2
sys-devel/gcc-config: 1.4.1
sys-devel/libtool:   2.2.6b
virtual/os-headers:  2.6.30-r1
ACCEPT_KEYWORDS="amd64"
ACCEPT_LICENSE="*"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-O2 -march=native -mfpmath=sse -fomit-frame-pointer -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/gconf /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo"
CXXFLAGS="-O2 -march=native -mfpmath=sse -fomit-frame-pointer -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="assume-digests distlocks fixpackages news parallel-fetch protect-owned sandbox sfperms strict unmerge-logs unmerge-orphans userfetch"
GENTOO_MIRRORS="http://mirrors.acm.cs.rpi.edu/gentoo/ http://gentoo.netnitco.net"
LDFLAGS="-Wl,-O1"
MAKEOPTS="-j1"
PKGDIR="/usr/portage/packages"
PORTAGE_CONFIGROOT="/"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage"
USE="X a52 aac amd64 bzip2 dga dri exif ffmpeg flac fortran gif intel joystick jpeg mmx mng moznopango mp3 mpeg nptl nptlonly nsplugin offensive ogg opengl png posix sse sse2 sse3 ssse3 theora threads tiff truetype vim-syntax vorbis wmf xcomposite xpm xv xvid zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol asym" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" ELIBC="glibc" INPUT_DEVICES="keyboard mouse" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" RUBY_TARGETS="ruby18" USERLAND="GNU" VIDEO_CARDS="intel vga" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq steal rawnat logmark ipmark dhcpmac delude chaos account" 
Unset:  CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, FFLAGS, INSTALL_MASK, LANG, LC_ALL, LINGUAS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY

=================================================================
                        Package Settings
=================================================================

sys-devel/gcc-4.4.3-r2 was built with the following:
USE="fortran nptl (-altivec) -bootstrap -build -doc (-fixed-point) -gcj -graphite -gtk (-hardened) (-libffi) -mudflap (-multilib) -multislot (-n32) (-n64) -nls -nocxx -objc -objc++ -objc-gc -openmp -test -vanilla" 
CFLAGS="-O2 -march=native -pipe"
CXXFLAGS="-O2 -march=native -pipe"

Re: [gentoo-user] gcc build fails during emerge system on new 64-bit install

[Stroller]

On 24 Jun 2010, at 00:33, Walter Dnes wrote:
> ... The MSI motherboard has
> PS/2 ports (YES!!!) so I don't have to tearfully throw away my genuine
> IBM PS/2 "clickety-clack" keyboard.

Your motherboard doesn't need native PS2 ports: http://www.ledshoppe.com/Product/com/CA4036.htm

Stroller.

Re: [gentoo-user] gcc build fails during emerge system on new 64-bit install

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 1672 bytes --]

On Thursday 24 June 2010 00:33:24 Walter Dnes wrote:
>   This is my first attempt at 64-bit mode.  I have a shiny new Intel i3
> with 8 gigs ram on an MSI motherboard.  I got it custom-built locally in
> north Toronto, rather than ordering from Dell.  The MSI motherboard has
> PS/2 ports (YES!!!) so I don't have to tearfully throw away my genuine
> IBM PS/2 "clickety-clack" keyboard.  I selected the profile...
> 
> default/linux/amd64/10.0/no-multilib
> 
> ...to go whole-hog 64-bit.  Does leaving IA32_EMULATION on cause a
> problem?

I thought that you can't have IA32_emulation without multilib ... 

Is there a reason why you don't go for a usual desktop profile with multilib?  
I'll repeat the advice I was given in this list sometime around last Christmas 
(but can't find the thread now): you're bound to find some pesky application 
which is only available in 32bit and then you'll curse for having to 
reinstall.

> #
> # Executable file formats / Emulations
> #
> CONFIG_BINFMT_ELF=y
> CONFIG_COMPAT_BINFMT_ELF=y
> CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS=y
> # CONFIG_HAVE_AOUT is not set
> CONFIG_BINFMT_MISC=y
> CONFIG_IA32_EMULATION=y
> # CONFIG_IA32_AOUT is not set
> CONFIG_COMPAT=y
> CONFIG_COMPAT_FOR_U64_ALIGNMENT=y
> CONFIG_SYSVIPC_COMPAT=y
> CONFIG_NET=y
> CONFIG_COMPAT_NETLINK_MESSAGES=y
> 
>   I've attached the tail-end of the build log file of gcc-4.4.3-r2, as
> well as output from "emerge --info" and "emerge -pqv".  I have a quite
> conservative make.conf.  Any ideas about the problem, or even better, a
> solution?

Have you tried setting -j1 and trying emerging it once more?
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] gcc build fails during emerge system on new 64-bit install

[Walter Dnes]

On Thu, Jun 24, 2010 at 07:28:14AM +0100, Stroller wrote
> On 24 Jun 2010, at 00:33, Walter Dnes wrote:
> > ... The MSI motherboard has
> > PS/2 ports (YES!!!) so I don't have to tearfully throw away my genuine
> > IBM PS/2 "clickety-clack" keyboard.
> 
> Your motherboard doesn't need native PS2 ports: http://www.ledshoppe.com/Product/com/CA4036.htm

  Hmmmm.  Interesting.  I assume that it's not your average passive
connector.  Those don't work.  "2. USB Bus Powered" probably means it
has keyboard emulation circuitry.

-- 
Walter Dnes <waltdnes@waltdnes.org>

[gentoo-user] [SOLVED] gcc build fails during emerge system on new 64-bit install

[Walter Dnes]

On Thu, Jun 24, 2010 at 09:38:17PM +0100, Mick wrote

> I'll repeat the advice I was given in this list sometime around last
> Christmas (but can't find the thread now): you're bound to find some
> pesky application which is only available in 32bit and then you'll
> curse for having to reinstall.

  If anything, I'll install a VM to run it in.

> Have you tried setting -j1 and trying emerging it once more?

  I *ALWAYS* have -j1 in /etc/make.conf.  Anyways, it turned out to be
something completely different.  Whilst doing additional Google
searching, I stumbled across "Foolproof Gentoo World Update Build Order"
at http://foxpa.ws/tag/package-keywords/ and it was proof against this
fool, too <G>.  My problem was that the Gentoo install snapshot put in
gcc-4.3.4, and "emerge --update world" pulled in gcc-4.4.3-r2.  So far,
so good.  But after the first build, I forgot to gcc-config over to
4.4.3-r2 ... dohhhhhhh.

  Anyhow, after switching over, rebuilding gcc-4.4.3-r2, exiting,
logging back in, unmerging gcc-4.3.4, and rebuilding glibc, I
successfully emerged system and world.  I'm now emerging xorg-x11.

<RANT>
  Why on earth will xorg-x11 *NOT* build if I mask out various arabic,
cyrillic, ethiopic, and jis fonts?  My PC is *NOT* intended to be a
kiosk machine at UN headquarters fer-cryin-out-loud.
</RANT>

-- 
Walter Dnes <waltdnes@waltdnes.org>

Re: [gentoo-user] [SOLVED] gcc build fails during emerge system on new 64-bit install

[Dale]

Walter Dnes wrote:
> On Thu, Jun 24, 2010 at 09:38:17PM +0100, Mick wrote
>
>    
>> I'll repeat the advice I was given in this list sometime around last
>> Christmas (but can't find the thread now): you're bound to find some
>> pesky application which is only available in 32bit and then you'll
>> curse for having to reinstall.
>>      
>    If anything, I'll install a VM to run it in.
>
>    
>> Have you tried setting -j1 and trying emerging it once more?
>>      
>    I *ALWAYS* have -j1 in /etc/make.conf.  Anyways, it turned out to be
> something completely different.  Whilst doing additional Google
> searching, I stumbled across "Foolproof Gentoo World Update Build Order"
> at http://foxpa.ws/tag/package-keywords/ and it was proof against this
> fool, too<G>.  My problem was that the Gentoo install snapshot put in
> gcc-4.3.4, and "emerge --update world" pulled in gcc-4.4.3-r2.  So far,
> so good.  But after the first build, I forgot to gcc-config over to
> 4.4.3-r2 ... dohhhhhhh.
>
>    Anyhow, after switching over, rebuilding gcc-4.4.3-r2, exiting,
> logging back in, unmerging gcc-4.3.4, and rebuilding glibc, I
> successfully emerged system and world.  I'm now emerging xorg-x11.
>
> <RANT>
>    Why on earth will xorg-x11 *NOT* build if I mask out various arabic,
> cyrillic, ethiopic, and jis fonts?  My PC is *NOT* intended to be a
> kiosk machine at UN headquarters fer-cryin-out-loud.
> </RANT>
>
>    

For future reference, after you switch gcc, you should run env-update 
and source /etc/profile.  Then you don't have to log out and back in 
again.  One could argue that one is easier than the other tho.  ;-)  
Depends on the length of the password I guess.

Dale

:-)  :-)

Re: [gentoo-user] gcc build fails during emerge system on new 64-bit install

[Stroller]

On 25 Jun 2010, at 03:56, Walter Dnes wrote:

> On Thu, Jun 24, 2010 at 07:28:14AM +0100, Stroller wrote
>> On 24 Jun 2010, at 00:33, Walter Dnes wrote:
>>> ... The MSI motherboard has
>>> PS/2 ports (YES!!!) so I don't have to tearfully throw away my  
>>> genuine
>>> IBM PS/2 "clickety-clack" keyboard.
>>
>> Your motherboard doesn't need native PS2 ports: http://www.ledshoppe.com/Product/com/CA4036.htm
>
>  Hmmmm.  Interesting.  I assume that it's not your average passive
> connector.  Those don't work.  "2. USB Bus Powered" probably means it
> has keyboard emulation circuitry.

I assume it has some electronics in there. These are exceedingly  
common, however, and make the keyboard appear to the o/s (and BIOS) as  
a standard USB HCI device.

Stroller.

Re: [gentoo-user] [SOLVED] gcc build fails during emerge system on new 64-bit install

[Alex Schuster]

Walter Dnes writes:

> On Thu, Jun 24, 2010 at 09:38:17PM +0100, Mick wrote
> 
> > I'll repeat the advice I was given in this list sometime around last
> > Christmas (but can't find the thread now): you're bound to find some
> > pesky application which is only available in 32bit and then you'll
> > curse for having to reinstall.
> 
>   If anything, I'll install a VM to run it in.

I'm curious. Are there advantages on not running a multilib profile?

> <RANT>
>   Why on earth will xorg-x11 *NOT* build if I mask out various arabic,
> cyrillic, ethiopic, and jis fonts?  My PC is *NOT* intended to be a
> kiosk machine at UN headquarters fer-cryin-out-loud.
> </RANT>

xorg-x11 depends on them, I think there is no way to tell portage a 
dependency is optional. Might be nice feature, though. Debian has 
something like this I think, 'suggested packages' that may be installed 
additionally if desired. Maybe an 'optional' use flag could do this? But 
it would habe to be set for every package, not in the DEPEND list in the 
xorg-x11 ebuild. A DEPEND_IF_NOT_MASKED entry in the ebuild would be nice.

Anyway, I do not install xorg-x11 at all, but xorg-server instead. Which 
means I have to care about optional stuff for myself, like fonts, tools 
like xdpyinfo and such. But at least I do not have cyrillic fonts on my 
system :)

	Wonko

Re: [gentoo-user] [SOLVED] gcc build fails during emerge system on new 64-bit install

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 525 bytes --]

On Thu, 24 Jun 2010 23:29:09 -0400, Walter Dnes wrote:

> <RANT>
>   Why on earth will xorg-x11 *NOT* build if I mask out various arabic,
> cyrillic, ethiopic, and jis fonts?  My PC is *NOT* intended to be a
> kiosk machine at UN headquarters fer-cryin-out-loud.
> </RANT>

Because xorg-x11 is  metapackage that pulls everything in. If you want to
choose what is installed, either emerge components individually or
create a set. 


-- 
Neil Bothwick

Copy from another: plagiarism. Copy from many: research.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] [SOLVED] gcc build fails during emerge system on new 64-bit install

[waltdnes]

On Fri, Jun 25, 2010 at 12:44:47AM -0500, Dale wrote

> For future reference, after you switch gcc, you should run env-update 
> and source /etc/profile.  Then you don't have to log out and back in 
> again.  One could argue that one is easier than the other tho.  ;-)  

  I knew I had to do a couple of things if I wanted to avoid logout and
login, but I couldn't remember off the top of my head.  It was easier to
just log out+in rather than look it up.

-- 
Walter Dnes <waltdnes@waltdnes.org>

Re: [gentoo-user] gcc build fails during emerge system on new 64-bit install

[Peter Humphrey]

On Friday 25 June 2010 09:26:25 Stroller wrote:

> I assume it has some electronics in there. These are exceedingly
> common, however, and make the keyboard appear to the o/s (and BIOS)
> as a standard USB HCI device.

Aha! Could I then use one of these adapters and my PS/2 mouse and 
keyboard with a USB KVM switch? I have a spare one of those lying about 
and my PS/2 and VGA one is getting a bit long in the tooth.

-- 
Rgds
Peter.          Linux Counter 5290, 1994-04-23.