public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: james <garftd@verizon.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Specific MAKEOPTS for one package
Date: Wed, 26 Sep 2018 09:57:19 -0400	[thread overview]
Message-ID: <7fe78231-ed1d-dcff-b919-7f36e2ff4c9f@verizon.net> (raw)
In-Reply-To: <20180925140536.GB10424@ikki.ethgen.ch>

On 9/25/18 10:05 AM, Klaus Ethgen wrote:
> Thanks Dale and Michael, that was exactly I was searching for. (I think.
> ;-)
> 
> Am Di den 25. Sep 2018 um 15:00 schrieb Peter Humphrey:
>> On Tuesday, 25 September 2018 14:25:50 BST Klaus Ethgen wrote:
> 
>>> Is there an option to set -j1 just for firefox package? (and rust, that
>>> has the same problem)?
> 
>> As Dale and Michael said, but you may find -j2 acceptable; It's what I use for 
>> everything here.
> 
> No. Firefox and Rust is such a beast. It kills my machine even with -j2.
> 
> Regards
>    Klaus
> 
> 

Memory may be your issue. A wide variety of places to look at::
ebuild
kernel
userland


I'd suggest you start with reading up on 'jemalloc' as a place to start.
Hopefully other will 'chime in' on debugging/controlling memory
constrained systems and large memory requirements on older/limited
resources.

hth,
James


  reply	other threads:[~2018-09-26 13:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-25 13:25 [gentoo-user] Specific MAKEOPTS for one package Klaus Ethgen
2018-09-25 13:31 ` Michael Orlitzky
2018-09-25 13:34 ` Dale
2018-09-25 14:00 ` Peter Humphrey
2018-09-25 14:05   ` Klaus Ethgen
2018-09-26 13:57     ` james [this message]
2018-09-28  4:19 ` Walter Dnes
2018-10-01 11:34   ` Klaus Ethgen
2018-10-01 14:45     ` Michael Orlitzky
2018-10-01 19:48     ` Walter Dnes

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=7fe78231-ed1d-dcff-b919-7f36e2ff4c9f@verizon.net \
    --to=garftd@verizon.net \
    --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