| 1 |
On 01/27/2011 04:16 PM, Neil Bothwick wrote: |
| 2 |
> On Thu, 27 Jan 2011 15:33:21 +0200, Nikos Chantziaras wrote: |
| 3 |
> |
| 4 |
>>> I am using the -j option for the first time now. I'm updating KDE. It |
| 5 |
>>> seems to work fine. It doesn't scroll all the stuff like with a |
| 6 |
>>> regular emerges but this new rig is so fast, I can't read it anyway. |
| 7 |
>>> I did have a package to fail and it spit out the error for me to |
| 8 |
>>> read. |
| 9 |
>> |
| 10 |
>> You don't need that if you have MAKEOPTS set in your make.conf, which |
| 11 |
>> is preferred. The -j option of emerge emerges multiple packages, while |
| 12 |
>> with MAKEOPTS set to "-j4" or whatever does a parallel build in the |
| 13 |
>> same package (meaning compiling multiple source files at the same time). |
| 14 |
> |
| 15 |
> And how many CPU cores are used during the configure and install stages? |
| 16 |
> |
| 17 |
> Using --jobs does a better job of making use of your CPU because one |
| 18 |
> package can use it fully for compiling while another is configuring. |
| 19 |
|
| 20 |
And what about the last package? The time you gained for faster |
| 21 |
configure and install (which don't take too much time anyway) is wasted |
| 22 |
again on the last package. |
Archives