The emerge of valgrind-3.2.3 fails on my AMD64 system due to a missing <gnu/stubs-32.h> header. Apparently, valgrind wants to compile both 32- and 64-bit versions, but glibc-2.5-r3 does not provide the 32-bit header -- stubs-64.h does exist in /usr/include/gnu and indeed was installed by glibc-2.5-r3. # FEATURES=-distcc emerge -atv valgrind [...] [ebuild U ] sys-devel/gdb-6.6-r2 [6.4] USE="-nls -test -vanilla" 0 kB [...] checking for a supported CPU... ok (x86_64) checking for a 64-bit only build... no checking for a 32-bit only build... no [...] Making all in coregrind make[2]: Entering directory `/var/tmp/portage/dev-util/valgrind-3.2.3/work/valgrind-3.2.3/coregrind' make all-am make[3]: Entering directory `/var/tmp/portage/dev-util/valgrind-3.2.3/work/valgrind-3.2.3/coregrind' x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -I../coregrind -I.. -I../coregrind/x86 -I../coregrind/linux -I../coregrind/x86-linux -I../include -I../VEX/pub -DVG_PLATFORM="\"x86-linux\"" -DVGA_x86=1 -DVGO_linux=1 -DVGP_x86_linux=1 -DVG_LIBDIR="\"/usr/lib/valgrind"\" -m32 -fno-stack-protector -O -g -Wmissing-prototypes -Winline -Wall -Wshadow -Wpointer-arith -Wstrict-prototypes -Wmissing-declarations -pipe -O2 -march=nocona -mtune=nocona -Wno-long-long -Wno-pointer-sign -Wdeclaration-after-statement -MT libcoregrind_x86_linux_a-m_commandline.o -MD -MP -MF .deps/libcoregrind_x86_linux_a-m_commandline.Tpo -c -o libcoregrind_x86_linux_a-m_commandline.o `test -f 'm_commandline.c' || echo './'`m_commandline.c In file included from /usr/include/features.h:346, from /usr/include/setjmp.h:26, from pub_core_basics.h:65, from m_commandline.c:31: /usr/include/gnu/stubs.h:7:27: error: gnu/stubs-32.h: No such file or directory make[3]: *** [libcoregrind_x86_linux_a-m_commandline.o] Error 1 make[3]: Leaving directory `/var/tmp/portage/dev-util/valgrind-3.2.3/work/valgrind-3.2.3/coregrind' make[2]: *** [all] Error 2 make[2]: Leaving directory `/var/tmp/portage/dev-util/valgrind-3.2.3/work/valgrind-3.2.3/coregrind' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/dev-util/valgrind-3.2.3/work/valgrind-3.2.3' make: *** [all] Error 2 !!! ERROR: dev-util/valgrind-3.2.3 failed. ---- emerge --info output: Portage 2.1.2.7 (default-linux/x86/2007.0, gcc-4.1.2, glibc-2.5-r3, 2.6.17-gentoo-r8-pig1 x86_64) ================================================================= System uname: 2.6.17-gentoo-r8-pig1 x86_64 Intel(R) Pentium(R) 4 CPU 3.00GHz Gentoo Base System release 1.12.6 Timestamp of tree: Thu, 14 Jun 2007 08:50:01 +0000 distcc 2.18.3 x86_64-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] dev-java/java-config: 1.3.7, 2.0.32 dev-lang/python: 2.4.4-r4 dev-python/pycrypto: 2.0.1-r5 sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.61 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10 sys-devel/binutils: 2.16.1-r3 sys-devel/gcc-config: 1.3.16 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.17-r2 ACCEPT_KEYWORDS="amd64 x86" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-pipe -O2 -fstack-protector -march=nocona -mtune=nocona" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc" CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf /etc/revdep-rebuild /etc/terminfo" CXXFLAGS="-pipe -O2 -fstack-protector -march=nocona -mtune=nocona" DISTDIR="/store/distfiles" FEATURES="distlocks metadata-transfer parallel-fetch sandbox sfperms strict userfetch userpriv usersandbox" GENTOO_MIRRORS="http://a2/gentoo/ ftp://ftp.ipv6.linux.ee/pub/gentoo/distfiles/ http://ftp.linux.ee/pub/gentoo/distfiles/" LANG="en_US" LC_ALL="en_US.UTF-8" MAKEOPTS="-j4" 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 --filter=H_**/files/digest-*" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="acl adns aio async berkdb bitmap-fonts caps cli cracklib crypt d dri gcc64 gdbm iconv ipv6 isdnlog jpeg libg++ logrotate midi mudflap multitarget ncurses nptl nptlonly offensive openmp pam pcre pg-intdatetime png pppd python quotas readline reflection sasl session spl ssl tiff truetype truetype-fonts type1-fonts unicode x86 xml xorg zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1 emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol" ELIBC="glibc" INPUT_DEVICES="keyboard mouse evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" USERLAND="GNU" VIDEO_CARDS="apm ark chips cirrus cyrix dummy fbdev glint i128 i740 i810 imstt mach64 mga neomagic nsc nv r128 radeon rendition s3 s3virge savage siliconmotion sis sisusb tdfx tga trident tseng v4l vesa vga via vmware voodoo" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LDFLAGS, LINGUAS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
Attach emerge --info -v output, please. Also, have you switched from no-multilib to multilib profile recently?
Created attachment 122599 [details] emerge -v --info emerge -v --info is attached. Indeed, the installation is non-multilib, with the multilib USE flag disabled (why?); the machine was installed from a 2006.1 amd64 installcd, *not* using a hardened profile, and recently upgraded to the 2007.0 profile. # USE=multilib emerge sys-libs/glibc -ptv [ebuild R ] sys-libs/glibc-2.5-r3 USE="nptl nptlonly -build -debug -glibc-compat20 -glibc-omitfp (-hardened) (-multilib) -nls -profile (-selinux)" 0 kB
(In reply to comment #2) > Indeed, the installation is non-multilib, with the multilib USE flag disabled > (why?) Nah, (-flag) means masked or forced flag, it's always enabled unless you are on no-multilib profile.
your system setup is completely screwed, not a chance this is supported ACCEPT_KEYWORDS="amd64 x86" CBUILD="x86_64-pc-linux-gnu" profile = default-linux/x86/2007.0,
