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