From: Nikos Chantziaras <realnc@arcor.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Simultaneously emerging multiple packages with same dependencies
Date: Thu, 27 Jan 2011 16:30:30 +0200 [thread overview]
Message-ID: <ihrvht$cl1$1@dough.gmane.org> (raw)
In-Reply-To: <20110127141625.09298a30@zaphod.digimed.co.uk>
On 01/27/2011 04:16 PM, Neil Bothwick wrote:
> On Thu, 27 Jan 2011 15:33:21 +0200, Nikos Chantziaras wrote:
>
>>> I am using the -j option for the first time now. I'm updating KDE. It
>>> seems to work fine. It doesn't scroll all the stuff like with a
>>> regular emerges but this new rig is so fast, I can't read it anyway.
>>> I did have a package to fail and it spit out the error for me to
>>> read.
>>
>> You don't need that if you have MAKEOPTS set in your make.conf, which
>> is preferred. The -j option of emerge emerges multiple packages, while
>> with MAKEOPTS set to "-j4" or whatever does a parallel build in the
>> same package (meaning compiling multiple source files at the same time).
>
> And how many CPU cores are used during the configure and install stages?
>
> Using --jobs does a better job of making use of your CPU because one
> package can use it fully for compiling while another is configuring.
And what about the last package? The time you gained for faster
configure and install (which don't take too much time anyway) is wasted
again on the last package.
next prev parent reply other threads:[~2011-01-27 14:32 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-26 12:12 [gentoo-user] Simultaneously emerging multiple packages with same dependencies PK
2011-01-26 13:07 ` Petri Rosenström
2011-01-26 13:49 ` Neil Bothwick
2011-01-26 18:28 ` PK
2011-01-26 19:43 ` Jacob Todd
2011-01-27 5:12 ` [gentoo-user] " Nikos Chantziaras
2011-01-27 10:01 ` Neil Bothwick
2011-01-27 13:11 ` Dale
2011-01-27 13:33 ` Nikos Chantziaras
2011-01-27 14:05 ` YoYo Siska
2011-01-27 14:12 ` J. Roeleveld
2011-01-27 18:13 ` YoYo Siska
2011-01-27 19:41 ` Dale
2011-01-27 20:15 ` Nikos Chantziaras
2011-01-27 20:25 ` Paul Hartman
2011-01-27 21:46 ` J. Roeleveld
2011-01-27 22:05 ` Paul Hartman
2011-01-27 22:18 ` J. Roeleveld
2011-01-27 22:59 ` Mick
2011-01-28 7:16 ` J. Roeleveld
2011-01-27 21:11 ` Bill Longman
2011-01-27 22:53 ` Dale
2011-01-28 7:16 ` J. Roeleveld
2011-01-28 14:53 ` Dale
2011-01-27 14:16 ` Neil Bothwick
2011-01-27 14:30 ` Nikos Chantziaras [this message]
2011-01-27 14:53 ` Neil Bothwick
2011-01-27 15:09 ` Nikos Chantziaras
2011-01-27 15:15 ` Alan McKinnon
2011-01-27 15:43 ` Dale
2011-01-27 15:36 ` Neil Bothwick
2011-01-27 18:56 ` Allan Gottlieb
2011-01-27 19:18 ` J. Roeleveld
2011-01-27 21:06 ` YoYo Siska
2011-01-27 22:02 ` J. Roeleveld
2011-01-27 22:14 ` J. Roeleveld
2011-02-04 22:06 ` Enrico Weigelt
2011-01-27 15:14 ` Paul Hartman
2011-02-04 21:14 ` Enrico Weigelt
2011-01-27 15:33 ` PK
[not found] <gfdih-76I-1@gated-at.bofh.it>
[not found] ` <gfsr0-7M6-1@gated-at.bofh.it>
[not found] ` <gfwXE-72T-3@gated-at.bofh.it>
2011-01-27 16:04 ` David W Noon
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='ihrvht$cl1$1@dough.gmane.org' \
--to=realnc@arcor.de \
--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