From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Controlling emerges
Date: Tue, 19 Sep 2023 06:06:15 -0400 [thread overview]
Message-ID: <CAGfcS_ke5eEHe9fXwmAzyj9Lfy8aK1MocctU_uiqmLoNMA7+EA@mail.gmail.com> (raw)
In-Reply-To: <2168301.irdbgypaU6@wstn>
On Tue, Sep 19, 2023 at 5:48 AM Peter Humphrey <peter@prh.myzen.co.uk> wrote:
>
> On Tuesday, 19 September 2023 10:14:42 BST William Kenworthy wrote:
> > That is where you set per package compiler parameters by overriding
> > make.conf settings.
>
> And which make.conf setting might achieve what I want? Careful reading of the
> make.conf man page hasn't revealed anything relevant.
>
There isn't one. At best there is -l which regulates jobs by system
load, but there is nothing that takes into account RAM use.
I just use package.env to limit jobs on packages that I know are RAM-hungry.
Right now my list includes:
calligra
qtwebengine
qtwebkit
ceph
nodejs
passwdqc
scipy
pandas
spidermonkey
(It has been ages since I've pruned the list, and of course what is
"too much RAM" will vary.)
The other thing I will tweak is avoiding building in a tmpfs.
Obviously anything that is RAM constrained is a good contender for not
using a tmpfs, but there are also packages that just have really large
build directories that otherwise don't need to much RAM when building.
--
Rich
next prev parent reply other threads:[~2023-09-19 10:06 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 12:00 [gentoo-user] Controlling emerges Peter Humphrey
2023-09-18 12:59 ` Jack
2023-09-18 13:44 ` Peter Humphrey
2023-09-18 13:48 ` Alan McKinnon
2023-09-18 16:03 ` Peter Humphrey
2023-09-18 16:13 ` Alan McKinnon
2023-09-18 17:54 ` Laurence Perkins
2023-09-18 22:44 ` William Kenworthy
2023-09-19 9:09 ` Peter Humphrey
2023-09-19 9:14 ` William Kenworthy
2023-09-19 9:37 ` Andreas Fink
2023-09-19 9:48 ` Peter Humphrey
2023-09-19 10:06 ` Rich Freeman [this message]
2023-09-19 10:13 ` William KENWORTHY
2023-09-18 17:59 ` Michael
2023-09-18 18:10 ` John Blinka
2023-09-18 18:18 ` Dale
2023-09-18 18:49 ` Rich Freeman
2023-09-19 12:28 ` Peter Humphrey
2023-09-20 22:06 ` Wol
2023-09-21 19:26 ` Laurence Perkins
2023-09-21 20:30 ` Tsukasa Mcp_Reznor
2023-09-22 1:13 ` Dale
2023-09-22 7:13 ` Michael
2023-09-22 10:07 ` Rich Freeman
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=CAGfcS_ke5eEHe9fXwmAzyj9Lfy8aK1MocctU_uiqmLoNMA7+EA@mail.gmail.com \
--to=rich0@gentoo.org \
--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