Summary: | sys-apps/sandbox: ../sandbox-1.2.18.1//configure: line 2353: ./a.out: cannot execute binary file | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Walter <walter> |
Component: | [OLD] Core system | Assignee: | Sandbox Maintainers <sandbox> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | l |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
config.log
complete build log |
Description
Walter
2008-07-21 02:07:48 UTC
Created attachment 160975 [details]
config.log
Try this (from bug #133209): FEATURES=-sandbox emerge sandbox (In reply to comment #2) > Try this (from bug #133209): > FEATURES=-sandbox emerge sandbox If you read the original bug report you can see: Reproducible: Always Steps to Reproduce: 1. FEATURES="-sandbox -usersandbox" emerge sandbox ../sandbox-1.2.18.1//configure: line 2353: ./a.out: cannot execute binary file Are you by any chance using ACLs on /var/tmp or is noexec enabled? > ../sandbox-1.2.18.1//configure: line 2353: ./a.out: cannot execute binary file
>
> Are you by any chance using ACLs on /var/tmp or is noexec enabled?
I've definitely not manually configured these. How would I check if
they're active?
Could you please post the entire sys-apps/sandbox build log? I'm ruling out bug #216793 and bug #227947. Bug #227947 and bug #202811 look similar because of: 'configure:1942: checking for i686-pc-linux-gnu-gcc' Do you have anything called /usr/bin/i686-* ? > Bug #227947 and bug #202811 look similar because of:
> 'configure:1942: checking for i686-pc-linux-gnu-gcc'
>
> Do you have anything called /usr/bin/i686-* ?
No.
Created attachment 161108 [details]
complete build log
I have the same problem on one of my machines (amd64). I can confirm that /var/tmp is *not* mounted noexec and that ACLs are not in use. I can also confirm that something like: echo 'int main(void) { return 0; }' > foo.c gcc foo.c ./a.out works correctly as root. Anyone looking at this or should I rebuild my entire system? I'm done waiting for a response... five weeks is long enough. I'm zapping the system in question for a total rebuild (there goes another two days). Do hope the bug eventually gets solved... :( This has to go in the 'worst gentoo experience yet' basket. After some judicious strace usage, and help from IRC, I found that gcc was creating a 32-bit ELF executable which was being run as part of configure. If the kernel option CONFIG_IA32_EMULATION is set to N then this of course fails as the kernel can't run 32-bit executables. The solution is either to enable CONFIG_IA32_EMULATION or to use a no-multilib profile (which would cause sandbox to be compiled without 64-bit executables). You cannot mix and match the two. if you use a multilib profile you had better well make sure your kernel is properly configured |