From: Dan Carpenter <dan.carpenter@linaro.org>
To: rust-for-linux@vger.kernel.org, Mark Brown <broonie@kernel.org>
Cc: Miguel Ojeda <ojeda@kernel.org>,
Alex Gaynor <alex.gaynor@gmail.com>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Oct 2
Date: Thu, 2 Oct 2025 23:10:45 +0300 [thread overview]
Message-ID: <aN7cRUOxq-zwCoZN@stanley.mountain> (raw)
In-Reply-To: <aN6qWFc6hIcbRU1o@sirena.org.uk>
Rust is broken on today's linux-next (next-20251002) on Debian forky/sid.
regards,
dan carpenter
$ make -j32
SYNC include/config/auto.conf
HOSTCC scripts/basic/fixdep
CALL scripts/checksyscalls.sh
RUSTC L rust/core.o
error: cannot find a built-in macro with name `define_opaque`
--> /usr/lib/rustlib/src/rust/library/core/src/macros/mod.rs:1757:5
|
1757 | / pub macro define_opaque($($tt:tt)*) {
1758 | | /* compiler built-in */
1759 | | }
| |_____^
error: attributes starting with `rustc` are reserved for use by the `rustc` compiler
--> /usr/lib/rustlib/src/rust/library/core/src/pin.rs:1946:28
|
1946 | #[cfg_attr(not(bootstrap), rustc_macro_edition_2021)]
| ^^^^^^^^^^^^^^^^^^^^^^^^
error: cannot find attribute `rustc_macro_edition_2021` in this scope
--> /usr/lib/rustlib/src/rust/library/core/src/pin.rs:1946:28
|
1946 | #[cfg_attr(not(bootstrap), rustc_macro_edition_2021)]
| ^^^^^^^^^^^^^^^^^^^^^^^^
error[E0522]: definition of an unknown lang item: `use_cloned`
--> /usr/lib/rustlib/src/rust/library/core/src/clone.rs:219:28
|
219 | #[cfg_attr(not(bootstrap), lang = "use_cloned")]
| ^^^^^^^^^^^^^^^^^^^ definition of unknown lang item `use_cloned`
error[E0522]: definition of an unknown lang item: `RangeMin`
--> /usr/lib/rustlib/src/rust/library/core/src/pat.rs:28:32
|
28 | #[cfg_attr(not(bootstrap), lang = "RangeMin")]
| ^^^^^^^^^^^^^^^^^ definition of unknown lang item `RangeMin`
error[E0522]: definition of an unknown lang item: `RangeMax`
--> /usr/lib/rustlib/src/rust/library/core/src/pat.rs:32:32
|
32 | #[cfg_attr(not(bootstrap), lang = "RangeMax")]
| ^^^^^^^^^^^^^^^^^ definition of unknown lang item `RangeMax`
error[E0522]: definition of an unknown lang item: `RangeSub`
--> /usr/lib/rustlib/src/rust/library/core/src/pat.rs:36:32
|
36 | #[cfg_attr(not(bootstrap), lang = "RangeSub")]
| ^^^^^^^^^^^^^^^^^ definition of unknown lang item `RangeSub`
error: requires `format_alignment` lang_item
--> /usr/lib/rustlib/src/rust/library/core/src/macros/mod.rs:623:24
|
623 | $dst.write_fmt($crate::format_args!($($arg)*))
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
::: /usr/lib/rustlib/src/rust/library/core/src/any.rs:790:13
|
790 | write!(f, "TypeId({:#034x})", self.as_u128())?;
| --------------------------------------------- in this macro invocation
|
= note: this error originates in the macro `$crate::format_args` which comes from the expansion of the macro `write` (in Nightly builds, run with -Z macro-backtrace for more info)
error: aborting due to 8 previous errors
For more information about this error, try `rustc --explain E0522`.
make[2]: *** [rust/Makefile:507: rust/core.o] Error 1
make[1]: *** [/home/dcarpenter/progs/kernel/trees/Makefile:1286: prepare] Error 2
make: *** [Makefile:248: __sub-make] Error 2
next prev parent reply other threads:[~2025-10-02 20:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 16:37 linux-next: Tree for Oct 2 Mark Brown
2025-10-02 20:10 ` Dan Carpenter [this message]
2025-10-02 21:35 ` Miguel Ojeda
2025-10-03 7:05 ` Dan Carpenter
2025-10-03 19:16 ` Dan Carpenter
-- strict thread matches above, loose matches on Subject: below --
2024-10-02 4:50 Stephen Rothwell
2020-10-02 9:57 Stephen Rothwell
2019-10-02 4:46 Stephen Rothwell
2018-10-02 9:18 Stephen Rothwell
2015-10-02 5:27 Stephen Rothwell
2014-10-02 10:26 Stephen Rothwell
2013-10-02 15:32 Thierry Reding
2012-10-02 6:32 Stephen Rothwell
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=aN7cRUOxq-zwCoZN@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=alex.gaynor@gmail.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.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