On Fri, 2005-07-22 at 09:42 -0700, Zac Medico wrote: > > > [snip] > > +++ making > chrome > /var/tmp/portage/mozilla-firefox-1.0.5-r1/work/mozilla/extensions/cookie => > ../../dist/bin/chrome/classic.jar > > ../../config/make-jars.pl: Could not get > lockfile > /var/tmp/portage/mozilla-firefox-1.0.5-r1/work/mozilla/dist/bin/chrome/classic.lck. > > > Remove > /var/tmp/portage/mozilla-firefox-1.0.5-r1/work/mozilla/dist/bin/chrome/classic.lck > to clear up > > Did you restart the build from scratch or resume it with > FEATURES=keepwork or something. You can remove the lockfile and try > to restart it.
I restarted from scratch with "emerge -va mozilla-firefox" > >From my experience, mozilla and firefox builds seem to work pretty > well with MAKEOPTS="-j5" and 2 single cpu athlon XP boxes running > distcc (emerge on one). I'm not sure what the deal is here. Maybe if > you increase to MAKEOPTS="-j5" that will help? Then again, maybe > there's something wrong in your toolchain. Hmm... I did a fairly standard stage1 install. The only problem was that I had to add "-gpm" to the USE flags when emerging the system. A circular dependency made the build stop halfway through. Everything seem to be working just fine, except for my Audigy sound card (see my other post). Any way to check if the toolchain is broken? Best regards, jules -- gentoo-user@gentoo.org mailing list
