Re: linux-next: Tree for Oct 2

Re: linux-next: Tree for Oct 2

[Dan Carpenter]

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

Re: linux-next: Tree for Oct 2

[Miguel Ojeda]

On Thu, Oct 2, 2025 at 10:10 PM Dan Carpenter <dan.carpenter@linaro.org> wrote:
>
>   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 | |     }
>      | |_____^
>

Thanks Dan.

Hmm... Strange, it is the `core` library, which comes with the
compiler and thus should always work.

So it sounds like a mismatch between the binary used and the sources
of the standard library (or perhaps other kind of mismatch, like the
wrong edition being passed, but from a quick look it doesn't seem like
it).

I will try to reproduce it. Did you happen to recently upgrade the
toolchain(s) or something like that, by chance? Are you using the
Debian packages?

Thanks!

Cheers,
Miguel

Re: linux-next: Tree for Oct 2

[Dan Carpenter]

On Thu, Oct 02, 2025 at 11:35:10PM +0200, Miguel Ojeda wrote:
> On Thu, Oct 2, 2025 at 10:10 PM Dan Carpenter <dan.carpenter@linaro.org> wrote:
> >
> >   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 | |     }
> >      | |_____^
> >
> 
> Thanks Dan.
> 
> Hmm... Strange, it is the `core` library, which comes with the
> compiler and thus should always work.
> 
> So it sounds like a mismatch between the binary used and the sources
> of the standard library (or perhaps other kind of mismatch, like the
> wrong edition being passed, but from a quick look it doesn't seem like
> it).
> 
> I will try to reproduce it. Did you happen to recently upgrade the
> toolchain(s) or something like that, by chance? Are you using the
> Debian packages?

Yes.  I am using the debian packages.  To be honest, I don't know it I
broke it with an update.  It's possible.  I am all the way updated with
`apt dist-upgrade`.

I'm on rustc version 1.87.0+dfsg1-1.

regards.
dan carpenter

Re: linux-next: Tree for Oct 2

[Dan Carpenter]

On Fri, Oct 03, 2025 at 10:05:11AM +0300, Dan Carpenter wrote:
> On Thu, Oct 02, 2025 at 11:35:10PM +0200, Miguel Ojeda wrote:
> > On Thu, Oct 2, 2025 at 10:10 PM Dan Carpenter <dan.carpenter@linaro.org> wrote:
> > >
> > >   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 | |     }
> > >      | |_____^
> > >
> > 
> > Thanks Dan.
> > 
> > Hmm... Strange, it is the `core` library, which comes with the
> > compiler and thus should always work.
> > 
> > So it sounds like a mismatch between the binary used and the sources
> > of the standard library (or perhaps other kind of mismatch, like the
> > wrong edition being passed, but from a quick look it doesn't seem like
> > it).
> > 
> > I will try to reproduce it. Did you happen to recently upgrade the
> > toolchain(s) or something like that, by chance? Are you using the
> > Debian packages?
> 
> Yes.  I am using the debian packages.  To be honest, I don't know it I
> broke it with an update.  It's possible.  I am all the way updated with
> `apt dist-upgrade`.
> 
> I'm on rustc version 1.87.0+dfsg1-1.
> 

It's fixed in today's linux-next.

I did go back and confirm that it was definitely something in the kernel
yesterday.  But it's fixed now, so no worries.

regards,
dan carpenter