Jules Colding wrote:
On Thu, 2005-07-21 at 19:12 -0700, Zac Medico wrote:
Hi Jules,
Jules Colding wrote:
[snip]
../../config/make-jars.pl: Could not get lockfile
/var/tmp/portage/mozilla-firefox-1.0.5-r1/work/mozilla/dist/bin/chrome/toolkit.lck.
[snip]
MAKEOPTS="-j3"
Try it with MAKEOPTS="-j2".
OK, did that. Now the error is another one (see below). The good news is
that you did get me to look in the right direction. MAKEOPTS="-j1" (or
no MAKEOPTS at all) fixed the problem.
The firefox build system must be somewhat flawed since this is needed.
This could be a timing problem as my box might be doing the build faster
than the usual dual CPU test box. Who knows...? Maybe MAKEOPTS should be
explicitly set in the ebuild?
Anyway, thanks a lot for your help :-)
[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.
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.
Zac
--
gentoo-user@gentoo.org mailing list
