public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Rust problem when upgrading Firefox
Date: Mon, 15 Oct 2018 14:04:24 -0500	[thread overview]
Message-ID: <7a61d9f0-3b07-504c-01b1-b6614f504d60@gmail.com> (raw)
In-Reply-To: <20181015184959.GG1848@ca.inter.net>

Philip Webb wrote:
> I finally needed to upgrade to FF 60.2.2 .
> This has several large requirements, incl Rust 1.29.1 .
>
> The 1st time I tried, Rust failed after 35 min with these final lines :
>
>   Compiling rustc-rayon v0.1.1
>   Compiling rustc_data_structures v0.0.0 (file:///var/tmp/portage/portage/dev-lang/rust-1.29.1/work/rustc-1.29.1-src/src/librustc_data_structures)
>   Compiling arena v0.0.0 (file:///var/tmp/portage/portage/dev-lang/rust-1.29.1/work/rustc-1.29.1-src/src/libarena)
>   Compiling syntax_pos v0.0.0 (file:///var/tmp/portage/portage/dev-lang/rust-1.29.1/work/rustc-1.29.1-src/src/libsyntax_pos)
>   Compiling rustc_errors v0.0.0 (file:///var/tmp/portage/portage/dev-lang/rust-1.29.1/work/rustc-1.29.1-src/src/librustc_errors)
>   Compiling proc_macro v0.0.0 (file:///var/tmp/portage/portage/dev-lang/rust-1.29.1/work/rustc-1.29.1-src/src/libproc_macro)
>   Compiling syntax_ext v0.0.0 (file:///var/tmp/portage/portage/dev-lang/rust-1.29.1/work/rustc-1.29.1-src/src/libsyntax_ext)
>   error: linking with `x86_64-pc-linux-gnu-gcc` failed: exit code: 1
>   |
>   = note: "x86_64-pc-linux-gnu-gcc" "-Wl,--as-needed" "-Wl,-z,noexecstack" "-m64" "-L" "/var/tmp/portage/portage/dev-lang/rust-1.29.1/work/rustc-1.29.1-src/build/x86_64-unknown-linux-gnu/stage1/lib64/rust\ ...
>
> This looked like a missing library or similar,
> so I recompiled with extra flags  USE="cargo clang rust gold" :
> "cargo clang rust" refer to other pkgs which FF requires
> & "gold" was then demanded by Portage when I tested with '-pv'.
>
> The 2nd time I tried with these USE flags, I got :
>
>   Compiling rustc_data_structures v0.0.0 (file:///var/tmp/portage/portage/dev-lang/rust-1.29.1/work/rustc-1.29.1-src/src/librustc_data_structures)
>   Compiling arena v0.0.0 (file:///var/tmp/portage/portage/dev-lang/rust-1.29.1/work/rustc-1.29.1-src/src/libarena)
>   Compiling syntax_pos v0.0.0 (file:///var/tmp/portage/portage/dev-lang/rust-1.29.1/work/rustc-1.29.1-src/src/libsyntax_pos)
>   Compiling rustc_errors v0.0.0 (file:///var/tmp/portage/portage/dev-lang/rust-1.29.1/work/rustc-1.29.1-src/src/librustc_errors)
>   Compiling proc_macro v0.0.0 (file:///var/tmp/portage/portage/dev-lang/rust-1.29.1/work/rustc-1.29.1-src/src/libproc_macro)
>   Compiling syntax_ext v0.0.0 (file:///var/tmp/portage/portage/dev-lang/rust-1.29.1/work/rustc-1.29.1-src/src/libsyntax_ext)
> LLVM ERROR: IO failure on output stream: No space left on device
> error: Could not compile `rustc`.
>
> Caused by:
>   process didn't exit successfully: `/var/tmp/portage/portage/dev-lang/rust-1.29.1/work/rustc-1.29.1-src/build/bootstrap/debug/rustc --crate-name rustc librustc/lib.rs --error-format json --crate-type dyl\ ...
>
> Earlier, I found I had to add 'llvm' to /etc/portage/package.env :
> apparently it overflowed my usual /var/tmp/portage 'tmpfs'.
> I will try again after adding 'rust' there too,
> but meanwhile does anyone have any similar experience or other advice ?
>


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.  

Hope that helps.

Dale

:-)  :-)  



  reply	other threads:[~2018-10-15 19:04 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 [this message]
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

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=7a61d9f0-3b07-504c-01b1-b6614f504d60@gmail.com \
    --to=rdalek1967@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