Bug 449980 – sys-devel/gcc-4.6.3 with sys-libs/glibc-2.16 works on host but fails in openvz container with same configuration - libquadmath: configure: error: cannot run C compiled programs.

• Status: RESOLVED NEEDINFO
• Product: Gentoo Linux

[Description Joakim 2013-01-03 11:24:20 UTC]

linux-2.6.32-openvz-062.2 runs on the base node and there gcc-4.6.3 and glibc-2.16 builds and runs fine, rebuilt several times. However, in all containers, glibc-2.16 and gcc-4.6.3 built once but then not again. 

Reproducible: Always

Steps to Reproduce:
1. # emerge -uDalvN system
These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild   R    ] sys-devel/gcc-4.6.3:4.6  USE="cxx fortran mudflap (multilib) nls nptl openmp (-altivec) -bootstrap -build -doc (-fixed-point) -gcj -go -graphite -gtk (-hardened) (-libssp) -multislot -nopie -nossp -objc -objc++ -objc-gc {-test} -vanilla (-nocxx%)" 20 kB

Total: 1 package (1 reinstall), Size of downloads: 20 kB

Would you like to merge these packages? [Yes/No] y
2.
3.
Actual Results:  
configure: creating ./config.status
config.status: creating Makefile
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libtool commands
config.status: executing default-1 commands
Adding multilib support to Makefile in /var/tmp/portage/sys-devel/gcc-4.6.3/work/gcc-4.6.3/libquadmath
multidirs=32
with_multisubdir=
Running configure in multilib subdirs 32
pwd: /var/tmp/portage/sys-devel/gcc-4.6.3/work/build/x86_64-pc-linux-gnu/libquadmath
Running configure in multilib subdir 32
pwd: /var/tmp/portage/sys-devel/gcc-4.6.3/work/build/x86_64-pc-linux-gnu
configure: creating cache ./config.cache
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking target system type... x86_64-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for --enable-version-specific-runtime-libs... no
checking for style of include used by make... GNU
checking for x86_64-pc-linux-gnu-gcc... /var/tmp/portage/sys-devel/gcc-4.6.3/work/build/./gcc/xgcc -B/var/tmp/portage/sys-devel/gcc-4.6.3/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  -m32
checking for C compiler default output file name... a.out
checking whether the C compiler works... configure: error: in `/var/tmp/portage/sys-devel/gcc-4.6.3/work/build/x86_64-pc-linux-gnu/32/libquadmath':
configure: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.
make[1]: *** [configure-target-libquadmath] Error 1
make[1]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.6.3/work/build'
make: *** [bootstrap-lean] Error 2
emake failed
 * ERROR: sys-devel/gcc-4.6.3 failed (compile phase):
 *   emake failed with bootstrap-lean
 * 
 * Call stack:
 *     ebuild.sh, line   93:  Called src_compile
 *   environment, line 4060:  Called toolchain_src_compile
 *   environment, line 4720:  Called gcc_do_make
 *   environment, line 2371:  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.6.3'`,
 * the complete build log and the output of `emerge -pqv '=sys-devel/gcc-4.6.3'`.
 * 
 * Please include /var/tmp/portage/sys-devel/gcc-4.6.3/work/build/gcc-build-logs.tar.bz2 in your bug report
 * 
 * The complete build log is located at '/var/tmp/portage/sys-devel/gcc-4.6.3/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-devel/gcc-4.6.3/temp/environment'.
 * Working directory: '/var/tmp/portage/sys-devel/gcc-4.6.3/work/build'
 * S: '/var/tmp/portage/sys-devel/gcc-4.6.3/work/build'

>>> Failed to emerge sys-devel/gcc-4.6.3, Log file:

>>>  '/var/tmp/portage/sys-devel/gcc-4.6.3/temp/build.log'

 * Messages for package sys-devel/gcc-4.6.3:

 * 
 * LTO support is still experimental and unstable.
 * Any bugs resulting from the use of LTO will not be fixed.
 * 
 * ERROR: sys-devel/gcc-4.6.3 failed (compile phase):
 *   emake failed with bootstrap-lean
 * 
 * Call stack:
 *     ebuild.sh, line   93:  Called src_compile
 *   environment, line 4060:  Called toolchain_src_compile
 *   environment, line 4720:  Called gcc_do_make
 *   environment, line 2371:  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.6.3'`,
 * the complete build log and the output of `emerge -pqv '=sys-devel/gcc-4.6.3'`.
 * 
 * Please include /var/tmp/portage/sys-devel/gcc-4.6.3/work/build/gcc-build-logs.tar.bz2 in your bug report
 * 
 * The complete build log is located at '/var/tmp/portage/sys-devel/gcc-4.6.3/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-devel/gcc-4.6.3/temp/environment'.
 * Working directory: '/var/tmp/portage/sys-devel/gcc-4.6.3/work/build'
 * S: '/var/tmp/portage/sys-devel/gcc-4.6.3/work/build'

Expected Results:  
It should have compiled without error

# emerge --info '=sys-devel/gcc-4.6.3'
Portage 2.2.0_alpha149 (default/linux/amd64/10.0/server, gcc-4.6.3, glibc-2.16.0, 2.6.32-openvz-062.2 x86_64)
=================================================================
                        System Settings
=================================================================
System uname: Linux-2.6.32-openvz-062.2-x86_64-Intel-R-_Core-TM-2_Quad_CPU_Q9400_@_2.66GHz-with-gentoo-2.2
Timestamp of tree: Wed, 02 Jan 2013 15:15:01 +0000
ld GNU ld (GNU Binutils) 2.23.1
app-shells/bash:          4.2_p39-r1
dev-lang/python:          2.7.3-r2, 3.2.3-r2
dev-util/cmake:           2.8.9-r1
dev-util/pkgconfig:       0.27.1
sys-apps/baselayout:      2.2
sys-apps/openrc:          0.11.8
sys-apps/sandbox:         2.6
sys-devel/autoconf:       2.69
sys-devel/automake:       1.11.5, 1.12.6
sys-devel/binutils:       2.23.1
sys-devel/gcc:            4.4.7, 4.5.4, 4.6.3
sys-devel/gcc-config:     1.8
sys-devel/libtool:        2.4.2
sys-devel/make:           3.82-r4
sys-kernel/linux-headers: 3.7 (virtual/os-headers)
sys-libs/glibc:           2.16.0
Repositories: gentoo x-portage
Installed sets: @system
ACCEPT_KEYWORDS="amd64 ~amd64"
ACCEPT_LICENSE="* -@EULA"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=native -O2 -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /sbin/rc"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo"
CXXFLAGS="-march=native -O2 -pipe"
DISTDIR="/usr/portage/distfiles"
FCFLAGS="-O2 -pipe"
FEATURES="assume-digests binpkg-logs config-protect-if-modified distlocks ebuild-locks fixlafiles merge-sync news parallel-fetch preserve-libs protect-owned sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch"
FFLAGS="-O2 -pipe"
GENTOO_MIRRORS="http://distfiles.gentoo.org"
LDFLAGS="-Wl,-O1 -Wl,--as-needed"
PKGDIR="/usr/portage/packages"
PORTAGE_CONFIGROOT="/"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --human-readable --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="acl amd64 berkdb bzip2 cli cracklib crypt cups cxx dri fortran gdbm gpm iconv mmx modules mudflap multilib ncurses nls nptl openmp pam pcre postgres pppd readline session snmp sse sse2 ssl tcpd truetype unicode urandom xml 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 asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="authn_core authz_core socache_shmcb unixd 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 cgi cgid 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" CALLIGRA_FEATURES="kexi words flow plan sheets stage tables krita karbon braindump" CAMERAS="ptp2" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock itrax mtk3301 nmea ntrip navcom oceanserver oldstyle oncore rtcm104v2 rtcm104v3 sirf superstar2 timing tsip tripmate tnt ubx" INPUT_DEVICES="keyboard mouse evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LIBREOFFICE_EXTENSIONS="presenter-console presenter-minimizer" PHP_TARGETS="php5-3" PYTHON_SINGLE_TARGET="python2_7" PYTHON_TARGETS="python2_7 python3_2" RUBY_TARGETS="ruby18 ruby19" USERLAND="GNU" VIDEO_CARDS="fbdev glint intel mach64 mga nouveau nv r128 radeon savage sis tdfx trident vesa via vmware dummy v4l" 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, INSTALL_MASK, LANG, LC_ALL, MAKEOPTS, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, USE_PYTHON

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

sys-devel/gcc-4.6.3 was built with the following:
USE="cxx fortran mudflap (multilib) nls nptl openmp (-altivec) -bootstrap -build -doc (-fixed-point) -gcj -go -graphite -gtk (-hardened) (-libssp) -multislot -nocxx -nopie -nossp -objc -objc++ -objc-gc -test -vanilla"

# emerge -pqv '=sys-devel/gcc-4.6.3'
[ebuild   R   ] sys-devel/gcc-4.6.3  USE="cxx fortran mudflap (multilib) nls nptl openmp (-altivec) -bootstrap -build -doc (-fixed-point) -gcj -go -graphite -gtk (-hardened) (-libssp) -multislot -nopie -nossp -objc -objc++ -objc-gc {-test} -vanilla (-nocxx%)"

[Comment 1 Joakim 2013-01-03 11:27:40 UTC]

Created attachment 334170 [details]
build.log.tgz

build.log was compressed with # tar -czf build.log.tgz build.log

[Comment 2 Joakim 2013-01-03 11:29:01 UTC]

Created attachment 334172 [details]
gcc-build-logs.tar.bz2

[Comment 3 Jeroen Roovers (RETIRED) 2013-01-03 12:30:13 UTC]

Comment on attachment 334170 [details]
build.log.tgz

Why did you stick it in a tar archive?

[Comment 4 Jeroen Roovers (RETIRED) 2013-01-03 12:33:37 UTC]

*** This bug has been marked as a duplicate of bug 437496 ***

[Comment 5 Joakim 2013-01-03 13:43:01 UTC]

(In reply to comment #3)
> Comment on attachment 334170 [details]
> build.log.tgz
> 
> Why did you stick it in a tar archive?

Because it's 6mb as plain text and only 1mb is allowed or have I missed something?

[Comment 6 Joakim 2013-01-03 13:49:48 UTC]

(In reply to comment #4)
> 
> *** This bug has been marked as a duplicate of bug 437496 ***

And I'm not sure if I agree about this, it may produce the same error but the fundamentals are different. Both gcc and glibc works perfectly with the current kenel configuartion in the base node, the problem arises inside of the vz container, which uses the same kernel configuration. So I suspect this to probably be a openvz bug.

Sorry if I'm wrong but I cannot accept that a perfectly working system stops working when gcc/glibc is upgraded and the resolution is set to be Invalid, doesn't sound right to me. I can of course still be wrong, but then I hope someone can explain this better so it's possible to solve the problem?

[Comment 7 Tom Wijsman (TomWij) (RETIRED) 2013-01-03 14:15:56 UTC]

> the problem arises inside of the vz container, which uses the same kernel configuration

While the kernel configuration might be the same, who knows the USE flags are different; not using multilib on the host and then using multilib inside the container is enough to make a difference. Telling us it is the same kernel configuration isn't the right response when the other bug tells you to "have x86 support in the kernel", can you please verify whether your multilib USE flags differ between host and container as well as how this setting is set in your container kernel?

[Comment 8 Joakim 2013-01-03 16:37:11 UTC]

(In reply to comment #7)
> > the problem arises inside of the vz container, which uses the same kernel configuration
> 
> While the kernel configuration might be the same, who knows the USE flags
> are different; not using multilib on the host and then using multilib inside
> the container is enough to make a difference. Telling us it is the same
> kernel configuration isn't the right response when the other bug tells you
> to "have x86 support in the kernel", can you please verify whether your
> multilib USE flags differ between host and container as well as how this
> setting is set in your container kernel?

Well these things are not so easy to know when you aren't a developer, just that things break break after upgrading from one minor version to another. Not sure if this is the correct way to answer what you ask for, but this is for the hardware node:

merc ~ # equery h multilib
 * Searching for USE flag multilib ... 
[IP-] [  ] sys-apps/sandbox-2.6:0
[IP-] [  ] sys-devel/gcc-4.5.4:4.5
[IP-] [  ] sys-devel/gcc-4.6.3:4.6
[IP-] [  ] sys-libs/glibc-2.16.0:2.2
merc ~ # equery u glibc   
[ Legend : U - final flag setting for installation]
[        : I - package is installed with flag     ]
[ Colors : set, unset                             ]
 * Found these USE flags for sys-libs/glibc-2.16.0:
 U I
 - - debug     : Enable extra debug codepaths, like asserts and extra output. If you want to get meaningful backtraces see
                 http://www.gentoo.org/proj/en/qa/backtraces.xml
 - - gd        : build memusage and memusagestat tools
 - - profile   : Adds support for software performance analysis (will likely vary from ebuild to ebuild)
 - - systemtap : enable systemtap static probe points
 - - vanilla   : Do not add extra patches which change default behaviour; DO NOT USE THIS ON A GLOBAL SCALE as the severity of the meaning changes
                 drastically
merc ~ # equery u gcc  
[ Legend : U - final flag setting for installation]
[        : I - package is installed with flag     ]
[ Colors : set, unset                             ]
 * Found these USE flags for sys-devel/gcc-4.6.3:
 U I
 - - bootstrap : !!internal use only!! DO NOT SET THIS FLAG YOURSELF!, used during original system bootstrapping [make stage2]
 - - build     : !!internal use only!! DO NOT SET THIS FLAG YOURSELF!, used for creating build images and the first half of bootstrapping [make stage1]
 + + cxx       : Builds support for C++ (bindings, extra libraries, code generation, ...)
 - - doc       : Adds extra documentation (API, Javadoc, etc). It is recommended to enable per package instead of globally
 + + fortran   : Adds support for fortran (formerly f77)
 - - gcj       : Enable building with gcj (The GNU Compiler for the Javatm Programming Language)
 - - go        : Build the GCC Go language frontend.
 - - graphite  : Add support for the framework for loop optimizations based on a polyhedral intermediate representation
 - - gtk       : Useful only when building GCJ, this enables Abstract Window Toolkit (AWT) peer support on top of GTK+
 + + mudflap   : Add support for mudflap, a pointer use checking library
 - - multislot : Allow for SLOTs to include minor version (3.3.4 instead of just 3.3)
 + + nls       : Adds Native Language Support (using gettext - GNU locale utilities)
 - - nopie     : Disable PIE support (NOT FOR GENERAL USE)
 - - nossp     : Disable SSP support (NOT FOR GENERAL USE)
 + + nptl      : Enable support for Native POSIX Threads Library, the new threading module (requires linux-2.6 or better usually)
 - - objc      : Build support for the Objective C code language
 - - objc++    : Build support for the Objective C++ language
 - - objc-gc   : Build support for the Objective C code language Garbage Collector
 + + openmp    : Build support for the OpenMP (support parallel computing), requires >=sys-devel/gcc-4.2 built with USE="openmp"
 - - test      : Workaround to pull in packages needed to run with FEATURES=test. Portage-2.1.2 handles this internally, so don't set it in
                 make.conf/package.use anymore
 - - vanilla   : Do not add extra patches which change default behaviour; DO NOT USE THIS ON A GLOBAL SCALE as the severity of the meaning changes
                 drastically

and this is for the container node in question:
sql / # equery h multilib
 * Searching for USE flag multilib ... 
[IP-] [  ] sys-apps/sandbox-2.6:0
[IP-] [  ] sys-devel/gcc-4.4.7:4.4
[IP-] [  ] sys-devel/gcc-4.5.4:4.5
[IP-] [  ] sys-devel/gcc-4.6.3:4.6
[IP-] [  ] sys-libs/glibc-2.16.0:2.2
sql / # equery u glibc   
[ Legend : U - final flag setting for installation]
[        : I - package is installed with flag     ]
[ Colors : set, unset                             ]
 * Found these USE flags for sys-libs/glibc-2.16.0:
 U I
 - - debug     : Enable extra debug codepaths, like asserts and extra output. If you want to get meaningful backtraces see
                 http://www.gentoo.org/proj/en/qa/backtraces.xml
 - - gd        : build memusage and memusagestat tools
 - - profile   : Adds support for software performance analysis (will likely vary from ebuild to ebuild)
 - - systemtap : enable systemtap static probe points
 - - vanilla   : Do not add extra patches which change default behaviour; DO NOT USE THIS ON A GLOBAL SCALE as the severity of the meaning changes
                 drastically
sql / # equery u gcc  
[ Legend : U - final flag setting for installation]
[        : I - package is installed with flag     ]
[ Colors : set, unset                             ]
 * Found these USE flags for sys-devel/gcc-4.6.3:
 U I
 - - bootstrap : !!internal use only!! DO NOT SET THIS FLAG YOURSELF!, used during original system bootstrapping [make stage2]
 - - build     : !!internal use only!! DO NOT SET THIS FLAG YOURSELF!, used for creating build images and the first half of bootstrapping [make stage1]
 + + cxx       : Builds support for C++ (bindings, extra libraries, code generation, ...)
 - - doc       : Adds extra documentation (API, Javadoc, etc). It is recommended to enable per package instead of globally
 + + fortran   : Adds support for fortran (formerly f77)
 - - gcj       : Enable building with gcj (The GNU Compiler for the Javatm Programming Language)
 - - go        : Build the GCC Go language frontend.
 - - graphite  : Add support for the framework for loop optimizations based on a polyhedral intermediate representation
 - - gtk       : Useful only when building GCJ, this enables Abstract Window Toolkit (AWT) peer support on top of GTK+
 + + mudflap   : Add support for mudflap, a pointer use checking library
 - - multislot : Allow for SLOTs to include minor version (3.3.4 instead of just 3.3)
 + + nls       : Adds Native Language Support (using gettext - GNU locale utilities)
 - - nopie     : Disable PIE support (NOT FOR GENERAL USE)
 - - nossp     : Disable SSP support (NOT FOR GENERAL USE)
 + + nptl      : Enable support for Native POSIX Threads Library, the new threading module (requires linux-2.6 or better usually)
 - - objc      : Build support for the Objective C code language
 - - objc++    : Build support for the Objective C++ language
 - - objc-gc   : Build support for the Objective C code language Garbage Collector
 + + openmp    : Build support for the OpenMP (support parallel computing), requires >=sys-devel/gcc-4.2 built with USE="openmp"
 - - test      : Workaround to pull in packages needed to run with FEATURES=test. Portage-2.1.2 handles this internally, so don't set it in
                 make.conf/package.use anymore
 - - vanilla   : Do not add extra patches which change default behaviour; DO NOT USE THIS ON A GLOBAL SCALE as the severity of the meaning changes
                 drastically

And they look pretty much the same to me. So bottom line, same USE on HW node and container, former compiles and work fine, latter breaks, which makes me suspect it's something that has to do with openvz, but there ends my ability and I suppose the idea is that developers take over or?

[Comment 9 Joakim 2013-01-03 16:49:25 UTC]

OK here is some more, first Hardware node and then vz Virtual Container and the only difference is  (-nocxx%) at end of VC gcc USE

HW
merc ~ # emerge -pqv '=sys-devel/gcc-4.6.3'
[ebuild   R   ] sys-devel/gcc-4.6.3  USE="cxx fortran mudflap (multilib) nls nptl openmp (-altivec) -bootstrap -build -doc (-fixed-point) -gcj -go -graphite -gtk (-hardened) (-libssp) -multislot -nopie -nossp -objc -objc++ -objc-gc {-test} -vanilla"

merc ~ # emerge -pqv '=sys-libs/glibc-2.16.0'
[ebuild   R   ] sys-libs/glibc-2.16.0  USE="(multilib) -debug -gd (-hardened) -profile (-selinux) -systemtap -vanilla"

VC
sql / # emerge -pqv '=sys-devel/gcc-4.6.3'
[ebuild   R   ] sys-devel/gcc-4.6.3  USE="cxx fortran mudflap (multilib) nls nptl openmp (-altivec) -bootstrap -build -doc (-fixed-point) -gcj -go -graphite -gtk (-hardened) (-libssp) -multislot -nopie -nossp -objc -objc++ -objc-gc {-test} -vanilla (-nocxx%)"

sql / # emerge -pqv '=sys-libs/glibc-2.16.0'
[ebuild   R   ] sys-libs/glibc-2.16.0  USE="(multilib) -debug -gd (-hardened) -profile (-selinux) -systemtap -vanilla"

[Comment 10 Tom Wijsman (TomWij) (RETIRED) 2013-01-03 17:12:13 UTC]

> I suppose the idea is that developers take over

Indeed, this bug seems sufficiently different from the suggested duplicate since you are in a different situation and have shown that the configuration is mostly the same and thus the problem / solution lies elsewhere (and might thus be caused by the openvz container).

I have assigned this bug to the maintainers of gcc and have put the openvz maintainers in CC.

[Comment 11 SpanKY 2013-01-03 18:37:05 UTC]

inside the openvz container, run:
$ echo 'main(){puts("HI");}' | gcc -m32 -x c - -o a.out
$ ./a.out
HI

[Comment 12 Joakim 2013-01-03 19:08:52 UTC]

(In reply to comment #11)
> inside the openvz container, run:
> $ echo 'main(){puts("HI");}' | gcc -m32 -x c - -o a.out
> $ ./a.out
> HI

sql / # echo 'main(){puts("HI");}' | gcc -m32 -x c - -o a.out
sql / # ./a.out
-bash: ./a.out: No such file or directory

[Comment 13 SpanKY 2013-01-03 20:18:54 UTC]

(In reply to comment #12)

your install is broken then

if you want to use a multilib profile, then you must have a glibc & gcc built & installed w/multilib support, as well as the kernel support enabled.

if any of those pieces are missing, then that simple test will fail with "no such file or directory".

*** This bug has been marked as a duplicate of bug 437496 ***

[Comment 14 Joakim 2013-01-03 21:11:01 UTC]

(In reply to comment #13)
> (In reply to comment #12)
> 
> your install is broken then
> 
> if you want to use a multilib profile, then you must have a glibc & gcc
> built & installed w/multilib support, as well as the kernel support enabled.
> 
> if any of those pieces are missing, then that simple test will fail with "no
> such file or directory".
> 
> *** This bug has been marked as a duplicate of bug 437496 ***

Well I can understand the logic in that, but what I don't understand is why this becomes an issue now but haven't been so before, because I haven't changed anything, just updated from one version to the other, same USE flags as with the previous build and both gcc and glibc have built once, but then don't build again.

If my install is broken it must have become so then when glibc-2.16.0 and/or gcc-4.6.3 built the first time, not building properly and how do I get out of this catch-22? I still cannot see how this is a dupe of bug 437496, more than an easy way out... This is clearly openvz releated or the hw node would have been broken too.

[Comment 15 SpanKY 2013-01-03 21:19:22 UTC]

(In reply to comment #14)

i don't know anything about openvz.  i don't see anything broken on the toolchain side.