From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Rusty problems
Date: Wed, 28 Apr 2021 00:09:12 +0100 [thread overview]
Message-ID: <20210428000759.6ed6696f@digimed.co.uk> (raw)
In-Reply-To: <YIh5tzP8L7WmVG98@ACM>
[-- Attachment #1: Type: text/plain, Size: 1686 bytes --]
On Tue, 27 Apr 2021 20:53:11 +0000, Alan Mackenzie wrote:
> Help! What am I supposed to do? I've got 16 Gb RAM (I'm _not_ going to
> use the word "only" here), and wondering just how big a chunk a ram disk
> can take out of that before the machine siezes up altogether. But if I
> increase the ram disk to 15 Gb, even assuming it'd work, it's only going
> to be a small number of releases before the clever people at rust
> increase their bloat even more.
Setting the RAM disk so high will mean you don't have enough memory for
the compilation, which will start swapping and everything will grind to a
near halt.
> I know I could plump for the -bin package. Maybe I should. But before
> I do that, is it possible to redirect this one ebuild away from
> /var/tmp/portage (my ram disk) without disturbing the other builds? If
> so, how would I do this (or where should I look for documentation)?
Lookup package.env on the wiki. I use rust-bin now, so this isn't an
issue for me, but my laptop has only 8GB and this is how I have it set
for chromium:
% cat /etc/portage/env/disk-tmpdir.conf
PORTAGE_TMPDIR="/mnt/scratch"
% cat /etc/portage/package.env/chromium
www-client/chromium disk-tmpdir.conf
I do similar for libreoffice and a couple of other heavyweights.
Another option, to be used instead of or as well as this would be distcc.
Once again, you can use package.env to apply this to selected packages:
% cat /etc/portage/env/distcc.conf
FEATURES="distcc buildpkg distlocks"
MAKEOPTS="-j36 -l4"
CFLAGS="-march=broadwell -O2 -pipe"
CXXFLAGS="${CFLAGS}"
--
Neil Bothwick
I'm firm. You're obstinate. He's a pigheaded fool.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-04-27 23:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 20:53 [gentoo-user] Rusty problems Alan Mackenzie
2021-04-27 21:17 ` Matt Connell (Gmail)
2021-04-27 22:00 ` Michael
2021-04-28 8:58 ` Wols Lists
2021-04-28 9:21 ` Michael
2021-04-27 22:02 ` tastytea
2021-04-27 22:38 ` Teru Yuu
2021-04-27 23:09 ` Neil Bothwick [this message]
2021-04-28 11:12 ` Alan Mackenzie
2021-04-28 12:03 ` Neil Bothwick
2021-04-28 22:05 ` antlists
2021-04-28 22:54 ` Neil Bothwick
2021-04-28 7:04 ` J. Roeleveld
2021-04-28 7:25 ` Andrew Lowe
2021-04-29 6:36 ` Adam Carter
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=20210428000759.6ed6696f@digimed.co.uk \
--to=neil@digimed.co.uk \
--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