1 |
Well, I decided to forge ahead while I still have the steam. I'm upgrading |
2 |
GCC from 3.4.4 to 4.1.1-r1. |
3 |
|
4 |
I followed the instructions thus: |
5 |
|
6 |
# emerge -uav gcc |
7 |
# gcc-config i686-pc-linux-gnu-4.1.1 |
8 |
# source /etc/profile |
9 |
# fix_libtool_files.sh 3.4.4 |
10 |
# emerge --oneshot -av libtool |
11 |
|
12 |
I then decided, before emerging -e system and risking confusion of GCC |
13 |
versions as before, to remove 3.4.4 and emerge libtool again to check that |
14 |
the compiler works ok. That went without a problem, so I do have a working |
15 |
4.1.1 compiler. |
16 |
|
17 |
Now, during emerge -e system, emerge of sandbox (the ninth package of 114) |
18 |
falls over with the dreaded "C compiler cannot create executables". I |
19 |
followed its own advice and ran: |
20 |
FEATURES="-sandbox" emerge sandbox |
21 |
which failed at the same point. Here are some extracts |
22 |
from /var/tmp/portage/sandbox-1.2.18.1/work/build-x86-x86_64-pc-linux-gnu/config.log: |
23 |
|
24 |
Invocation command line was |
25 |
$ ../sandbox-1.2.18.1//configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr |
26 |
/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib32 --enable-multili |
27 |
b --build=i686-pc-linux-gnu |
28 |
|
29 |
Note the "--host=i686-pc-linux-gnu". I think that's wrong: it should |
30 |
say "--host=x86_64-pc-linux-gnu", no? Continuing the log extract: |
31 |
|
32 |
configure:1533: checking for a BSD-compatible install |
33 |
configure:1588: result: /bin/install -c |
34 |
configure:1599: checking whether build environment is sane |
35 |
configure:1642: result: yes |
36 |
configure:1707: checking for gawk |
37 |
configure:1723: found /bin/gawk |
38 |
configure:1733: result: gawk |
39 |
configure:1743: checking whether make sets $(MAKE) |
40 |
configure:1763: result: yes |
41 |
configure:1942: checking for i686-pc-linux-gnu-gcc |
42 |
configure:1958: found /usr/bin/i686-pc-linux-gnu-gcc |
43 |
configure:1968: result: i686-pc-linux-gnu-gcc |
44 |
configure:2250: checking for C compiler version |
45 |
configure:2253: i686-pc-linux-gnu-gcc --version </dev/null >&5 |
46 |
gcc-config error: i686-pc-linux-gnu-gcc wrapper: Could not determine which |
47 |
compiler to use. Invalid CTARGET or CTARGET has no selected profile. |
48 |
|
49 |
Indeed, issuing commands manually I get this: |
50 |
|
51 |
$ i686-pc-linux-gnu-gcc --version |
52 |
gcc-config error: i686-pc-linux-gnu-gcc wrapper: Could not determine which |
53 |
compiler to use. Invalid CTARGET or CTARGET has no selected profile. |
54 |
$ which i686-pc-linux-gnu-gcc |
55 |
/usr/bin/i686-pc-linux-gnu-gcc |
56 |
$ eselect compiler list |
57 |
Available compilers for CTARGET i686-pc-linux-gnu |
58 |
[1] x86_64-pc-linux-gnu-4.1.1/x86-vanilla |
59 |
Available compilers for CTARGET x86_64-pc-linux-gnu |
60 |
[2] x86_64-pc-linux-gnu-4.1.1/amd64-vanilla |
61 |
|
62 |
Activated profiles: |
63 |
[null] |
64 |
$ x86_64-pc-linux-gnu-gcc --version |
65 |
x86_64-pc-linux-gnu-gcc (GCC) 4.1.1 (Gentoo 4.1.1-r1) |
66 |
[...copyright notice...] |
67 |
|
68 |
[End of log extracts] |
69 |
|
70 |
Other packages are compiling as I write, having got to package 38 of 105, so |
71 |
the environment is broadly correct. |
72 |
|
73 |
Anyone any ideas? |
74 |
|
75 |
-- |
76 |
Rgds |
77 |
Peter |
78 |
-- |
79 |
gentoo-amd64@g.o mailing list |