Re: VirtualBox: invisible executable

On Thu, Feb 5, 2015 at 8:48 PM, Mark Knecht <[email protected]> wrote:
> On Thu, Feb 5, 2015 at 11:43 AM, Tamas Karpati <[email protected]> wrote:
>> Dear Mark,
>>
>> Thank you for your effort again. Quick rechecked to see that all four
>> pkgs that you've mentioned are already installed. I think this comes
>> from the USE flags, I've added extensions and sdk to defaults.
>> Besides, I use "emerge -vbuND", not just "emerge -v".
>>
>> Regards,
>>   toma
>>
>
> Please bottom post if possible. Thanks.

sure. sorry!

> -b is OK. I do that and a bit more in my make.conf file:
>
> EMERGE_DEFAULT_OPTS="--with-bdeps=y --jobs=5"

Ooops, --jobs is very very wild! I will cosider bdeps, too.

> MAKEOPTS="-j13 -l8"

This I already use, although not much gain when Python is in action.
(Maybe --jobs was invented for this reason?)

> PORTAGE_NICENESS=5
> PORTAGE_IONICE_COMMAND="ionice -c 3 -p \${PID}"

Usually I just have my coffee during emerge -u, no desktop
work on this machine that time, but maybe usefull if do not want to kill
the simulations during builds that do not need the recompilation of the SWs.
I update when no calculation is in progress.
NB: last two options haven't yet hit my man pages.

> Note that this is a 12 core processor machine so those setting may
> well not be right for your hardware.

Wow, nice. kernel baked in 2 mins? great.

Anyways, VB is not yet working and only I'll have the time for WS next
week. Will let you know the results. Thank you so much so far,
   toma