On minimal gentoo system that is actually running inside virtualbox on amd64 hw emulating i486 hw command "emerge x11" fails when emerging ghc-7.6.3. It looks like configure scripts tries to select wrong compiler. Gcc itself is functional, but in i686-pc-linux-gnu-gcc flavour. output goes like this: * econf: updating ghc-7.6.3/libraries/unix/config.guess with /usr/share/gnuconfig/config.guess ./configure --prefix=/usr --build=i486-pc-linux-gnu --host=i486-pc-linux-gnu --target=i486-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib --with-gcc=i486-pc-linux-gnu-gcc --enable-bootstrap-with-devel-snapshot checking for gfind... no checking for find... /usr/bin/find checking for sort... /usr/bin/sort checking for ghc... /var/tmp/portage/dev-lang/ghc-7.6.3-r1/work/usr/bin/ghc checking version of ghc... 7.6.3 checking build system type... i486-pc-linux-gnu checking host system type... i486-pc-linux-gnu checking target system type... i486-pc-linux-gnu HOST: i486-pc-linux-gnu GHC build : i386-unknown-linux GHC host : i386-unknown-linux GHC target : i386-unknown-linux configure: Building in-tree ghc-pwd ghc: could not execute: i686-pc-linux-gnu-gcc configure: error: Building ghc-pwd failed
Created attachment 402778 [details] emerge.info of the machine
Please attach the full build log.
Created attachment 403146 [details] build log from "emerge x11"
Please find attached build.log. In addition it might be worth noting that inside virtualbox $ uname -a Linux entuu 3.18.11-gentoo #1 SMP Wed Apr 15 00:41:03 EEST 2015 i686 AMD Athlon( tm) 64 X2 Dual Core Processor 4600+ AuthenticAMD GNU/Linux $ cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 15 model : 43 model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4600+ stepping : 1 cpu MHz : 1795.979 cache size : 512 KB physical id : 0 siblings : 1 core id : 0 cpu cores : 1 apicid : 0 ... and $ gcc -v Using built-in specs. COLLECT_GCC=/usr/i486-pc-linux-gnu/gcc-bin/4.8.4/gcc COLLECT_LTO_WRAPPER=/usr/libexec/gcc/i486-pc-linux-gnu/4.8.4/lto-wrapper Target: i486-pc-linux-gnu Configured with: /var/tmp/portage/sys-devel/gcc-4.8.4/work/gcc-4.8.4/configure - -host=i486-pc-linux-gnu --build=i486-pc-linux-gnu --prefix=/usr --bindir=/usr/i4 86-pc-linux-gnu/gcc-bin/4.8.4 --includedir=/usr/lib/gcc/i486-pc-linux-gnu/4.8.4/ include --datadir=/usr/share/gcc-data/i486-pc-linux-gnu/4.8.4 --mandir=/usr/shar e/gcc-data/i486-pc-linux-gnu/4.8.4/man --infodir=/usr/share/gcc-data/i486-pc-lin ux-gnu/4.8.4/info --with-gxx-include-dir=/usr/lib/gcc/i486-pc-linux-gnu/4.8.4/in clude/g++-v4 --with-python-dir=/share/gcc-data/i486-pc-linux-gnu/4.8.4/python -- enable-languages=c,c++,fortran --enable-obsolete --enable-secureplt --disable-we rror --with-system-zlib --enable-nls --without-included-gettext --enable-checkin g=release --with-bugurl=https://bugs.gentoo.org/ --with-pkgversion='Gentoo 4.8.4 p1.5, pie-0.6.1' --enable-libstdcxx-time --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu --disable-multilib --disable-altivec --disable-fixed-point --with-arch=i486 --enable-targets=all --disable-libgcj -- enable-libgomp --disable-libmudflap --disable-libssp --enable-lto --without-cloo g --enable-libsanitizer Thread model: posix gcc version 4.8.4 (Gentoo 4.8.4 p1.5, pie-0.6.1) if that helps at all. The system has been emerged as "i486", e.g. in make.conf CFLAGS="-O2 -march=i486" -pipe"
> $ cat /proc/cpuinfo > > processor : 0 > vendor_id : AuthenticAMD > cpu family : 15 > model : 43 > model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4600+ > stepping : 1 > cpu MHz : 1795.979 > cache size : 512 KB > physical id : 0 > siblings : 1 > core id : 0 > cpu cores : 1 > apicid : 0 > Target: i486-pc-linux-gnu Yeah, it's a known issue of prebuilt binaries using i686 CHOST. One day we will workaround it, but do you really need dev-haskell/x11 on i486 triplet and not x11-base/xorg-x11 package?
*** This bug has been marked as a duplicate of bug 531016 ***