From: Jules Colding <colding@omesc.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Can't emerge mozilla-firefox
Date: Fri, 22 Jul 2005 18:56:18 +0200 [thread overview]
Message-ID: <1122051378.20738.31.camel@omc-2.omesc.com> (raw)
In-Reply-To: <42E121DF.3070006@gmail.com>
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
next prev parent reply other threads:[~2005-07-22 17:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-22 1:02 [gentoo-user] Can't emerge mozilla-firefox Jules Colding
2005-07-22 2:12 ` Zac Medico
2005-07-22 12:25 ` Jules Colding
2005-07-22 16:42 ` Zac Medico
2005-07-22 16:56 ` Jules Colding [this message]
2005-07-22 17:54 ` Zac Medico
2005-07-22 19:16 ` Jules Colding
2005-07-23 6:26 ` Walter Dnes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1122051378.20738.31.camel@omc-2.omesc.com \
--to=colding@omesc.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox