public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Franz Fellner <alpine.art.de@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Rust problem when upgrading Firefox
Date: Tue, 16 Oct 2018 11:38:20 +0200	[thread overview]
Message-ID: <CADtyuE4y1H0rhw+admuRmo1=tVcBWHcjDcC=D2TKFUoSaENwcA@mail.gmail.com> (raw)
In-Reply-To: <2610125.4NNjHNgcKo@dell_xps>

[-- Attachment #1: Type: text/plain, Size: 1890 bytes --]

My "other advice" would be to simply use rust-bin.

Am Di., 16. Okt. 2018 um 11:25 Uhr schrieb Mick <michaelkintzios@gmail.com>:

> On Monday, 15 October 2018 19:49:59 BST Philip Webb wrote:
> > 181015 Dale wrote:
> > > Just curious, did you notice this little part?
> > > "LLVM ERROR: IO failure on output stream: No space left on device"
> > > You may want to make sure you are not out of disk space
> > > wherever your tmp directory is or out of ram if you use tmpfs.
> >
> > Yes, I did, as I said, & added  2  lines to 'package.env'.
> > That solved that problem, which was surprising :
> > my explanation is that FF itself is too big to use 'tmpfs'
> > & this then squeezes out any other pkgs to be compiled along with it,
> > even a tiny virtual.  Otherwise, the 1st problem was USE flags.
> >
> > The new FF requires some very big items, which took a long time to
> emerge :
> > Rust (59), Clang (11), Llvm (15), FF (33) : total  118 min .
> > The total download was  c 500 MB .  LO is modest in comparison.
> >
> > Now to get some groceries, then I'll try it out.
> > The big question is whether I can still group tabs,
> > whether directly with FF or via some add-on (whatever they're now
> called).
> >
> > Thanks for offering a bit of help.
>
> I've noticed the same both in terms of the dependencies now being drawn in
> and
> in terms of how much RAM the compile consumes.  On systems with low RAM I
> set
> lower MAKEOPTS jobs and average values and add plenty of swap.  This keeps
> emerge in check and stops it from swapping in and out continuously
> thrashing
> the disk.
>
> More than a year ago I'd noticed similar uncontrolled consumption of
> resources
> by emerge on Chromium.  Interestingly a few versions later something must
> have
> changed (some hardware limit checks added by devs?) and Chromium became
> much
> less hungry for resources.
> --
> Regards,
> Mick

[-- Attachment #2: Type: text/html, Size: 2393 bytes --]

      reply	other threads:[~2018-10-16  9:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-15 18:49 [gentoo-user] Rust problem when upgrading Firefox Philip Webb
2018-10-15 19:04 ` Dale
2018-10-15 21:24   ` [gentoo-user] Rust problem when upgrading Firefox : solved Philip Webb
2018-10-16  0:28     ` Dale
2018-10-22  5:26     ` [gentoo-user] Re: tab-grouping in Firefox Philip Webb
2018-10-22  5:36       ` Davyd McColl
2018-10-22  6:21         ` Khaosgrille
2018-10-16  9:25 ` [gentoo-user] Rust problem when upgrading Firefox Mick
2018-10-16  9:38   ` Franz Fellner [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='CADtyuE4y1H0rhw+admuRmo1=tVcBWHcjDcC=D2TKFUoSaENwcA@mail.gmail.com' \
    --to=alpine.art.de@gmail.com \
    --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