1 |
On Tuesday, 23 July 2019 16:01:01 BST Raffaele Belardi wrote: |
2 |
|
3 |
> > Am 23.07.19 um 01:31 schrieb Jack: |
4 |
> >> On 2019.07.22 09:02, Jens Pelzetter wrote: |
5 |
> >>> Hello everyone, |
6 |
> >>> |
7 |
> >>> recently x11-libs/libXt was updated to version 1.2.0. On one of systems |
8 |
> >>> 1.2.0 does not compile. The error is rather strange: |
9 |
> >>> |
10 |
> >>> checking for i686-pc-linux-gnu-cpp... /usr/bin/i686-pc-linux-gnu-cpp |
11 |
> >>> checking if /usr/bin/i686-pc-linux-gnu-cpp requires -undef... * |
12 |
> >>> gcc-config: No gcc profile is active! |
13 |
> >>> /usr/bin/gcc-config: line 76: /etc/env.d/gcc/config-i686-pc-linux-gnu: |
14 |
> >>> No such file or directory |
15 |
> >>> gcc-config: error: could not run/locate 'i686-pc-linux-gnu-cpp' |
16 |
> >>> |
17 |
> >>> * gcc-config: No gcc profile is active! |
18 |
> >>> |
19 |
> >>> /usr/bin/gcc-config: line 76: /etc/env.d/gcc/config-i686-pc-linux-gnu: |
20 |
> >>> No such file or directory |
21 |
> >>> gcc-config: error: could not run/locate 'i686-pc-linux-gnu-cpp' |
22 |
> >>> |
23 |
> >>> * gcc-config: No gcc profile is active! |
24 |
> >>> |
25 |
> >>> /usr/bin/gcc-config: line 76: /etc/env.d/gcc/config-i686-pc-linux-gnu: |
26 |
> >>> No such file or directory |
27 |
> >>> gcc-config: error: could not run/locate 'i686-pc-linux-gnu-cpp' |
28 |
> >>> configure: error: /usr/bin/i686-pc-linux-gnu-cpp defines unix with or |
29 |
> >>> without -undef. I don't know what to do. |
30 |
> >>> |
31 |
> >>> The systems is a multilib systems (32 and 64 Bit). I suspect that it is |
32 |
> >>> not a bug in the libXt ebuild but a problem with my system, but I can't |
33 |
> >>> figure out what the problem is. Any help is appreciated. |
34 |
> >>> |
35 |
> >>> build.log, environment etc. are attached. |
36 |
> >>> |
37 |
> >>> Best regards |
38 |
> >> |
39 |
> >> Do you have a gcc profile selected? "gcc-config -l" should list the |
40 |
> >> available ones and indicate which is selected. |
41 |
> >> |
42 |
> >> Jack |
43 |
> |
44 |
> The gcc compiler for your profile is prefixed by x86_64-* but your configure |
45 |
> script is looking for i686-* and does not find it: "gcc-config: error: |
46 |
> could not run/locate 'i686-pc-linux-gnu-cpp'" |
47 |
> |
48 |
> That said, I'm no longer on multilib since years so I would not know what |
49 |
> the root cause of your problem is, sorry. |
50 |
> |
51 |
> Maybe 'eselect profile list' helps? |
52 |
> |
53 |
> raffaele |
54 |
|
55 |
On multilib: |
56 |
|
57 |
$ ls -la /etc/env.d/gcc/ |
58 |
total 16 |
59 |
drwxr-xr-x 2 root root 4096 Jun 11 12:23 . |
60 |
drwxr-xr-x 5 root root 4096 Jul 20 16:53 .. |
61 |
lrwxrwxrwx 1 root root 25 Jun 11 12:23 .NATIVE -> x86_64-pc-linux-gnu-8.3.0 |
62 |
-rw-r--r-- 1 root root 34 Jun 11 12:23 config-x86_64-pc-linux-gnu |
63 |
-rw-r--r-- 1 root root 358 Jun 11 12:23 x86_64-pc-linux-gnu-8.3.0 |
64 |
|
65 |
The question must be why is emerge looking for config-i686-pc-linux-gnu? |
66 |
|
67 |
Has Jens messed about with CHOST= in /etc/portage/make.conf? |
68 |
|
69 |
Will the package build without complaining if emerged so: |
70 |
|
71 |
CHOST="x86_64-pc-linux-gnu" emerge -1aDv x11-libs/libXt |
72 |
|
73 |
-- |
74 |
Regards, |
75 |
|
76 |
Mick |