bug#48239: rust-1.19.0 build fails

[Mark H Weaver]

Hi,

Bone Baboon via Bug reports for GNU Guix <bug-guix@gnu.org> writes:
> On a x86_64 computer when I run `guix build --no-substitutes --cores=1
> rust` it fails during the build phase of rust-1.19.0.

Thanks for the report.

> The build log of rust-1.19.0 is attached.

Here are the last few lines of the log:

--8<---------------cut here---------------start------------->8---
(76/77) BUILDING cargo v0.20.0
> /gnu/store/c7w05pkmcpsqbng62wlxsna2zaybl9v5-mrustc-0.9/bin/mrustc 
> src/tools/cargo/src/cargo/lib.rs -o output/cargo-build/libcargo-0_20_0.rlib 
> --crate-name cargo --crate-type rlib -C 
> emit-depfile=output/cargo-build/libcargo-0_20_0.rlib.d --crate-tag 0_20_0 -g 
> --cfg debug_assertions -O -L output -L 
> /gnu/store/c7w05pkmcpsqbng62wlxsna2zaybl9v5-mrustc-0.9/lib/mrust -L 
> output/cargo-build --extern 
> crates_io=output/cargo-build/libcrates_io-0_9_0.rlib --extern 
> crossbeam=output/cargo-build/libcrossbeam-0_2_10.rlib --extern 
> curl=output/cargo-build/libcurl-0_4_6.rlib --extern 
> docopt=output/cargo-build/libdocopt-0_7_0.rlib --extern 
> env_logger=output/cargo-build/libenv_logger-0_4_2.rlib --extern 
> error_chain=output/cargo-build/liberror_chain-0_10_0.rlib --extern 
> filetime=output/cargo-build/libfiletime-0_1_10.rlib --extern 
> flate2=output/cargo-build/libflate2-0_2_19.rlib --extern 
> fs2=output/cargo-build/libfs2-0_4_1.rlib --extern 
> git2=output/cargo-build/libgit2-0_6_6.rlib --extern 
> git2_curl=output/cargo-build/libgit2_curl-0_7_0.rlib --extern 
> glob=output/cargo-build/libglob-0_2_11.rlib --extern 
> jobserver=output/cargo-build/libjobserver-0_1_6.rlib --extern 
> libc=output/cargo-build/liblibc-0_2_22.rlib --extern 
> libgit2_sys=output/cargo-build/liblibgit2_sys-0_6_12.rlib --extern 
> log=output/cargo-build/liblog-0_3_7.rlib --extern 
> num_cpus=output/cargo-build/libnum_cpus-1_4_0.rlib --extern 
> rustc_serialize=output/cargo-build/librustc_serialize-0_3_24.rlib --extern 
> scoped_tls=output/cargo-build/libscoped_tls-0_1_0.rlib --extern 
> semver=output/cargo-build/libsemver-0_7_0.rlib --extern 
> serde=output/cargo-build/libserde-1_0_6.rlib --extern 
> serde_derive=output/cargo-build/libserde_derive-1_0_6-plugin --extern 
> serde_ignored=output/cargo-build/libserde_ignored-0_0_3.rlib --extern 
> serde_json=output/cargo-build/libserde_json-1_0_2.rlib --extern 
> shell_escape=output/cargo-build/libshell_escape-0_1_3.rlib --extern 
> tar=output/cargo-build/libtar-0_4_13.rlib --extern 
> tempdir=output/cargo-build/libtempdir-0_3_5.rlib --extern 
> term=output/cargo-build/libterm-0_4_5.rlib --extern 
> toml=output/cargo-build/libtoml-0_4_1.rlib --extern 
> url=output/cargo-build/liburl-1_4_0.rlib --extern 
> openssl=output/cargo-build/libopenssl-0_9_12.rlib
BUILDING cargo v0.20.0
> /gnu/store/c7w05pkmcpsqbng62wlxsna2zaybl9v5-mrustc-0.9/bin/mrustc 
> src/tools/cargo/src/bin/cargo.rs -o output/cargo-build/cargo --crate-name 
> cargo --crate-type bin -C emit-depfile=output/cargo-build/cargo.d --crate-tag 
> 0_20_0 -g --cfg debug_assertions -O -L output -L 
> /gnu/store/c7w05pkmcpsqbng62wlxsna2zaybl9v5-mrustc-0.9/lib/mrust -L 
> output/cargo-build --extern cargo=output/cargo-build/libcargo-0_20_0.rlib 
> --extern crates_io=output/cargo-build/libcrates_io-0_9_0.rlib --extern 
> crossbeam=output/cargo-build/libcrossbeam-0_2_10.rlib --extern 
> curl=output/cargo-build/libcurl-0_4_6.rlib --extern 
> docopt=output/cargo-build/libdocopt-0_7_0.rlib --extern 
> env_logger=output/cargo-build/libenv_logger-0_4_2.rlib --extern 
> error_chain=output/cargo-build/liberror_chain-0_10_0.rlib --extern 
> filetime=output/cargo-build/libfiletime-0_1_10.rlib --extern 
> flate2=output/cargo-build/libflate2-0_2_19.rlib --extern 
> fs2=output/cargo-build/libfs2-0_4_1.rlib --extern 
> git2=output/cargo-build/libgit2-0_6_6.rlib --extern 
> git2_curl=output/cargo-build/libgit2_curl-0_7_0.rlib --extern 
> glob=output/cargo-build/libglob-0_2_11.rlib --extern 
> jobserver=output/cargo-build/libjobserver-0_1_6.rlib --extern 
> libc=output/cargo-build/liblibc-0_2_22.rlib --extern 
> libgit2_sys=output/cargo-build/liblibgit2_sys-0_6_12.rlib --extern 
> log=output/cargo-build/liblog-0_3_7.rlib --extern 
> num_cpus=output/cargo-build/libnum_cpus-1_4_0.rlib --extern 
> rustc_serialize=output/cargo-build/librustc_serialize-0_3_24.rlib --extern 
> scoped_tls=output/cargo-build/libscoped_tls-0_1_0.rlib --extern 
> semver=output/cargo-build/libsemver-0_7_0.rlib --extern 
> serde=output/cargo-build/libserde-1_0_6.rlib --extern 
> serde_derive=output/cargo-build/libserde_derive-1_0_6-plugin --extern 
> serde_ignored=output/cargo-build/libserde_ignored-0_0_3.rlib --extern 
> serde_json=output/cargo-build/libserde_json-1_0_2.rlib --extern 
> shell_escape=output/cargo-build/libshell_escape-0_1_3.rlib --extern 
> tar=output/cargo-build/libtar-0_4_13.rlib --extern 
> tempdir=output/cargo-build/libtempdir-0_3_5.rlib --extern 
> term=output/cargo-build/libterm-0_4_5.rlib --extern 
> toml=output/cargo-build/libtoml-0_4_1.rlib --extern 
> url=output/cargo-build/liburl-1_4_0.rlib --extern 
> openssl=output/cargo-build/libopenssl-0_9_12.rlib
"libcore"
command "output/rustc-build/rustc" "-C" 
"linker=/gnu/store/afpgzln8860m6yfhxy6i8n9rywbp85cy-gcc-7.5.0/bin/gcc" "-Z" 
"force-unstable-if-unmarked" "-L" "output/target-libs" "src/libcore/lib.rs" 
"-o" "output/target-libs/libcore.rlib" failed with signal 8
--8<---------------cut here---------------end--------------->8---

On x86_64-linux systems, signal 8 is SIGFPE i.e. a floating-point
exception, or "Erroneous arithmetic operation" as the comment says in
include/bits/signum-generic.h.

Are you aware of any relevant customizations to your kernel
configuration that might possibly be related to this?

For what it's worth, on my Thinkpad X200 (Core 2 Duo) with 4 GB of RAM
and 8 GB of swap, I've been successully building Rust locally using Guix
for many years, as long as I don't run other memory intensive processes
at the same time.

It might be worth trying the build a second time.  Occasionally we see
nondeterministic build failures in some packages, although I don't
recall seeing such failures in Rust.

     Regards,
       Mark

-- 
Disinformation flourishes because many people care deeply about
injustice but very few check the facts.  Ask me about
<https://stallmansupport.org>.