1 |
I wrote: |
2 |
|
3 |
> The problem is that in the libtool linking phase the arguments "/usr/bin |
4 |
> /usr/sbin /bin /sbin" are given along the libraries and library paths. I |
5 |
> have no idea why this happens, and how to solve this. Something must be |
6 |
> wrong on my system. But what? For libggi, emerging with USE=-aalib sort |
7 |
> of solved this. But I have no idea what to do about pygtksourceview. As |
8 |
> all gthe KDE stuff seems to depend on this, I cannot continue |
9 |
|
10 |
And the solution is <ta-daaah>: unset path |
11 |
|
12 |
I am using systemrescuecd, which sets a 'path' environment variable. |
13 |
This variable is being used in the libtool script, without being cleared |
14 |
first. |
15 |
|
16 |
Makes me feel a little stupid. I filed a bug report for a package that |
17 |
built without problems on my other system. I looked a bugs.gentoo.org, |
18 |
but did not search the web much for keywords like 'libtool' and |
19 |
'/usr/bin /usr/sbin /bin /sbin', which would have found a few mentions |
20 |
of this problem. And I wasted too much time debugging and trying to |
21 |
understand the libtool script. |
22 |
|
23 |
I filed a bug for autoconf: |
24 |
https://bugs.gentoo.org/show_bug.cgi?id=396213 |
25 |
|
26 |
Wonko |