LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Gentoo (http://www.linuxquestions.org/questions/gentoo-87/)
-   -   emerge sandbox fails with compiler error (http://www.linuxquestions.org/questions/gentoo-87/emerge-sandbox-fails-with-compiler-error-4175428968/)

MarcusWebb1966 09-25-2012 12:26 PM

emerge sandbox fails with compiler error
 
Ok, please understand I've nearly lost the will to live over this stuff so I may not have googled everything under the sun... however, when I try to emerge sandbox I get the following error:

Code:

checking whether we are cross compiling... configure: error: in `/usr/portage/tmp/portage/sys-apps/sandbox-2.5/work/build-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:
!!! /usr/portage/tmp/portage/sys-apps/sandbox-2.5/work/build-x86/config.log
 * ERROR: sys-apps/sandbox-2.5 failed (compile phase):
 *  econf failed
 *
 * Call stack:
 *          ebuild.sh, line  85:  Called src_compile
 *        environment, line 2555:  Called multijob_child_init 'sb_configure'
 *        environment, line 2073:  Called sb_configure
 *        environment, line 2502:  Called econf
 *  phase-helpers.sh, line  467:  Called die
 * The specific snippet of code:
 *                      die "econf failed"
 *
 * If you need support, post the output of `emerge --info '=sys-apps/sandbox-2.5'`,
 * the complete build log and the output of `emerge -pqv '=sys-apps/sandbox-2.5'`.
 * If configure failed with a 'cannot run C compiled programs' error, try this:
 * FEATURES=-sandbox emerge sandbox
/usr/lib64/portage/bin/isolated-functions.sh: line 214: wait: `econf failed': not a pid or valid job spec
 * The complete build log is located at '/usr/portage/log/sys-apps:sandbox-2.5:20120925-161859.log'.
 * For convenience, a symlink to the build log is located at '/usr/portage/tmp/portage/sys-apps/sandbox-2.5/temp/build.log'.
 * The ebuild environment file is located at '/usr/portage/tmp/portage/sys-apps/sandbox-2.5/temp/environment'.
 * Working directory: '/usr/portage/tmp/portage/sys-apps/sandbox-2.5/work/build-x86'
 * S: '/usr/portage/tmp/portage/sys-apps/sandbox-2.5/work/sandbox-2.5'

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

>>>  '/usr/portage/log/sys-apps:sandbox-2.5:20120925-161859.log'

 * Messages for package sys-apps/sandbox-2.5:

 * This profile is merely a convenience for people who require a more
 * minimal profile, yet are unable to use hardened due to restrictions in
 * the software being used on the server. If you seek a secure
 * production server profile, please check the Hardened project
 * (http://hardened.gentoo.org)
 * ERROR: sys-apps/sandbox-2.5 failed (compile phase):
 *  econf failed
 *
 * Call stack:
 *          ebuild.sh, line  85:  Called src_compile
 *        environment, line 2555:  Called multijob_child_init 'sb_configure'
 *        environment, line 2073:  Called sb_configure
 *        environment, line 2502:  Called econf
 *  phase-helpers.sh, line  467:  Called die
 * The specific snippet of code:
 *                      die "econf failed"
 *
 * If you need support, post the output of `emerge --info '=sys-apps/sandbox-2.5'`,
 * the complete build log and the output of `emerge -pqv '=sys-apps/sandbox-2.5'`.
 * If configure failed with a 'cannot run C compiled programs' error, try this:
 * FEATURES=-sandbox emerge sandbox
 * The complete build log is located at '/usr/portage/log/sys-apps:sandbox-2.5:20120925-161859.log'.
 * For convenience, a symlink to the build log is located at '/usr/portage/tmp/portage/sys-apps/sandbox-2.5/temp/build.log'.
 * The ebuild environment file is located at '/usr/portage/tmp/portage/sys-apps/sandbox-2.5/temp/environment'.
 * Working directory: '/usr/portage/tmp/portage/sys-apps/sandbox-2.5/work/build-x86'
 * S: '/usr/portage/tmp/portage/sys-apps/sandbox-2.5/work/sandbox-2.5'

So, please believe me when I tell you I've tried:
Code:

FEATURES=-sandbox emerge sandbox
Code:

FEATURES="-sandbox -usersandbox" emerge sandbox
and this hasn't worked.
SO

any suggestions gratefully, etc...

hydraMax 10-01-2012 03:06 AM

Erm... Why are you emerging sys-apps/sandbox? It should already be installed on the system as a system application.

MarcusWebb1966 10-02-2012 04:48 AM

Reasonable question, hydraMax:

The short answer is, I wasn't initially. I was trying to update apache. During this I got compiler errors. Various bits of googling led me to find a solution that said I needed to update the toolchain. As part of the failure to emerge the toolchain it was suggested that I try
Code:

FEATURES="-sandbox" emerge sandbox
and when that didn't work, I did more googling which led me to try to
Code:

FEATURES="-sandbox -usersandbox" emerge sandbox
sandbox already exists on the system, it's just that it is rather old...

hydraMax 10-03-2012 04:09 AM

Hmm... Well, can you post / pastebin (the relevant parts) of the aforementioned config log and build log? And your emerge --info?


All times are GMT -5. The time now is 03:10 PM.