Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 203025 - sys-apps/sandbox-1.2.18.1-r2 gcc problem
Summary: sys-apps/sandbox-1.2.18.1-r2 gcc problem
Status: VERIFIED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: AMD64 Linux
: High normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-12-22 15:15 UTC by Matteo Spreafico
Modified: 2007-12-22 15:57 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
config.log (config.log,7.07 KB, text/plain)
2007-12-22 15:16 UTC, Matteo Spreafico
Details
build.log (build.log,2.49 KB, text/plain)
2007-12-22 15:16 UTC, Matteo Spreafico
Details
environment (environment,99.99 KB, text/plain)
2007-12-22 15:17 UTC, Matteo Spreafico
Details
emerge --info (emerge.info,9.21 KB, text/plain)
2007-12-22 15:18 UTC, Matteo Spreafico
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Matteo Spreafico 2007-12-22 15:15:32 UTC
Atlantis ~ # FEATURES=-sandbox emerge sandbox

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild     U ] sys-apps/sandbox-1.2.18.1-r2 [1.2.18.1] 0 kB 

Total: 1 package (1 upgrade), Size of downloads: 0 kB

>>> Verifying ebuild Manifests...

>>> Emerging (1 of 1) sys-apps/sandbox-1.2.18.1-r2 to /
 * sandbox-1.2.18.1.tar.bz2 RMD160 SHA1 SHA256 size ;-) ...                                                                                            [ ok ]
 * checking ebuild checksums ;-) ...                                                                                                                   [ ok ]
 * checking auxfile checksums ;-) ...                                                                                                                  [ ok ]
 * checking miscfile checksums ;-) ...                                                                                                                 [ ok ]
 * checking sandbox-1.2.18.1.tar.bz2 ;-) ...                                                                                                           [ ok ]
>>> Unpacking source...
>>> Unpacking sandbox-1.2.18.1.tar.bz2 to /gentoo/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/work
 * Applying sandbox-1.2.18.1-open-normal-fail.patch ...                                                                                                [ ok ]
 * Applying sandbox-1.2.18.1-open-cloexec.patch ...                                                                                                    [ ok ]
>>> Source unpacked.
>>> Compiling source in /gentoo/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/work/sandbox-1.2.18.1 ...
 * If configure fails with a 'cannot run C compiled programs' error, try this:
 * FEATURES=-sandbox emerge sandbox
 * Configuring sandbox for ABI=x86...
 * econf: updating sandbox-1.2.18.1/config.guess with /usr/share/gnuconfig/config.guess
 * econf: updating sandbox-1.2.18.1/config.sub with /usr/share/gnuconfig/config.sub
../sandbox-1.2.18.1//configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib32 --enable-multilib --build=i686-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for i686-pc-linux-gnu-gcc... no
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... 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:
!!! /gentoo/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/work/build-x86-x86_64-pc-linux-gnu/config.log
 * 
 * ERROR: sys-apps/sandbox-1.2.18.1-r2 failed.
 * Call stack:
 *               ebuild.sh, line   46:  Called src_compile
 *             environment, line 2406:  Called econf 'src_compile' 'src_compile'
 *               ebuild.sh, line  506:  Called die
 * The specific snippet of code:
 *   			die "econf failed"
 *  The die message:
 *   econf failed
 * 
 * If you need support, post the topmost build error, and the call stack if relevant.
 * A complete build log is located at '/gentoo/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/temp/build.log'.
 * The ebuild environment file is located at '/gentoo/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/temp/environment'.
 * 
Atlantis ~ # find /usr/bin | xargs strings -f 2> /dev/null | grep "Unable to determine executable" | cut -d : -f 1
Atlantis ~ # 


Reproducible: Always

Steps to Reproduce:
Comment 1 Matteo Spreafico 2007-12-22 15:16:26 UTC
Created attachment 139108 [details]
config.log
Comment 2 Matteo Spreafico 2007-12-22 15:16:56 UTC
Created attachment 139110 [details]
build.log
Comment 3 Matteo Spreafico 2007-12-22 15:17:37 UTC
Created attachment 139112 [details]
environment
Comment 4 Matteo Spreafico 2007-12-22 15:18:51 UTC
Created attachment 139114 [details]
emerge --info
Comment 5 Jakub Moc (RETIRED) gentoo-dev 2007-12-22 15:34:05 UTC
<snip>
configure:2352: ./a.out
../sandbox-1.2.18.1//configure: line 2353: ./a.out: cannot execute binary file
configure:2355: $? = 126
configure:2364: error: cannot run C compiled programs.
</snip>

You are missing IA32 emulation in kernel.

http://www.gentoo.org/doc/en/gentoo-amd64-faq.xml#kernel
Comment 6 Matteo Spreafico 2007-12-22 15:39:50 UTC
Yes, I disabled that option in the kernel, I want a 64bit only system.
It's very strange I need to enable it for the sandbox.
Is it a limit of the current sandbox?
Comment 7 Jakub Moc (RETIRED) gentoo-dev 2007-12-22 15:50:35 UTC
(In reply to comment #6)
> Yes, I disabled that option in the kernel, I want a 64bit only system.
> It's very strange I need to enable it for the sandbox.
> Is it a limit of the current sandbox?

No, it's not a limit of the current sandbox, it's a feature - you cannot have a 64bit-only system at all with your profile set. You need one of the no-multilib subprofiles (which are unsupported).


Comment 8 Matteo Spreafico 2007-12-22 15:57:47 UTC
(In reply to comment #7)

> No, it's not a limit of the current sandbox, it's a feature - you cannot have a
> 64bit-only system at all with your profile set. You need one of the no-multilib
> subprofiles (which are unsupported).

Ok, thanks, I'll enable the IA32 emulation.

I hope there will be in the (near) future a *supported* 64bit-only (sub)profile.