On Mon, Dec 26, 2011 at 07:23:27PM +0100, Alex Schuster wrote > Hi there! > > I'm currently upgrading my little sister's PC from an x86 Sempron to an > x86_64 AMDS A6 processor. So Gentoo is being installed from scratch. > > But some packages fail to build. I filed a bug [1] for > media-libs/libggi-2.2.2, but a similar problem is happening for > pygtksourceview now, and I do not find a simple workaround. > > 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
I notice that you have 'MAKEOPTS="-j4"'. You wouldn't believe how many problems you can solve by changing to 'MAKEOPTS="-j1"'. Yes, the build process may take a bit longer, but the final executable runs just as fast. Change to 'MAKEOPTS="-j1"' and see what happens. The concept of parallel jobs is nice in theory, and you can *USUALLY* get away with it. The problem is that if a job tries to use an intermediate file before it's fully created, or if the "destructor" (file deletion) does it's thing before the scratch file has been used, things get very fouled up. My attitude is that the first time you spend hours trying to trace down a non-replicatable bug, you will lose more time than you "save" by speeding up builds with 'MAKEOPTS="-j4"'. -- Walter Dnes <waltd...@waltdnes.org>
