1 |
Hallo all, |
2 |
|
3 |
Am 23.07.19 um 17:14 schrieb Mick: |
4 |
> On Tuesday, 23 July 2019 16:01:01 BST Raffaele Belardi wrote: |
5 |
> |
6 |
>>> Am 23.07.19 um 01:31 schrieb Jack: |
7 |
> |
8 |
> On multilib: |
9 |
> |
10 |
> $ ls -la /etc/env.d/gcc/ |
11 |
> total 16 |
12 |
> drwxr-xr-x 2 root root 4096 Jun 11 12:23 . |
13 |
> drwxr-xr-x 5 root root 4096 Jul 20 16:53 .. |
14 |
> lrwxrwxrwx 1 root root 25 Jun 11 12:23 .NATIVE -> x86_64-pc-linux-gnu-8.3.0 |
15 |
> -rw-r--r-- 1 root root 34 Jun 11 12:23 config-x86_64-pc-linux-gnu |
16 |
> -rw-r--r-- 1 root root 358 Jun 11 12:23 x86_64-pc-linux-gnu-8.3.0 |
17 |
> |
18 |
> The question must be why is emerge looking for config-i686-pc-linux-gnu? |
19 |
> |
20 |
> Has Jens messed about with CHOST= in /etc/portage/make.conf? |
21 |
> |
22 |
> Will the package build without complaining if emerged so: |
23 |
> |
24 |
> CHOST="x86_64-pc-linux-gnu" emerge -1aDv x11-libs/libXt |
25 |
> |
26 |
|
27 |
with CHOST="x86_64-pc-linux-gnu" emerge -1aDv x11-libs/libXt the ebuild |
28 |
produces the same error. CHOST in my make.conf is x86_64-pc-linux-gnu. |
29 |
|
30 |
env.d/gcc also looks fine: |
31 |
|
32 |
# ls -la /etc/env.d/gcc/ |
33 |
total 16 |
34 |
drwxr-xr-x 2 root root 4096 Jul 21 19:45 . |
35 |
drwxr-xr-x 7 root root 4096 Jul 22 19:21 .. |
36 |
lrwxrwxrwx 1 root root 25 Jul 21 19:45 .NATIVE -> |
37 |
x86_64-pc-linux-gnu-8.3.0 |
38 |
-rw-r--r-- 1 root root 34 Jul 21 19:45 config-x86_64-pc-linux-gnu |
39 |
-rw-r--r-- 1 root root 358 Jul 19 21:18 x86_64-pc-linux-gnu-8.3.0 |
40 |
|
41 |
Best regards |
42 |
|
43 |
Jens |