From: "Walter Dnes" <waltdnes@waltdnes.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [SOLVED] Re: [gentoo-user] Cannot emerge x11-libs/qt-webkit-4.6.2-r1
Date: Thu, 13 May 2010 00:06:17 -0400 [thread overview]
Message-ID: <20100513040617.GB3159@waltdnes.org> (raw)
In-Reply-To: <20100510003321.2ecb4f7e@digimed.co.uk>
On Mon, May 10, 2010 at 12:33:21AM +0100, Neil Bothwick wrote
> On Sun, 9 May 2010 18:28:31 -0400, Walter Dnes wrote:
>
> > Ditto for setting MAKEOPTS to -j1. Every once in a while, somebody
> > runs into a problem that is solved by it. I finally decided to let
> > the builds take a little bit longer, in exchange for saving me problems
> > with "unreproducable errors". This setting does not affect the final
> > binary; just how long it takes to build.
>
> I can't recall the last time I needed to use MAKEOPTS=-j1, but if you
> do set it you can get back the time you lose by using the jobs option
> with emerge. That way you get parallel compilation, but of separate
> packages.
Something just occured to me. At the risk of sounding paranoid, is
there an absolute guarantee that...
- if package A has dependancies Y and Z...
- the compile for A won't start before Y and Z are built and installed
This could be especially ugly for my new system installs. I usually
install text-console mode only, followed by "emerge gimp", which pulls
in X and a whole bunch of other stuff as dependancies. Portage handles
this process very well right now.
--
Walter Dnes <waltdnes@waltdnes.org>
next prev parent reply other threads:[~2010-05-13 4:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-07 21:36 [gentoo-user] Cannot emerge x11-libs/qt-webkit-4.6.2-r1 Jim Cunning
2010-05-08 0:04 ` William Kenworthy
2010-05-08 6:16 ` [SOLVED] " Jim Cunning
2010-05-08 7:18 ` Neil Bothwick
2010-05-08 11:58 ` Dale
2010-05-09 22:28 ` Walter Dnes
2010-05-09 23:33 ` Neil Bothwick
2010-05-13 4:06 ` Walter Dnes [this message]
2010-05-13 7:44 ` Alan McKinnon
2010-05-13 8:17 ` Neil Bothwick
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=20100513040617.GB3159@waltdnes.org \
--to=waltdnes@waltdnes.org \
--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