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