public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "J. Roeleveld" <joost@antarean.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Rusty problems
Date: Wed, 28 Apr 2021 09:04:05 +0200	[thread overview]
Message-ID: <11740769.O9o76ZdvQC@iris> (raw)
In-Reply-To: <YIh5tzP8L7WmVG98@ACM>

On Tuesday, April 27, 2021 10:53:11 PM CEST Alan Mackenzie wrote:
> 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!

I managed to get it to compile with a 16GB ramdisk using "system-llvm":


$ grep -r rust /etc/portage
/etc/portage/profile/package.use.mask:dev-lang/rust -system-llvm
/etc/portage/package.use/rust:dev-lang/rust system-llvm parallel-compiler

It claims it wants:
Checking for at least 13312 MiB

From the build-log:

======
 * Final size of build directory: 12344956 KiB ( 11.7 GiB)
 * Final size of installed tree:    366492 KiB (357.9 MiB)

 * The ebuild is installing to one or more unexpected paths:
 * 
 *   /usr/share/doc/rust-1.51.0
 * 
 * Please fix the ebuild to use correct FHS/Gentoo policy paths.
=======

Hope this helps,

Joost




  parent reply	other threads:[~2021-04-28  7:04 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
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 [this message]
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=11740769.O9o76ZdvQC@iris \
    --to=joost@antarean.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