public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Rusty problems
Date: Tue, 27 Apr 2021 20:53:11 +0000	[thread overview]
Message-ID: <YIh5tzP8L7WmVG98@ACM> (raw)

Hello, Gentoo.

I'm having problems building rust.

I build everything in a ram disk, and last night my 13 Gb ram disk
proved too small to build rust in.  So I increased its size to 14 Gb,
and tried again this evening.  Same result.  The pre-check on the disk
size gave an OK both times, and both runs lasted about 45 minutes before
running out of space.

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.

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)?

Thanks for the help!

-- 
Alan Mackenzie (Nuremberg, Germany).


             reply	other threads:[~2021-04-27 20:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-27 20:53 Alan Mackenzie [this message]
2021-04-27 21:17 ` [gentoo-user] Rusty problems 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
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=YIh5tzP8L7WmVG98@ACM \
    --to=acm@muc.de \
    --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