From: "Sid Spry" <sid@aeam.us>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Limit Memory Used By Portage/Firefox Build Causes OOM
Date: Sun, 21 Jun 2020 22:11:03 -0500 [thread overview]
Message-ID: <0614114d-1ab5-4649-8dff-028e576087ad@www.fastmail.com> (raw)
In-Reply-To: <20200622011315.GA2450@waltdnes.org>
On Sun, Jun 21, 2020, at 8:13 PM, Walter Dnes wrote:
> On Sun, Jun 21, 2020 at 06:02:22PM -0500, Sid Spry wrote
> >
> > My immediate issue is cargo seems to ignore MAKEOPTS. Cargo
> > also seems to select build parallelism itself.
>
> You can also set the load average in MAKEOPTS ("-l" parameter; letter
> "ell") to indirectly force fewer jobs. Try...
>
> MAKEOPTS="-j1 -l1.5"
>
> See also https://wiki.gentoo.org/wiki//etc/portage/package.env and
> https://wiki.gentoo.org/wiki/Knowledge_Base:Overriding_environment_variables_per_package for pointers on how to create package-specific make.conf files
> (or other stuff) for individual packages.
>
I did set this. It seems to be ignored. The llvm/clang portions of
the build do abide by them but part of the build still runs out of
memory.
prev parent reply other threads:[~2020-06-22 3:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-21 23:02 [gentoo-user] Limit Memory Used By Portage/Firefox Build Causes OOM Sid Spry
2020-06-22 1:13 ` Walter Dnes
2020-06-22 3:11 ` Sid Spry [this message]
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=0614114d-1ab5-4649-8dff-028e576087ad@www.fastmail.com \
--to=sid@aeam.us \
--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