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"

[Todd Goodman]

What does 'gcc-config -l' show?

Todf

⁣Sent from BlueMail ​

On Mar 27, 2018, 5:02 AM, at 5:02 AM, Peter Humphrey  
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

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  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"

[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"

[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

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  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"

[Mike Gilbert]

On Mon, Mar 26, 2018 at 9: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?

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"

[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  
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

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  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 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"

[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 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"

[Andrés Becerra Sandoval]

2018-03-26 9:34 GMT-05:00 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?
> >
>
>
​Peter,

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

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

:-)  :-)