Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
emerge ERROR: sys-apps/sandbox-2.10-r3::gentoo failed (confi
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Installing Gentoo
View previous topic :: View next topic  
Author Message
steven101082
n00b
n00b


Joined: 14 Mar 2017
Posts: 2

PostPosted: Tue Mar 14, 2017 5:25 am    Post subject: emerge ERROR: sys-apps/sandbox-2.10-r3::gentoo failed (confi Reply with quote

when i run "emerge --update --deep --newuse @world" as the last command of my gentoo install,
i get this error.

Code:
Performing Global Updates
(Could take a couple of minutes if you have a lot of binary packages.)



 * IMPORTANT: 12 news items need reading for repository 'gentoo'.
 * Use eselect news read to view new items.

(chroot) livecd / # nice --20 eselect profile set 9
(chroot) livecd / # nice --20 emerge --update --deep --newuse @world                                   
                                                                                                       
 * IMPORTANT: 12 news items need reading for repository 'gentoo'.                                     
 * Use eselect news read to view new items.                                                           
                                                                                                       
Calculating dependencies... done!                                                                     
                                                                                                       
>>> Verifying ebuild manifests                                                                         
>>> Running pre-merge checks for sys-devel/gcc-4.9.4                                                   
                                                                                                       
>>> Emerging (1 of 16) sys-devel/binutils-config-5-r3::gentoo                                         
>>> Unpacking source...                                                                               
>>> Source unpacked in /var/tmp/portage/sys-devel/binutils-config-5-r3/work
>>> Preparing source in /var/tmp/portage/sys-devel/binutils-config-5-r3/work ...
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/sys-devel/binutils-config-5-r3/work ...
>>> Source configured.
>>> Compiling source in /var/tmp/portage/sys-devel/binutils-config-5-r3/work ...
>>> Source compiled.
>>> Test phase [not enabled]: sys-devel/binutils-config-5-r3

>>> Install binutils-config-5-r3 into /var/tmp/portage/sys-devel/binutils-config-5-r3/image/ category sys-devel
>>> Completed installing binutils-config-5-r3 into /var/tmp/portage/sys-devel/binutils-config-5-r3/image/

 * Final size of build directory: 0 KiB
 * Final size of installed tree: 20 KiB

ecompressdir: bzip2 -9 /usr/share/man

>>> Installing (1 of 16) sys-devel/binutils-config-5-r3::gentoo

>>> Emerging (2 of 16) sys-apps/sandbox-2.10-r3::gentoo
 * sandbox-2.10.tar.xz SHA256 SHA512 WHIRLPOOL size ;-) ...                                     [ ok ]
>>> Unpacking source...
>>> Unpacking sandbox-2.10.tar.xz to /var/tmp/portage/sys-apps/sandbox-2.10-r3/work
>>> Source unpacked in /var/tmp/portage/sys-apps/sandbox-2.10-r3/work
>>> Preparing source in /var/tmp/portage/sys-apps/sandbox-2.10-r3/work/sandbox-2.10 ...
 * Applying sandbox-2.10-memory-corruption.patch ...                                            [ ok ]
 * Applying sandbox-2.10-disable-same.patch ...                                                 [ ok ]
 * Applying sandbox-2.10-fix-opendir.patch ...                                                  [ ok ]
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/sys-apps/sandbox-2.10-r3/work/sandbox-2.10 ...
 * abi_x86_64.amd64: running multilib-minimal_abi_src_configure
 * econf: updating sandbox-2.10/config.guess with /usr/share/gnuconfig/config.guess
 * econf: updating sandbox-2.10/config.sub with /usr/share/gnuconfig/config.sub
/var/tmp/portage/sys-apps/sandbox-2.10-r3/work/sandbox-2.10/configure --prefix=/usr --build=X86_64-pc-linux-gnu --host=X86_64-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 --libdir=/usr/lib64
checking for a BSD-compatible install... /var/tmp/portage/._portage_reinstall_.p1an5k8e/bin/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 X86_64-pc-linux-gnu-gcc... no
checking for gcc... gcc
checking whether the C compiler works... no
configure: error: in `/var/tmp/portage/sys-apps/sandbox-2.10-r3/work/sandbox-2.10-abi_x86_64.amd64':
configure: error: C compiler cannot create executables
See `config.log' for more details

!!! Please attach the following file when seeking support:
!!! /var/tmp/portage/sys-apps/sandbox-2.10-r3/work/sandbox-2.10-abi_x86_64.amd64/config.log
 * ERROR: sys-apps/sandbox-2.10-r3::gentoo failed (configure phase):
 *   econf failed
 *
 * Call stack:
 *               ebuild.sh, line  115:  Called src_configure
 *             environment, line 2984:  Called multilib-minimal_src_configure
 *             environment, line 2089:  Called multilib_foreach_abi 'multilib-minimal_abi_src_configure'
 *             environment, line 2303:  Called multibuild_foreach_variant '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_configure'
 *             environment, line 1950:  Called _multibuild_run '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_configure'
 *             environment, line 1948:  Called _multilib_multibuild_wrapper 'multilib-minimal_abi_src_configure'
 *             environment, line  374:  Called multilib-minimal_abi_src_configure
 *             environment, line 2083:  Called multilib_src_configure
 *             environment, line 2518:  Called econf
 *        phase-helpers.sh, line  665:  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.10-r3::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-apps/sandbox-2.10-r3::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/tmp/portage/sys-apps/sandbox-2.10-r3/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-apps/sandbox-2.10-r3/temp/environment'.
 * Working directory: '/var/tmp/portage/sys-apps/sandbox-2.10-r3/work/sandbox-2.10-abi_x86_64.amd64'
 * S: '/var/tmp/portage/sys-apps/sandbox-2.10-r3/work/sandbox-2.10'

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

>>>  '/var/tmp/portage/sys-apps/sandbox-2.10-r3/temp/build.log'

 * Messages for package sys-apps/sandbox-2.10-r3:

 * ERROR: sys-apps/sandbox-2.10-r3::gentoo failed (configure phase):
 *   econf failed
 *
 * Call stack:
 *               ebuild.sh, line  115:  Called src_configure
 *             environment, line 2984:  Called multilib-minimal_src_configure
 *             environment, line 2089:  Called multilib_foreach_abi 'multilib-minimal_abi_src_configure'
 *             environment, line 2303:  Called multibuild_foreach_variant '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_configure'
 *             environment, line 1950:  Called _multibuild_run '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_configure'
 *             environment, line 1948:  Called _multilib_multibuild_wrapper 'multilib-minimal_abi_src_configure'
 *             environment, line  374:  Called multilib-minimal_abi_src_configure
 *             environment, line 2083:  Called multilib_src_configure
 *             environment, line 2518:  Called econf
 *        phase-helpers.sh, line  665:  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.10-r3::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-apps/sandbox-2.10-r3::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/tmp/portage/sys-apps/sandbox-2.10-r3/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-apps/sandbox-2.10-r3/temp/environment'.
 * Working directory: '/var/tmp/portage/sys-apps/sandbox-2.10-r3/work/sandbox-2.10-abi_x86_64.amd64'
 * S: '/var/tmp/portage/sys-apps/sandbox-2.10-r3/work/sandbox-2.10'

 * GNU info directory index is up-to-date.

 * IMPORTANT: 12 news items need reading for repository 'gentoo'.
 * Use eselect news read to view new items.

 * After world updates, it is important to remove obsolete packages with
 * emerge --depclean. Refer to `man emerge` for more information.

Added code-tags to improve readability and to preserve formatting.Chiitoo
Back to top
View user's profile Send private message
Syl20
Guru
Guru


Joined: 04 Aug 2005
Posts: 564
Location: France

PostPosted: Tue Mar 14, 2017 8:10 am    Post subject: Reply with quote

Code:
* If configure failed with a 'cannot run C compiled programs' error, try this:
* FEATURES='-sandbox -usersandbox' emerge sandbox

The message says you what to do.
Back to top
View user's profile Send private message
fturco
l33t
l33t


Joined: 08 Dec 2010
Posts: 629
Location: Italy

PostPosted: Tue Mar 14, 2017 10:50 am    Post subject: Reply with quote

Quote:
Code:
* IMPORTANT: 12 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.

This is another portage message that should be checked.
Back to top
View user's profile Send private message
pcp1976
n00b
n00b


Joined: 30 May 2017
Posts: 3

PostPosted: Tue May 30, 2017 9:56 pm    Post subject: checking whether the C compiler works... no Reply with quote

Issuing
Code:
FEATURES='-sandbox -usersandbox' emerge sandbox
in a terminal results in the same (or similar) error:
Code:
checking whether the C compiler works... no
.
Back to top
View user's profile Send private message
Hu
Moderator
Moderator


Joined: 06 Mar 2007
Posts: 13865

PostPosted: Wed May 31, 2017 1:13 am    Post subject: Reply with quote

For both of the users who reported problems: if you still need help, please follow the instructions shown in the Portage output. Pastebin the relevant log files so that we can investigate why configure fails.
Back to top
View user's profile Send private message
pcp1976
n00b
n00b


Joined: 30 May 2017
Posts: 3

PostPosted: Wed May 31, 2017 8:25 am    Post subject: Reply with quote

Hi Hu, thank you for responding - however following the suggestion from the portage output does not solve the issue. As I wrote: portage asks the user to try
Code:
FEATURES='-sandbox -usersandbox' emerge sandbox
however the outcome is the same:
Code:
checking whether the C compiler works... no
.

Having looked elsewhere, I found
Code:
FEATURES="-sandbox" USE="multilib" emerge gcc portage
which I'm running before updating my @world. I'll come back to report if this helps. If it does the user manual needs an edit for x64 multilib installs.
Back to top
View user's profile Send private message
krinn
Watchman
Watchman


Joined: 02 May 2003
Posts: 7071

PostPosted: Wed May 31, 2017 9:35 am    Post subject: Reply with quote

pcp1976 open your own thread, the "omg i have the same error as him" generally endup with "sorry guys, i was thinking it was".
Back to top
View user's profile Send private message
pcp1976
n00b
n00b


Joined: 30 May 2017
Posts: 3

PostPosted: Wed May 31, 2017 1:56 pm    Post subject: Reply with quote

Same error, same situation. [for the sake of clarity: creating a fresh install, reach the point where updating @world, fail at emerging sandbox. Doing as portage output suggests results in a repeat of the error. I'm not saying because I have the same error the situation is the same - we have the same situation, and the same error]

Incidentally, the line I posted worked.
Back to top
View user's profile Send private message
Hu
Moderator
Moderator


Joined: 06 Mar 2007
Posts: 13865

PostPosted: Thu Jun 01, 2017 2:07 am    Post subject: Reply with quote

pcp1976 wrote:
however following the suggestion from the portage output does not solve the issue. As I wrote: portage asks the user to try
Code:
FEATURES='-sandbox -usersandbox' emerge sandbox
That is not what I meant. I was referring to the instructions Portage prints when something fails, which tell you what output to provide to us so that we can help you:
Code:
 * If you need support, post the output of `emerge --info '=sys-apps/sandbox-2.10-r3::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-apps/sandbox-2.10-r3::gentoo'`.
Back to top
View user's profile Send private message
krinn
Watchman
Watchman


Joined: 02 May 2003
Posts: 7071

PostPosted: Thu Jun 01, 2017 11:29 am    Post subject: Reply with quote

pcp1976 wrote:
Same error, same situation. [for the sake of clarity: creating a fresh install, reach the point where updating @world, fail at emerging sandbox. Doing as portage output suggests results in a repeat of the error. I'm not saying because I have the same error the situation is the same - we have the same situation, and the same error]

If you go like this, then everybody has the same error and situation as soon as anyone have an error?
I cannot emerge something -> same as him, i fail to emerge a thing

the sandbox message is for people unable to build sandbox, but getting 'cannot run C compiled programs' error, and he was having the error 'C compiler cannot create executables"

If anything happen while testing gcc, the primary error is just "checking whether the C compiler works... no" and it mean everybody will get this one when compiler is in trouble, it doesn't mean the causes are the same.
His message is typical to a gcc that work, but is unable to create executable, because someone ask something gcc cannot do, generally, bad cflags.

And even if really you were having 100% exact same situation and error, just open your own thread for clarity.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Installing Gentoo All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum