<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Hi, I maintain raspbian and have been trying to update rustc in
raspbian bullseye to get it back in sync with Debian bullseye.
Debian bullseye recently skipped forward from 0.34 to 0.37<br>
<br>
The rustc package in raspbian is broadly the same as the one in
Debian except we change the triplet (rust uses
arm-unknown-linux-gnueabihf for armv6).<br>
<br>
The upgrade from 1.34 to 1.35 went broadly as expected*, however
trying to upgrade from 1.35 to 1.36 failed. <br>
<br>
error: extern location for rustc does not exist:
/rustc/build/arm-unknown-linux-gnueabihf/stage0-rustc/arm-unknown-linux-gnueabihf/release/deps/librustc-6cf22a64f23a8aef.so
<br>
<br>
<blockquote type="cite">error[E0463]: can't find crate for
`rustc`
<br>
-->
src/librustc_incremental/lib.rs:13:14
<br>
|
<br>
13 | #[macro_use] extern crate
rustc;
<br>
| ^^^^^^^^^^^^^^^^^^^ can't find
crate
<br>
<br>
error: aborting due to 2 previous
errors
<br>
<br>
For more information about this error, try `rustc --explain
E0463`.</blockquote>
googling the error didn't turn up anything useful.<br>
<br>
Full build log at <a class="moz-txt-link-freetext" href="http://plugwash.raspbian.org/rustc1.36.log">http://plugwash.raspbian.org/rustc1.36.log</a><br>
<br>
I then decided to try a different approach, setting up a "dirty"
chroot that was mostly raspbian, but with rustc from debian armhf
and using that to build a rustc 1.37 package for raspbian. That
also failed with a similar but slightly different error.</p>
<p>
<blockquote type="cite">error[E0463]: can't find crate for
`rustc_macros` which `rustc` depends
on
<br>
-->
src/librustc_codegen_llvm/lib.rs:34:14
<br>
|
<br>
34 | #[macro_use] extern crate
rustc;
<br>
| ^^^^^^^^^^^^^^^^^^^ can't find
crate
<br>
<br>
error: aborting due to previous
error
<br>
<br>
For more information about this error, try `rustc --explain
E0463`.</blockquote>
There was also an error earlier in the build about being unable to
find STD while buliding "backtrace".<br>
<br>
Googling the error turned up
<a class="moz-txt-link-freetext" href="https://github.com/rust-lang/rust/issues/62447">https://github.com/rust-lang/rust/issues/62447</a>, but the hint there
to add "<code>-C target-feature=-crt-static</code>" to RUSTFLAGS
did not help.<br>
<br>
A full log for that build can be found at
<a class="moz-txt-link-freetext" href="http://plugwash.raspbian.org/rustc1.37.log">http://plugwash.raspbian.org/rustc1.37.log</a><br>
<br>
Any ideas on what is going wrong and how I can get an up to date
rustc into raspbian bullseye?<br>
</p>
<p><br>
* The long standing issue that fabricate livelocks on one of our
build boxes was worked around by building on a different box. The
cargo home issue was worked around by building in a non-sbuild
environment.<br>
</p>
</body>
</html>