| 1 |
Walter Dnes writes: |
| 2 |
|
| 3 |
> On Mon, Dec 26, 2011 at 07:23:27PM +0100, Alex Schuster wrote |
| 4 |
|
| 5 |
>> The problem is that in the libtool linking phase the arguments "/usr/bin |
| 6 |
>> /usr/sbin /bin /sbin" are given along the libraries and library paths. I |
| 7 |
>> have no idea why this happens, and how to solve this. Something must be |
| 8 |
>> wrong on my system. But what? For libggi, emerging with USE=-aalib sort |
| 9 |
>> of solved this. But I have no idea what to do about pygtksourceview. As |
| 10 |
>> all gthe KDE stuff seems to depend on this, I cannot continue |
| 11 |
> |
| 12 |
> I notice that you have 'MAKEOPTS="-j4"'. You wouldn't believe how |
| 13 |
> many problems you can solve by changing to 'MAKEOPTS="-j1"'. Yes, the |
| 14 |
> build process may take a bit longer, but the final executable runs just |
| 15 |
> as fast. Change to 'MAKEOPTS="-j1"' and see what happens. |
| 16 |
|
| 17 |
Good idea, I also had some weird side effects from that in the past. |
| 18 |
Although not that reproducible. I see this with libggi, libiodbc, |
| 19 |
gtksourceview and gettext, at least. |
| 20 |
|
| 21 |
I still get the same error. And the emerge -e also did not clean things up. |
| 22 |
|
| 23 |
My next idea would be to compare the build logs on that and on my own |
| 24 |
machine, maybe I spot a difference. Or to analyze the libtool script |
| 25 |
deeper. Before I give up and install Ubuntu... |
| 26 |
|
| 27 |
Wonko |
Archives