I execute: # FEATURES=-sandbox emerge -1 sandbox Output: ... checking whether the C compiler works... configure: error: in `/var/tmp/portage/sys-apps/sandbox-2.2/work/build-x86': configure: error: cannot run C compiled programs. If you meant to cross compile, use `--host'. See `config.log' for more details. ... If configure failed with a 'cannot run C compiled programs' error, try this: FEATURES=-sandbox emerge sandbox
Created attachment 229581 [details] /var/tmp/portage/sys-apps/sandbox-2.2/temp/build.log
Created attachment 229583 [details] /var/tmp/portage/sys-apps/sandbox-2.2/work/build-x86/config.log
Created attachment 229585 [details] /var/tmp/portage/sys-apps/sandbox-2.2/temp/environment
Created attachment 229587 [details] emerge --info =sys-apps/sandbox-2.2
Created attachment 229589 [details] emerge -pqv =sys-apps/sandbox-2.2
# cat /etc/make.conf | grep -i flags CFLAGS="-O2 -pipe -march=core2 -mtune=core2" CXXFLAGS="-O2 -pipe -march=core2 -mtune=core2" # gcc-config -l [1] x86_64-pc-linux-gnu-4.5.0 *
Looks like it's picking the wrong architecture target with USE=multilib.
> Looks like it's picking the wrong architecture target with USE=multilib. Yes, the system was built without 'multilib', and now I want to add multilib. I don't understood, what i need to do next from your answer (how to change "architecture target").
I am trying to follow the article http://www.gentoo.org/doc/en/change-chost.xml but the command emerge -av1 binutils gcc glibc have the sandbox as dependency, and it fails to build
http://www.gentoo.org/doc/en/gentoo-amd64-faq.xml#multilib "Warning: Currently you cannot switch from a no-multilib to a multilib-enabled profile, so think over your decision twice before you use the no-multilib profile."
not a bug in sandbox. bugzilla isnt a support forum for people switching between non-multilib/multilib. seek assistance on the forums or mailing lists.
> not a bug in sandbox. every other package out of 793 packages was successfully recompiled with multilib flag. And only sandbox doesn't.
*** This bug has been marked as a duplicate of bug 272871 ***