On Mon, 03 Aug 2009 17:16:18 +0300, Nikos Chantziaras wrote:
> So my advice for others is to not take Walter's advice and use -j1
> because "it doesn't slow down the emerge that much". It can slow it
> down. Up to four times slower.
Personaly, I've never had an ebuild fail due to setting MAKEO
Stroller wrote:
>
> On 3 Aug 2009, at 15:56, Dale wrote:
>> But if he has a single CPU system, it won't matter that much. I have
>> always heard that it should be set to number of CPU's plus 1. Mine is
>> set to 2 since I have a single CPU rig.
>
> It should be set to at least the number of *core
On 3 Aug 2009, at 15:56, Dale wrote:
But if he has a single CPU system, it won't matter that much. I have
always heard that it should be set to number of CPU's plus 1. Mine is
set to 2 since I have a single CPU rig.
It should be set to at least the number of *cores*, not CPUs.
Back in ye ol
Nikos Chantziaras wrote:
> On 08/03/2009 03:11 PM, Walter Dnes wrote:
>> On Sun, Aug 02, 2009 at 09:10:49PM +0300, Nikos Chantziaras wrote
>>
>>> Note that by doing so you will be using -j1 for every future version
>>> of duma. That means, if the problem gets fixed, you'll still be
>>> using -j1.
Nikos Chantziaras wrote:
> On 08/03/2009 03:11 PM, Walter Dnes wrote:
>>
>>Actually, I put -j1 into my make.conf after being bitten by -j2 a few
>> times. It doesn't slow down the emerge that much, and doesn't slow down
>> the compiled program at all. And the big thing is that it has probably
On 08/03/2009 03:11 PM, Walter Dnes wrote:
On Sun, Aug 02, 2009 at 09:10:49PM +0300, Nikos Chantziaras wrote
Note that by doing so you will be using -j1 for every future version
of duma. That means, if the problem gets fixed, you'll still be
using -j1.
Actually, I put -j1 into my make.con
On Sun, Aug 02, 2009 at 09:10:49PM +0300, Nikos Chantziaras wrote
> Note that by doing so you will be using -j1 for every future version
> of duma. That means, if the problem gets fixed, you'll still be
> using -j1.
Actually, I put -j1 into my make.conf after being bitten by -j2 a few
times.
On Sun, 02 Aug 2009 21:10:49 +0300, Nikos Chantziaras wrote:
> >> echo 'MAKEOPTS="-j1"'>/etc/portage/env/dev-util/duma
> >
> > Exactly what I was looking for!
>
> Note that by doing so you will be using -j1 for every future version of
> duma. That means, if the problem gets fixed, you'll st
Nikos Chantziaras wrote:
> On 08/02/2009 08:37 PM, David Relson wrote:
>> On Sun, 2 Aug 2009 17:23:40 +0100
>> Neil Bothwick wrote:
>>
>>> On Sun, 2 Aug 2009 09:20:37 -0400, David Relson wrote:
>>>
I've had trouble building dev-util/duma and discovered this morning
that -j2 was the culpri
On 08/02/2009 08:37 PM, David Relson wrote:
On Sun, 2 Aug 2009 17:23:40 +0100
Neil Bothwick wrote:
On Sun, 2 Aug 2009 09:20:37 -0400, David Relson wrote:
I've had trouble building dev-util/duma and discovered this morning
that -j2 was the culprit. duma's build compiles and runs
createconf.c
On 08/02/2009 04:20 PM, David Relson wrote:
I've had trouble building dev-util/duma and discovered this morning that
-j2 was the culprit. duma's build compiles and runs createconf.c in
order to create duma_config.h which is needed by dumapp.cpp. With -j2,
the cpp compilation is starting before
11 matches
Mail list logo
