[gentoo-user] Rust problem when upgrading Firefox
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 ? -- ,, SUPPORT ___//___, Philip Webb ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto TRANSIT`-O--O---' purslowatchassdotutorontodotca
Re: [gentoo-user] Rust problem when upgrading Firefox
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 :-) :-)
Re: [gentoo-user] Rust problem when upgrading Firefox : solved
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. -- ,, SUPPORT ___//___, Philip Webb ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto TRANSIT`-O--O---' purslowatchassdotutorontodotca
Re: [gentoo-user] Rust problem when upgrading Firefox : solved
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. > After I went back and reread your post, I see that you mentioned that. Funny how I missed that but saw the out of space part. :/ I to used tab groups. I tested every tab group add on I could find. I'll go ahead and tell you now, none of them are like the old tab group add on. However, the closest I can find is simple tab group. Here's a link. https://addons.mozilla.org/en-US/firefox/addon/simple-tab-groups/?src=search I used to use tab utilities to help manage tabs. Sometimes I have a LOT of tabs open. I now use this. https://addons.mozilla.org/en-US/firefox/addon/tree-style-tab/?src=search I might add, I also use profiles so that I can log into certain sites as more than one user. The new Firefox has a nifty new thing called containers that can help with that. Here is the best add on I could find for that. https://addons.mozilla.org/en-US/firefox/addon/multi-account-containers/?src=search Instead of me typing, youtube some of those. It helps a LOT to see what others are doing. I recommend at least two videos each. More if you want to really get a wide range of ideas. The way I did this, I bookmarked everything and then started fresh after the upgrade. You may also want to look into conex add on if simple tab group isn't to your liking. I didn't like it but . . . Also Tree style tab has a group add on that works with it, wasn't for me but you may like it. On tmpfs, I have the following set to compile on the hard drive instead of tmpfs. This is my env file. www-client/firefox ../env/notmpfs.conf www-client/seamonkey ../env/notmpfs.conf app-office/libreoffice ../env/notmpfs.conf sys-devel/gcc ../env/notmpfs.conf dev-qt/qtwebengine ../env/notmpfs.conf dev-qt/qtwebkit ../env/notmpfs.conf sci-electronics/kicad ../env/notmpfs.conf Those are packages that over time, I've learned either requires to much ram or requires to much when being built with other packages. Usually, if it is only one, they can fit. However, any two of them ends up being compiled at the same time causes problems. Hope that helps. Dale :-) :-) P. S. Here is my USE flags for Firefox. It works well here. That said, I may could reset some of these given them major changes in recent Firefox. Just a suggestion if you should need it. [ebuild R ~] www-client/firefox-62.0.3::gentoo USE="dbus gmp-autoupdate screenshot startup-notification system-harfbuzz system-jpeg system-libevent system-libvpx system-sqlite -bindist -clang -custom-cflags -custom-optimization -debug -eme-free -geckodriver -hardened -hwaccel -jack -lto (-neon) -pulseaudio (-selinux) -system-icu -test -wifi"
