Gentoo Archives: gentoo-user

From: Dale <rdalek1967@×××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] emerge -quad --newuse @world
Date: Mon, 29 Jan 2018 18:53:40
Message-Id: 57538edb-3248-4163-9b6e-c6f6bdea3600@gmail.com
In Reply to: [gentoo-user] emerge -quad --newuse @world by gg
1 gg wrote:
2 > Hallo ,
3 >
4 > please help me. I try to install a new Gentoo with no-multilib (AMD64) ,
5 >
6 > but compiling sandbox fails :
7 >
8 >
9 > ebuild R ] sys-apps/sandbox-2.12
10 >
11 > Would you like to merge these packages? [Yes/No] y
12 >>>> Verifying ebuild manifests
13 >>>> Emerging (1 of 1) sys-apps/sandbox-2.12::gentoo
14 >>>> Failed to emerge sys-apps/sandbox-2.12, Log file:
15 >>>> '/var/tmp/portage/sys-apps/sandbox-2.12/temp/build.log'
16 > * Package: sys-apps/sandbox-2.12
17 > * Repository: gentoo
18 > * Maintainer: sandbox@g.o
19 > * USE: abi_x86_32 abi_x86_64 amd64 elibc_glibc kernel_linux
20 > userland_GNU
21 > * FEATURES: preserve-libs sandbox userpriv usersandbox
22 > * abi_x86_32.x86: running multilib-minimal_abi_src_configure
23 > checking for a BSD-compatible install...
24 > /usr/lib/portage/python3.5/ebuild-helpers/xattr/install -c
25 > checking whether build environment is sane... yes
26 > checking for a thread-safe mkdir -p... /bin/mkdir -p
27 > checking for gawk... gawk
28 > checking whether make sets $(MAKE)... yes
29 > checking whether make supports nested variables... yes
30 > checking whether make supports nested variables... (cached) yes
31 > checking environment state... ok
32 > checking for i686-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc -m32
33 > checking whether the C compiler works... no
34 > configure: error: in
35 > `/var/tmp/portage/sys-apps/sandbox-2.12/work/sandbox-2.12-abi_x86_32.x86':
36 > configure: error: C compiler cannot create executables
37 > See `config.log' for more details
38 >
39 > !!! Please attach the following file when seeking support:
40 > !!!
41 >
42
43
44 I thought this looked familiar.  I did a google search and found a old
45 thread of mine.  I did a emerge -e @world to fix it.  You may can do a
46 emerge -e @system and it fix it, since it should fix gcc and everything
47 it depends on. 
48
49 Before doing that tho, I would check gcc-config -l and see if it is
50 set.  It should have a "*" beside one version in the list.  I seem to
51 recall once ages ago setting it, even tho it shows it is set, again and
52 it helping.  Should look something like this:
53
54 root@fireball / # gcc-config -l
55  [1] x86_64-pc-linux-gnu-6.4.0 *
56 root@fireball / # gcc-config 1
57  * Switching native-compiler to x86_64-pc-linux-gnu-6.4.0
58 ...                                                                                                                         
59 [ ok ]
60 root@fireball / # gcc-config -l
61  [1] x86_64-pc-linux-gnu-6.4.0 *
62 root@fireball / #
63
64 That is grasping at straws but if it works, it would save a lot of
65 compile time.  It's faster too.
66
67 Hope that helps and if not, maybe someone else has a good idea. 
68
69 Dale
70
71 :-)  :-)