From: Dan Carpenter <dan.carpenter@linaro.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: rust-for-linux@vger.kernel.org, Mark Brown <broonie@kernel.org>,
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: Fri, 3 Oct 2025 22:16:17 +0300 [thread overview]
Message-ID: <aOAhAaUQdrFjJMk9@stanley.mountain> (raw)
In-Reply-To: <aN91pwLmB_2TwK77@stanley.mountain>
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
prev parent reply other threads:[~2025-10-03 19:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <aN6qWFc6hIcbRU1o@sirena.org.uk>
2025-10-02 20:10 ` linux-next: Tree for Oct 2 Dan Carpenter
2025-10-02 21:35 ` Miguel Ojeda
2025-10-03 7:05 ` Dan Carpenter
2025-10-03 19:16 ` Dan Carpenter [this message]
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=aOAhAaUQdrFjJMk9@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=miguel.ojeda.sandonis@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).