1 |
On Tue, Jul 23, 2019 at 12:51 PM Jens Pelzetter |
2 |
<jens.pelzetter@××××××××××.com> wrote: |
3 |
> |
4 |
> Hallo all, |
5 |
> |
6 |
> Am 23.07.19 um 17:14 schrieb Mick: |
7 |
> > On Tuesday, 23 July 2019 16:01:01 BST Raffaele Belardi wrote: |
8 |
> > |
9 |
> >>> Am 23.07.19 um 01:31 schrieb Jack: |
10 |
> > |
11 |
> > On multilib: |
12 |
> > |
13 |
> > $ ls -la /etc/env.d/gcc/ |
14 |
> > total 16 |
15 |
> > drwxr-xr-x 2 root root 4096 Jun 11 12:23 . |
16 |
> > drwxr-xr-x 5 root root 4096 Jul 20 16:53 .. |
17 |
> > lrwxrwxrwx 1 root root 25 Jun 11 12:23 .NATIVE -> x86_64-pc-linux-gnu-8.3.0 |
18 |
> > -rw-r--r-- 1 root root 34 Jun 11 12:23 config-x86_64-pc-linux-gnu |
19 |
> > -rw-r--r-- 1 root root 358 Jun 11 12:23 x86_64-pc-linux-gnu-8.3.0 |
20 |
> > |
21 |
> > The question must be why is emerge looking for config-i686-pc-linux-gnu? |
22 |
> > |
23 |
> > Has Jens messed about with CHOST= in /etc/portage/make.conf? |
24 |
> > |
25 |
> > Will the package build without complaining if emerged so: |
26 |
> > |
27 |
> > CHOST="x86_64-pc-linux-gnu" emerge -1aDv x11-libs/libXt |
28 |
> > |
29 |
> |
30 |
> with CHOST="x86_64-pc-linux-gnu" emerge -1aDv x11-libs/libXt the ebuild |
31 |
> produces the same error. CHOST in my make.conf is x86_64-pc-linux-gnu. |
32 |
> |
33 |
> env.d/gcc also looks fine: |
34 |
> |
35 |
> # ls -la /etc/env.d/gcc/ |
36 |
> total 16 |
37 |
> drwxr-xr-x 2 root root 4096 Jul 21 19:45 . |
38 |
> drwxr-xr-x 7 root root 4096 Jul 22 19:21 .. |
39 |
> lrwxrwxrwx 1 root root 25 Jul 21 19:45 .NATIVE -> |
40 |
> x86_64-pc-linux-gnu-8.3.0 |
41 |
> -rw-r--r-- 1 root root 34 Jul 21 19:45 config-x86_64-pc-linux-gnu |
42 |
> -rw-r--r-- 1 root root 358 Jul 19 21:18 x86_64-pc-linux-gnu-8.3.0 |
43 |
> |
44 |
> Best regards |
45 |
> |
46 |
> Jens |
47 |
> |
48 |
|
49 |
You probably installed a (cross) toolchain with host=i686-pc-linux-gnu |
50 |
at some point, and now you have stale symlinks leftover in /usr. Try |
51 |
removing them. |