Re: [gentoo-user] Re: --jobs

[Dale <rdalek1967@gmail.com>]

Harry Putnam wrote:
> Alan McKinnon<alan.mckinnon@gmail.com>  writes:
>
>> On Wed, 07 Dec 2011 16:55:38 -0600
>> Harry Putnam<reader@newsguy.com>  wrote:
>>
>>> Under the newest portage with x86~, if I run `emerge -vuD world'
>>> should I see something besides:
>>>
>>>>>> Jobs 0 of 71 complete, 1 running [...]
>>> Shouldn't there be more jobs running?
>>>
>>> (This is on gentoo installed as guest on win7 using Vbox)
>> What is the first job?
>>
>> Assuming that the system is set up to run parallel jobs, you have 71
>> updates. That's quite a lot. Maybe the first one is some really basic
>> package in @system upon which the other 70 depend (directly or
>> indirectly). Portage must complete the first fully in that case, then
>> proceed.
>>
>> Or, that first job is portage itself. It makes sense that portage
>> updates should be done in isolation.
> Now 38 are installed and it has never shown more than 1 running.
> Appears to be doing them all one by one.
>
> I'm not sure what you mean about system being setup for parallel jobs.
>
> Isn't the new default emerge to run that way?  Isn't that why we now
> have this line about jobs and load that completely removes the old -v
> ouput?
>
> This is a brand new install, and I've changed very little.  I've done
> nothing consciously to effect how many jobs are to be run.
>
> If its only going to do the jobs one by one, then why cover the -v
> output?
>
> I'd sooner disable this new behavior but it appears there is no across
> the board way to do that.  Maybe a function like:
>
>    emg () { emerge --quite-build=n $@; }
>
> Would have that effect.  I can't see where it would be losing anything
> since emerge is doing 1 job at a time anyway.  By the way, are these
> heavy or unusual loads:
>
>     1.10 1.17 1.14
>
> Its an i7 processor but gentoo is running as vbox guest.
>
>
>

If you are emerging packages one at a time, look at my sig.  I'm 
thinking you are expecting to see the configure, gcc and install info 
like it used to be by default.  The new default doesn't show that.  If 
you want the old way, see my sig for the option to put in make.conf.

If I am wrong on what you are expecting, ignore me.  Lots of people do 
anyway.  lol

Dale

:-)  :-)

-- 
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!

Miss the compile output?  Hint:
EMERGE_DEFAULT_OPTS="--quiet-build=n"