[gentoo-user] The return of the dreaded "Cannot run C compiled programs"

[gentoo-user] The return of the dreaded "Cannot run C compiled programs"

[Peter Humphrey]

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

I have a four-core 64-bit Celeron box with 4GB RAM, on which I've just 
installed a standard XFCE system on the desktop profile. It all went as 
expected, but when I ran an emerge -e world at the end I had two failures: 
both glibc and sandbox failed with the error in the subject line.

It's some years since I last saw this error, and I'm stuck. I've looked 
through /etc hoping to find something skew-whiff, and I've compared the 
environment with this box's, but nothing stands out.

Finally, following the hint in the portage output, I ran "FEATURES='-sandbox -
usersandbox' emerge -1 --color n sandbox". It made no discernible difference.

I've attached the logs etc from sandbox.

Has anyone a clue?

-- 
Regards.
Peter

[-- Attachment #2: sandbox.info --]
[-- Type: text/plain, Size: 15391 bytes --]

# emerge -pqv '=sys-apps/sandbox-2.12::gentoo'
[ebuild   R   ] sys-apps/sandbox-2.12  ABI_X86="(32) (64) (-x32)"


#####################
Output to tty4 of FEATURES='-sandbox -usersandbox' emerge -1 --color n sandbox
#####################

>>> Emerging (1 of 1) sys-apps/sandbox-2.12::gentoo
 * sandbox-2.12.tar.xz BLAKE2B SHA512 size ;-) ...                                                                                                                     [ ok ]
>>> Unpacking source...
>>> Unpacking sandbox-2.12.tar.xz to /var/tmp/portage/sys-apps/sandbox-2.12/work
>>> Source unpacked in /var/tmp/portage/sys-apps/sandbox-2.12/work
>>> Preparing source in /var/tmp/portage/sys-apps/sandbox-2.12/work/sandbox-2.12 ...
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/sys-apps/sandbox-2.12/work/sandbox-2.12 ...
 * abi_x86_32.x86: running multilib-minimal_abi_src_configure
 * econf: updating sandbox-2.12/config.guess with /usr/share/gnuconfig/config.guess
 * econf: updating sandbox-2.12/config.sub with /usr/share/gnuconfig/config.sub
/var/tmp/portage/sys-apps/sandbox-2.12/work/sandbox-2.12/configure --prefix=/usr --build=i686-pc-linux-gnu --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --disable-dependency-tracking --disable-silent-rules --docdir=/usr/share/doc/sandbox-2.12 --htmldir=/usr/share/doc/sandbox-2.12/html --libdir=/usr/lib32
checking for a BSD-compatible install... /usr/lib/portage/python3.5/ebuild-helpers/xattr/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 whether make supports nested variables... yes
checking whether make supports nested variables... (cached) yes
checking environment state... ok
checking for i686-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc -m32
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... configure: error: in `/var/tmp/portage/sys-apps/sandbox-2.12/work/sandbox-2.12-abi_x86_32.x86':
configure: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details

!!! Please attach the following file when seeking support:
!!! /var/tmp/portage/sys-apps/sandbox-2.12/work/sandbox-2.12-abi_x86_32.x86/config.log
 * ERROR: sys-apps/sandbox-2.12::gentoo failed (configure phase):
 *   econf failed
 *
 * Call stack:
 *               ebuild.sh, line  124:  Called src_configure
 *             environment, line 2816:  Called multilib-minimal_src_configure
 *             environment, line 1934:  Called multilib_foreach_abi 'multilib-minimal_abi_src_configure'
 *             environment, line 2148:  Called multibuild_foreach_variant '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_configure'
 *             environment, line 1864:  Called _multibuild_run '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_configure'
 *             environment, line 1862:  Called _multilib_multibuild_wrapper 'multilib-minimal_abi_src_configure'
 *             environment, line  337:  Called multilib-minimal_abi_src_configure
 *             environment, line 1928:  Called multilib_src_configure
 *             environment, line 2363:  Called econf
 *        phase-helpers.sh, line  666:  Called __helpers_die 'econf failed'
 *   isolated-functions.sh, line  117:  Called die
 * The specific snippet of code:
 *              die "$@"
 *
 * If you need support, post the output of `emerge --info '=sys-apps/sandbox-2.12::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-apps/sandbox-2.12::gentoo'`.
 * If configure failed with a 'cannot run C compiled programs' error, try this:
 * FEATURES='-sandbox -usersandbox' emerge sandbox
 * The complete build log is located at '/var/log/portage/sys-apps:sandbox-2.12:20180326-131024.log'.
 * For convenience, a symlink to the build log is located at '/var/tmp/portage/sys-apps/sandbox-2.12/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-apps/sandbox-2.12/temp/environment'.
 * Working directory: '/var/tmp/portage/sys-apps/sandbox-2.12/work/sandbox-2.12-abi_x86_32.x86'
 * S: '/var/tmp/portage/sys-apps/sandbox-2.12/work/sandbox-2.12'

>>> Failed to emerge sys-apps/sandbox-2.12, Log file:

>>>  '/var/log/portage/sys-apps:sandbox-2.12:20180326-131024.log'
 *
 * The following package has failed to build, install, or execute postinst:
 *
 *  (sys-apps/sandbox-2.12:0/0::gentoo, ebuild scheduled for merge), Log file:
 *   '/var/log/portage/sys-apps:sandbox-2.12:20180326-131024.log'
 *


#####################
/var/log/portage/sys-apps:sandbox-2.12:20180326-130401.log'
#####################

 * Package:    sys-apps/sandbox-2.12
 * Repository: gentoo
 * Maintainer: sandbox@gentoo.org
 * USE:        abi_x86_32 abi_x86_64 amd64 elibc_glibc kernel_linux userland_GNU
 * FEATURES:   preserve-libs userpriv
>>> Unpacking source...
>>> Unpacking sandbox-2.12.tar.xz to /var/tmp/portage/sys-apps/sandbox-2.12/work
>>> Source unpacked in /var/tmp/portage/sys-apps/sandbox-2.12/work
>>> Preparing source in /var/tmp/portage/sys-apps/sandbox-2.12/work/sandbox-2.12 ...
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/sys-apps/sandbox-2.12/work/sandbox-2.12 ...
 * abi_x86_32.x86: running multilib-minimal_abi_src_configure
 * econf: updating sandbox-2.12/config.guess with /usr/share/gnuconfig/config.guess
 * econf: updating sandbox-2.12/config.sub with /usr/share/gnuconfig/config.sub
/var/tmp/portage/sys-apps/sandbox-2.12/work/sandbox-2.12/configure --prefix=/usr --build=i686-pc-linux-gnu --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --disable-dependency-tracking --disable-silent-rules --docdir=/usr/share/doc/sandbox-2.12 --htmldir=/usr/share/doc/sandbox-2.12/html --libdir=/usr/lib32
checking for a BSD-compatible install... /usr/lib/portage/python3.5/ebuild-helpers/xattr/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 whether make supports nested variables... yes
checking whether make supports nested variables... (cached) yes
checking environment state... ok
checking for i686-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc -m32
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... configure: error: in `/var/tmp/portage/sys-apps/sandbox-2.12/work/sandbox-2.12-abi_x86_32.x86':
configure: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details

!!! Please attach the following file when seeking support:
!!! /var/tmp/portage/sys-apps/sandbox-2.12/work/sandbox-2.12-abi_x86_32.x86/config.log
 * ERROR: sys-apps/sandbox-2.12::gentoo failed (configure phase):
 *   econf failed
 * 
 * Call stack:
 *               ebuild.sh, line  124:  Called src_configure
 *             environment, line 2816:  Called multilib-minimal_src_configure
 *             environment, line 1934:  Called multilib_foreach_abi 'multilib-minimal_abi_src_configure'
 *             environment, line 2148:  Called multibuild_foreach_variant '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_configure'
 *             environment, line 1864:  Called _multibuild_run '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_configure'
 *             environment, line 1862:  Called _multilib_multibuild_wrapper 'multilib-minimal_abi_src_configure'
 *             environment, line  337:  Called multilib-minimal_abi_src_configure
 *             environment, line 1928:  Called multilib_src_configure
 *             environment, line 2363:  Called econf
 *        phase-helpers.sh, line  666:  Called __helpers_die 'econf failed'
 *   isolated-functions.sh, line  117:  Called die
 * The specific snippet of code:
 *   		die "$@"
 * 
 * If you need support, post the output of `emerge --info '=sys-apps/sandbox-2.12::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-apps/sandbox-2.12::gentoo'`.
 * If configure failed with a 'cannot run C compiled programs' error, try this:
 * FEATURES='-sandbox -usersandbox' emerge sandbox
 * The complete build log is located at '/var/log/portage/sys-apps:sandbox-2.12:20180326-130401.log'.
 * For convenience, a symlink to the build log is located at '/var/tmp/portage/sys-apps/sandbox-2.12/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-apps/sandbox-2.12/temp/environment'.
 * Working directory: '/var/tmp/portage/sys-apps/sandbox-2.12/work/sandbox-2.12-abi_x86_32.x86'
 * S: '/var/tmp/portage/sys-apps/sandbox-2.12/work/sandbox-2.12'


#####################
emerge --info '=sys-apps/sandbox-2.12::gentoo'
#####################

Portage 2.3.24 (python 3.5.4-final-0, default/linux/amd64/17.0/desktop, gcc-6.4.0, glibc-2.25-r10, 4.9.76-gentoo-r1 x86_64)
=================================================================
                         System Settings
=================================================================
System uname: Linux-4.9.76-gentoo-r1-x86_64-Intel-R-_Celeron-R-_CPU_N3150_@_1.60GHz-with-gentoo-2.4.1
KiB Mem:     3959280 total,   3688832 free
KiB Swap:    4194300 total,   4194300 free
Timestamp of repository gentoo: Sat, 24 Mar 2018 00:28:32 +0000
Head commit of repository gentoo: 8bf7509c70f24881974bba27ec94938c94ba4f65

sh bash 4.4_p12
ld GNU ld (Gentoo 2.29.1 p3) 2.29.1
app-shells/bash:          4.4_p12::gentoo
dev-lang/perl:            5.24.3::gentoo
dev-lang/python:          2.7.14-r1::gentoo, 3.5.4-r1::gentoo
dev-util/cmake:           3.9.6::gentoo
dev-util/pkgconfig:       0.29.2::gentoo
sys-apps/baselayout:      2.4.1-r2::gentoo
sys-apps/openrc:          0.34.11::gentoo
sys-apps/sandbox:         2.12::gentoo
sys-devel/autoconf:       2.13::gentoo, 2.69-r4::gentoo
sys-devel/automake:       1.15.1-r2::gentoo
sys-devel/binutils:       2.29.1-r1::gentoo
sys-devel/gcc:            6.4.0-r1::gentoo
sys-devel/gcc-config:     1.8-r1::gentoo
sys-devel/libtool:        2.4.6-r3::gentoo
sys-devel/make:           4.2.1::gentoo
sys-kernel/linux-headers: 4.13::gentoo (virtual/os-headers)
sys-libs/glibc:           2.25-r10::gentoo
Repositories:

gentoo
    location: /usr/portage
    sync-type: git
    sync-uri: https://github.com/gentoo-mirror/gentoo.git
    priority: -1000

prh-local
    location: /usr/local/portage
    masters: gentoo

ACCEPT_KEYWORDS="amd64"
ACCEPT_LICENSE="* !PUEL"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=native -O2"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/share/config /usr/share/gnupg/qualified.txt"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/dconf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/init.d /etc/pam.d /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo"
CXXFLAGS="-march=native -O2"
DISTDIR="/usr/portage/distfiles"
EMERGE_DEFAULT_OPTS="--backtrack=100 --autounmask=n --with-bdeps y --keep-going --nospinner"
FCFLAGS="-O2 -pipe"
FEATURES="assume-digests binpkg-logs buildpkg config-protect-if-modified distlocks ebuild-locks fixlafiles merge-sync multilib-strict news parallel-fetch parallel-install preserve-libs protect-owned sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync xattr"
FFLAGS="-O2 -pipe"
GENTOO_MIRRORS="ftp://ftp.mirrorservice.org/sites/distfiles.gentoo.org/ ftp://mirror.bytemark.co.uk/gentoo/ http://mirror.bytemark.co.uk/gentoo/ http://mirror.qubenet.net/mirror/gentoo/ http://mirrors.evowise.com/gentoo/ http://www.mirrorservice.org/sites/distfiles.gentoo.org/"
LANG="en_GB.UTF-8"
LDFLAGS="-Wl,-O1 -Wl,--as-needed"
LINGUAS="en_GB en"
MAKEOPTS="--jobs=8 --load-average=16"
PKGDIR="/usr/portage/packages"
PORTAGE_CONFIGROOT="/"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --omit-dir-times --compress --force --whole-file --delete --stats --human-readable --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --exclude=/.git"
PORTAGE_TMPDIR="/var/tmp"
USE="X a52 aac acl acpi alsa amd64 berkdb branding bzip2 cairo cdda cdr cli consolekit crypt cups cxx dbus dri dts dvd dvdr emboss encode exif fam flac gdbm gif glamor gpm gtk iconv ipv6 jpeg lcms libnotify mad mng modules mp3 mp4 mpeg multilib ncurses nls nptl ogg opengl openmp pam pango pcre pdf png policykit ppds qt3support readline sdl seccomp spell ssl startup-notification svg symlink tcpd tiff truetype udev udisks unicode upower usb vorbis wxwidgets x264 xattr xcb xml xv xvid zlib" ABI_X86="64" 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" 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 author" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" CPU_FLAGS_X86="aes mmx mmxext popcnt sse sse2 sse3 sse4_1 sse4_2 ssse3" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock isync itrax mtk3301 nmea ntrip navcom oceanserver oldstyle oncore rtcm104v2 rtcm104v3 sirf skytraq superstar2 timing tsip tripmate tnt ublox ubx" INPUT_DEVICES="evdev" KERNEL="linux" L10N="en-GB en" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LIBREOFFICE_EXTENSIONS="presenter-console presenter-minimizer" OFFICE_IMPLEMENTATION="libreoffice" PHP_TARGETS="php5-6 php7-0" POSTGRES_TARGETS="postgres9_5" PYTHON_SINGLE_TARGET="python3_5" PYTHON_TARGETS="python2_7 python3_5" RUBY_TARGETS="ruby22 ruby23" USERLAND="GNU" VIDEO_CARDS="intel i965" XFCE_PLUGINS="clock trash" 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:  CC, CPPFLAGS, CTARGET, CXX, INSTALL_MASK, LC_ALL, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS

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

sys-apps/sandbox-2.12::gentoo was built with the following:
USE="" ABI_X86="(32) (64) (-x32)"
CFLAGS="-O2 -pipe"
CXXFLAGS="-O2 -pipe"

Re: [gentoo-user] The return of the dreaded "Cannot run C compiled programs"

[Dale]

Peter Humphrey wrote:
> I have a four-core 64-bit Celeron box with 4GB RAM, on which I've just 
> installed a standard XFCE system on the desktop profile. It all went as 
> expected, but when I ran an emerge -e world at the end I had two failures: 
> both glibc and sandbox failed with the error in the subject line.
>
> It's some years since I last saw this error, and I'm stuck. I've looked 
> through /etc hoping to find something skew-whiff, and I've compared the 
> environment with this box's, but nothing stands out.
>
> Finally, following the hint in the portage output, I ran "FEATURES='-sandbox -
> usersandbox' emerge -1 --color n sandbox". It made no discernible difference.
>
> I've attached the logs etc from sandbox.
>
> Has anyone a clue?
>


I did some googling on this.  I seem to recall running into this once to
but can't recall what I did to fix it.  Sorry, I'm getting older. 
Anyway, check how /tmp is mounted, or whatever directory you have
portage's work directory on.  It seems that sometimes it may not be
mounted correctly.  I also found a somewhat recent post on the forums
that mentioned disabling the pie USE flag.  I'm assuming that would be
for gcc.  Posting link to forum to see if it makes more sense to you.

If none of that helps, maybe someone else will come along with something
else to try. 

https://forums.gentoo.org/viewtopic-t-1073552-start-0.html

https://www.howtoforge.com/community/threads/error-cannot-run-c-compiled-programs.44647/

Dale

:-)  :-) 

Re: [gentoo-user] The return of the dreaded "Cannot run C compiled programs"

[Andrés Becerra Sandoval]

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

2018-03-26 9:34 GMT-05:00 Dale <rdalek1967@gmail.com>:

> Peter Humphrey wrote:
> > I have a four-core 64-bit Celeron box with 4GB RAM, on which I've just
> > installed a standard XFCE system on the desktop profile. It all went as
> > expected, but when I ran an emerge -e world at the end I had two
> failures:
> > both glibc and sandbox failed with the error in the subject line.
> >
> > It's some years since I last saw this error, and I'm stuck. I've looked
> > through /etc hoping to find something skew-whiff, and I've compared the
> > environment with this box's, but nothing stands out.
> >
> > Finally, following the hint in the portage output, I ran
> "FEATURES='-sandbox -
> > usersandbox' emerge -1 --color n sandbox". It made no discernible
> difference.
> >
> > I've attached the logs etc from sandbox.
> >
> > Has anyone a clue?
> >
>
>
​Peter,

I would check /etc/portage/make.conf for ​a typo in the main variables
(CHOST, CFLAGS,CXXFLAGS) ....

[-- Attachment #2: Type: text/html, Size: 1971 bytes --]

Re: [gentoo-user] The return of the dreaded "Cannot run C compiled programs"

[Peter Humphrey]

On Monday, 26 March 2018 15:34:30 BST Dale wrote:

> I did some googling on this.

Thanks. Looks like you turned something up that I didn't.

> I seem to recall running into this once to
> but can't recall what I did to fix it.  Sorry, I'm getting older. 
> Anyway, check how /tmp is mounted, or whatever directory you have
> portage's work directory on.  It seems that sometimes it may not be
> mounted correctly.  I also found a somewhat recent post on the forums
> that mentioned disabling the pie USE flag.  I'm assuming that would be
> for gcc.  Posting link to forum to see if it makes more sense to you.
> 
> If none of that helps, maybe someone else will come along with something
> else to try. 
> 
> https://forums.gentoo.org/viewtopic-t-1073552-start-0.html

I did what it suggested but it didn't help.

> https://www.howtoforge.com/community/threads/error-cannot-run-c-compiled-pro
> grams.44647/

You and Andres mentioned tmp directories. I have a sepaate partition for /var/
tmp/portage, so I tried remounting it with specifice options rw and exec; I 
also tried just unmounting it. No change.

-- 
Regards
Peter.

Re: [gentoo-user] The return of the dreaded "Cannot run C compiled programs"

[Daniel Frey]

On 03/26/18 06:19, Peter Humphrey wrote:
> I have a four-core 64-bit Celeron box with 4GB RAM, on which I've just 
> installed a standard XFCE system on the desktop profile. It all went as 
> expected, but when I ran an emerge -e world at the end I had two failures: 
> both glibc and sandbox failed with the error in the subject line.
> 
> It's some years since I last saw this error, and I'm stuck. I've looked 
> through /etc hoping to find something skew-whiff, and I've compared the 
> environment with this box's, but nothing stands out.
> 
> Finally, following the hint in the portage output, I ran "FEATURES='-sandbox -
> usersandbox' emerge -1 --color n sandbox". It made no discernible difference.
> 
> I've attached the logs etc from sandbox.
> 
> Has anyone a clue?
> 

I ran into this some time ago and one of the updates removed the /lib ->
/lib64 symlink.

I simply ran `ln -s /lib64 /lib` and it was fine after that.

Dan

Re: [gentoo-user] The return of the dreaded "Cannot run C compiled programs"

[Peter Humphrey]

On Tuesday, 27 March 2018 01:24:09 BST Daniel Frey wrote:

> I ran into this some time ago and one of the updates removed the /lib ->
> /lib64 symlink.
> 
> I simply ran `ln -s /lib64 /lib` and it was fine after that.

Nice idea, Dan, but that isn't it in this case: 

# /bin/ls -ld /lib
lrwxrwxrwx 1 root root 5 Mar 12 00:08 /lib -> lib64

-- 
Regards
Peter

Re: [gentoo-user] The return of the dreaded "Cannot run C compiled programs"

[Alexander Kapshuk]

On Tue, Mar 27, 2018 at 12:01 PM, Peter Humphrey <peter@prh.myzen.co.uk> wrote:
> On Tuesday, 27 March 2018 01:24:09 BST Daniel Frey wrote:
>
>> I ran into this some time ago and one of the updates removed the /lib ->
>> /lib64 symlink.
>>
>> I simply ran `ln -s /lib64 /lib` and it was fine after that.
>
> Nice idea, Dan, but that isn't it in this case:
>
> # /bin/ls -ld /lib
> lrwxrwxrwx 1 root root 5 Mar 12 00:08 /lib -> lib64
>
> --
> Regards
> Peter
>
>

See if this post helps:
Failed to emerge sys-apps/sandbox-2.12:
https://forums.gentoo.org/viewtopic-t-1076582-start-0.html

Re: [gentoo-user] The return of the dreaded "Cannot run C compiled programs"

[Peter Humphrey]

On Tuesday, 27 March 2018 10:33:45 BST Alexander Kapshuk wrote:
> On Tue, Mar 27, 2018 at 12:01 PM, Peter Humphrey <peter@prh.myzen.co.uk> 
wrote:
> > On Tuesday, 27 March 2018 01:24:09 BST Daniel Frey wrote:
> >> I ran into this some time ago and one of the updates removed the /lib ->
> >> /lib64 symlink.
> >> 
> >> I simply ran `ln -s /lib64 /lib` and it was fine after that.
> > 
> > Nice idea, Dan, but that isn't it in this case:
> > 
> > # /bin/ls -ld /lib
> > lrwxrwxrwx 1 root root 5 Mar 12 00:08 /lib -> lib64
> > 
> > --
> > Regards
> > Peter
> 
> See if this post helps:
> Failed to emerge sys-apps/sandbox-2.12:
> https://forums.gentoo.org/viewtopic-t-1076582-start-0.html

No, it doesn't look like the same problem: he seems not to have failed with 
the same error "cannot run C compiled programs."

-- 
Regards
Peter

[gentoo-user] Re: The return of the dreaded "Cannot run C compiled programs"

[Ian Zimmerman]

Have you looked at config.log in the work directory after the failed
build?  Those are very verbose, including the source code of tests run.

-- 
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
To reply privately _only_ on Usenet and on broken lists
which rewrite From, fetch the TXT record for no-use.mooo.com.

Re: [gentoo-user] The return of the dreaded "Cannot run C compiled programs"

[Todd Goodman]

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

What does 'gcc-config -l' show?

Todf

⁣Sent from BlueMail ​

On Mar 27, 2018, 5:02 AM, at 5:02 AM, Peter Humphrey <peter@prh.myzen.co.uk> wrote:
>On Tuesday, 27 March 2018 01:24:09 BST Daniel Frey wrote:
>
>> I ran into this some time ago and one of the updates removed the /lib
>->
>> /lib64 symlink.
>>
>> I simply ran `ln -s /lib64 /lib` and it was fine after that.
>
>Nice idea, Dan, but that isn't it in this case: 
>
># /bin/ls -ld /lib
>lrwxrwxrwx 1 root root 5 Mar 12 00:08 /lib -> lib64
>
>--
>Regards
>Peter

[-- Attachment #2: Type: text/html, Size: 1205 bytes --]

Re: [gentoo-user] The return of the dreaded "Cannot run C compiled programs"

[Peter Humphrey]

On Wednesday, 28 March 2018 17:15:38 BST Todd Goodman wrote:
> What does 'gcc-config -l' show?

That I have just the one version of GCC installed. But see my reply to Floyd.

-- 
Regards
Peter

Re: [gentoo-user] The return of the dreaded "Cannot run C compiled programs"

[Mike Gilbert]

On Mon, Mar 26, 2018 at 9:19 AM, Peter Humphrey <peter@prh.myzen.co.uk> wrote:
> I have a four-core 64-bit Celeron box with 4GB RAM, on which I've just
> installed a standard XFCE system on the desktop profile. It all went as
> expected, but when I ran an emerge -e world at the end I had two failures:
> both glibc and sandbox failed with the error in the subject line.
>
> It's some years since I last saw this error, and I'm stuck. I've looked
> through /etc hoping to find something skew-whiff, and I've compared the
> environment with this box's, but nothing stands out.
>
> Finally, following the hint in the portage output, I ran "FEATURES='-sandbox -
> usersandbox' emerge -1 --color n sandbox". It made no discernible difference.
>
> I've attached the logs etc from sandbox.
>
> Has anyone a clue?

configure: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details

Please take a look at the config.log file in the build directory; this
will probably have more detailed error information. Attach it here if
you would like me to take a look at it.

Re: [gentoo-user] The return of the dreaded "Cannot run C compiled programs"

[Floyd Anderson]

On Mon, 26 Mar 2018 14:19:07 +0100
Peter Humphrey <peter@prh.myzen.co.uk> wrote:
> […]
>It's some years since I last saw this error, and I'm stuck. I've looked
>through /etc hoping to find something skew-whiff, and I've compared the
>environment with this box's, but nothing stands out.
> […]
>
>Has anyone a clue?

Just a guess, because you’re compiling multilib – look whether your 
kernel is able to run 32bit binaries. Check, e.g. the setting for kernel 
option CONFIG_IA32_EMULATION.


-- 
Regards,
floyd

Re: [gentoo-user] The return of the dreaded "Cannot run C compiled programs"

[Peter Humphrey]

On Tuesday, 27 March 2018 16:47:32 BST Floyd Anderson wrote:

> Just a guess, because you’re compiling multilib – look whether your
> kernel is able to run 32bit binaries. Check, e.g. the setting for kernel
> option CONFIG_IA32_EMULATION.

That's it! I just reused the .config from the previous no-multilib system 
without thinking about it. Stupid boy (TM).

Many thanks, Floyd.

-- 
Regards
Peter

Re: [gentoo-user] The return of the dreaded "Cannot run C compiled programs"

[Floyd Anderson]

On Wed, 28 Mar 2018 08:38:10 +0100
Peter Humphrey <peter@prh.myzen.co.uk> wrote:
>On Tuesday, 27 March 2018 16:47:32 BST Floyd Anderson wrote:
>
>> Just a guess, because you’re compiling multilib – look whether your
>> kernel is able to run 32bit binaries. Check, e.g. the setting for kernel
>> option CONFIG_IA32_EMULATION.
>
>That's it! I just reused the .config from the previous no-multilib system
>without thinking about it. Stupid boy (TM).

You’re not alone. I wanted to shrink my kernel size and switched that 
kernel option off (beside others) – the error occurred weeks later.


-- 
Regards,
floyd

Re: [gentoo-user] The return of the dreaded "Cannot run C compiled programs"

[thelma]

On 03/26/2018 07:19 AM, Peter Humphrey wrote:
> I have a four-core 64-bit Celeron box with 4GB RAM, on which I've just 
> installed a standard XFCE system on the desktop profile. It all went as 
> expected, but when I ran an emerge -e world at the end I had two failures: 
> both glibc and sandbox failed with the error in the subject line.
> 
> It's some years since I last saw this error, and I'm stuck. I've looked 
> through /etc hoping to find something skew-whiff, and I've compared the 
> environment with this box's, but nothing stands out.
> 
> Finally, following the hint in the portage output, I ran "FEATURES='-sandbox -
> usersandbox' emerge -1 --color n sandbox". It made no discernible difference.
> 
> I've attached the logs etc from sandbox.
> 
> Has anyone a clue?

Are you using gcc-6.4.0-r1?
When compiling large packages change in make.conf  MAKEOPTS="-j1"

I had happen twice to me.
It seems to me the gcc-6.4.0-r1 much more resource hungry or there is
a bug in it.

--
Thelma