| 1 |
On Sat, Jan 23, 2016 at 09:52:29PM +0100, karl@××××××××.se wrote: |
| 2 |
> Karl Hammar: |
| 3 |
> > Alec Ten Harmsel: |
| 4 |
> > > On Tue, Jan 19, 2016 at 10:05:49PM +0100, karl@××××××××.se wrote: |
| 5 |
> > > > Alec: Ten Harmsel: |
| 6 |
> > > > > On Tue, Jan 19, 2016 at 08:01:19PM +0100, karl@××××××××.se wrote: |
| 7 |
> > > > > > Makefile:1318: recipe for target 'xinput.c' failed |
| 8 |
> > > > > > when emerging x11-libs/libxcb-1.11.1, logs etc.: |
| 9 |
> ... |
| 10 |
> > > The problem is a python script that runs in the build process has a |
| 11 |
> > > KeyError. I did notice that for you, that python script is running on |
| 12 |
> > > files in `/usr/local/share/xcb', while it runs on files in |
| 13 |
> > > `/usr/share/xcb' on mine. These are a part of the `x11-proto/xcb-proto' |
| 14 |
> > > package. Do you have a version of xcb-proto installed in /usr/local? It |
| 15 |
> > > is possible that the libxcb configure script is picking an old version |
| 16 |
> > > of xcb-proto that is installed in `/usr/local' over the correct version |
| 17 |
> > > installed in `/usr'. |
| 18 |
> > |
| 19 |
> > Yes, that's probably it, thanks for the look. |
| 20 |
> > |
| 21 |
> > > I would recommend removing `/usr/local/share/xcb' and trying to install |
| 22 |
> > > libxcb again. |
| 23 |
> > |
| 24 |
> > I mv'ed /usr/local/share but it didn't help. |
| 25 |
> |
| 26 |
> emerge -C'd x*/* thing, and reemerged, didn't help. |
| 27 |
> |
| 28 |
> Restarting the installation of gentoo from the very beginning helped. |
| 29 |
> Wasn't aware of that /usr/local could affect installing gentoo |
| 30 |
> packages, havn't had that experience with binary distributions. |
| 31 |
> Well, case closed. |
| 32 |
|
| 33 |
Ideally, it shouldn't. However, sometimes configure scripts and/or |
| 34 |
portage's environment somehow gets polluted by stuff in `/usr/local'. |
| 35 |
|
| 36 |
Alec |
Archives