Your message dated Wed, 18 Apr 2018 21:19:56 +0000
with message-id <[email protected]>
and subject line Bug#895300: fixed in cargo 0.25.0-3
has caused the Debian Bug report #895300,
regarding cargo: Please disable incremental-by-default on sparc64
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
895300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895300
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: cargo
Version: 0.25.0-2
Severity: normal
User: [email protected]
Usertags: sparc64
Hello!
The change to enable incremental builds by default unfortunately currently
breaks Rust builds on sparc64. I have observed this problem for building
both Firefox and the Rust compiler and it looks like this [1]:
Compiling cmake v0.1.29
Running `/usr/bin/rustc --crate-name cmake vendor/cmake/src/lib.rs
--crate-type lib --emit=dep-info,link -C debug-assertions=off -C
overflow-checks=on -C metadata=e1cd2a47defb4d9a -C
extra-filename=-e1cd2a47defb4d9a --out-dir
'/<<BUILDDIR>>/rustc-1.25.0+dfsg1/build/bootstrap/debug/deps' -L
'dependency=/<<BUILDDIR>>/rustc-1.25.0+dfsg1/build/bootstrap/debug/deps'
--extern
'cc=/<<BUILDDIR>>/rustc-1.25.0+dfsg1/build/bootstrap/debug/deps/libcc-9169eb827816c87c.rlib'
--cap-lints warn -Cdebuginfo=2`
error: incremental compilation: could not create session directory lock file:
No such process (os error 3)
error: internal compiler error: unexpected panic
note: the compiler unexpectedly panicked. this is a bug.
note: we would appreciate a bug report:
https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md#bug-reports
note: rustc 1.24.1 running on sparc64-unknown-linux-gnu
note: run with `RUST_BACKTRACE=1` for a backtrace
thread 'rustc' panicked at 'src/librustc/session/mod.rs:665: Trying to get
session directory from IncrCompSession `NotInitialized`',
src/librustc/session/mod.rs:1141:26
stack backtrace:
0: rust_metadata_std_e973fcbcfde4db1b7f5619ab17536071
1: rust_metadata_std_e973fcbcfde4db1b7f5619ab17536071
2: rust_metadata_std_e973fcbcfde4db1b7f5619ab17536071
3: rust_metadata_std_e973fcbcfde4db1b7f5619ab17536071
4: std::panicking::rust_panic_with_hook
5: rust_metadata_rustc_f5b4f956815e4c315eb00c57eaa07f5b
6: <unknown>
7: rust_metadata_rustc_f5b4f956815e4c315eb00c57eaa07f5b
8: rustc::session::bug_fmt
9: rustc::session::Session::incr_comp_session_dir
10: rustc_incremental::persist::load::load_dep_graph
11: <unknown>
12: rustc_driver::driver::compile_input
13: rustc_driver::run_compiler
14: <unknown>
15: <unknown>
16: __rust_maybe_catch_panic
17: <unknown>
18: rust_metadata_std_e973fcbcfde4db1b7f5619ab17536071
19: rust_metadata_std_e973fcbcfde4db1b7f5619ab17536071
20: <unknown>
error: Could not compile `build_helper`.
I have not yet figured out what the problem is, but I can work-around the
issue by setting CARGO_INCREMENTAL=0 in the build environment.
Would it be possible to disable incremental builds on sparc64 by default
until this issue has been resolved? I assume that the problem is that
the incremental builds are not 100% thread-safe yet and might cause issues
on SPARC servers which often have many CPUs available.
Thanks,
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - [email protected]
`. `' Freie Universitaet Berlin - [email protected]
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
--- End Message ---
--- Begin Message ---
Source: cargo
Source-Version: 0.25.0-3
We believe that the bug you reported is fixed in the latest version of
cargo, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Vasudev Kamath <[email protected]> (supplier of updated cargo package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Sun, 15 Apr 2018 12:28:29 +0530
Source: cargo
Binary: cargo cargo-doc
Architecture: source
Version: 0.25.0-3
Distribution: sid
Urgency: medium
Maintainer: John Paul Adrian Glaubitz <[email protected]>
Changed-By: Vasudev Kamath <[email protected]>
Description:
cargo - Rust package manager
cargo-doc - Rust package manager, documentation
Closes: 895300
Changes:
cargo (0.25.0-3) unstable; urgency=medium
.
[ Ximin Luo ]
* Update Vcs-* fields to salsa
.
[ Vasudev Kamath ]
* Add patch to prevent incremental builds on sparc64.
Closes: bug#895300, Thanks to John Paul Adrian Glaubitz.
Checksums-Sha1:
0dcedae905774c890d062809488ae6d3d842342c 2723 cargo_0.25.0-3.dsc
a56c2c03d34f0050e67b61420448aa8e60cd1ddc 36884 cargo_0.25.0-3.debian.tar.xz
7d1eb507795a48874cb5e771f728c0c8a23c9545 7644 cargo_0.25.0-3_amd64.buildinfo
Checksums-Sha256:
5468da3c25493232950dd4f2cfa75f573963fb6a28a22c49cf295806f4644c4e 2723
cargo_0.25.0-3.dsc
018e16765ca1b9b2f204eea25a1c0985b0dbe262fb662e1c0656585d29731481 36884
cargo_0.25.0-3.debian.tar.xz
9bde13576121689c1589ba8ca629993573711776b40a11de3012ef88849ae1de 7644
cargo_0.25.0-3_amd64.buildinfo
Files:
2122d809badf01a9bd5c1241004d268f 2723 devel optional cargo_0.25.0-3.dsc
87bfecf0dcd30718bc08e58c2d34ef97 36884 devel optional
cargo_0.25.0-3.debian.tar.xz
e9653d57fa2f66e82fd4569fe1af402c 7644 devel optional
cargo_0.25.0-3_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEYv+KdYTgKVaVRgAGdCY7N/W1+RMFAlrXsuUACgkQdCY7N/W1
+RMwRg//bK8uADKYWXP7+3/pD/KrExJU4xa94X1AXbTv/HMecVSudbpaBwZSYAya
4AAVmYRQV10T2rhtGCltWo48a0AlVyHWBg++MRemiXQXBViGsksPx1PQk55T32I7
LhfThbZm4twoI19N7WRcvhSxmb3fC1nwFIzfVJDrKhN/XnY/3NbFSmN8w5aWUQkf
tsKZkzXuAhEJyu6MAzDZsz0XrMae/sU5MlX4CdrsIUcMm6flF1E7Vd3yN0FzgtiS
pow7u4CWhGRCwGE1058s10v+an8MVWin13YlyxmUl0dSeLnYf30pJ/ugt/1nJZA/
JfjUW66LfciQzlbrt9Azofd8JlTVRMZzo9aH49U2bc9kmIcFfELMqAFMzkMC5HC0
puq0XScPw+oLmRJgrYqeRz0pLPZ1rzXtpObo0Rkt9uIzoOHHO/G9Be12/uqECjlk
ve0WoxPrLMEQYEHCB24hfmwZISS5Tuu/aKVTYV5HHVv/4qcZdFzzZcozD4d67XYY
E50KpkrED/ixbnhm5Pq2yGAd9kRMSv98VYOyz0t0DexdiQ9bb9pc0A259qZj2ibb
X1hy8fS+1YksVfm835AqZGlUxwTFCcFgUBZSyAkUKEqNpHa7ioP/kqaSP+COMU1H
U8KElsb1leNVaW8NG/LtoYBoH7fA84uE/1152ztn6Bq8wXVGjfg=
=ruoN
-----END PGP SIGNATURE-----
--- End Message ---
