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 21:16:01 +0200 [thread overview]
Message-ID: <1122059761.17840.2.camel@omc-2.omesc.com> (raw)
In-Reply-To: <42E132CB.6020007@gmail.com>
On Fri, 2005-07-22 at 10:54 -0700, Zac Medico wrote:
> Since you rebuilt from scratch, assuming that most other people can
> build successfully with equivalent settings, it seems like something
> in the toolchain (see output of "emerge --info") is actually is
> broken. Maybe it's just "make" itself (hence MAKEOPTS). Go ahead and
> remerge make and see what happens.
Nope, not make at least. Re-emerged make but still a problem with some
lock files when emerging firefox with MAKEOPTS is >1. Disabling MAKEOPTS
for now...
Thanks,
jules
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-07-22 19:20 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
2005-07-22 17:54 ` Zac Medico
2005-07-22 19:16 ` Jules Colding [this message]
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=1122059761.17840.2.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