Pandu Poluan writes:
> On Dec 27, 2011 6:01 AM, "Alex Schuster" <wo...@wonkology.org
> <mailto:wo...@wonkology.org>> wrote:
>>
>> 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
The problem seems to happen deep in the libtool script in the build
directory, where a variable deplibs is set to "/sbin /bin /usr/sbin
/usr/bin/usr/lib64/libaa.so ...", but I do not yet know why and where in
those 7700 lines of code that happens, a 'libtool=' occurs 121 times
there. Gotta go to bed for now
> Have you tried revdep-rebuild? python-updater?
No. When I do, all is consistent, and python-updater does not find much,
mostly things that are not even installed yet.
Now I try another of those things that are supposed to fix all kind of
weird problems, emerge -e @world. I changed the CFLAGS a little, and I
had forgotten to add sse2 to the USE flags, so I just build everything
again this night. But I don't expect this to help with my problem.
Wonko
