From: Alice Ryhl <aliceryhl@google.com>
To: Steven Rostedt <rostedt@goodmis.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
rust-for-linux <rust-for-linux@vger.kernel.org>,
Miguel Ojeda <ojeda@kernel.org>
Subject: Re: linux-next: build failure after merge of the ftrace tree
Date: Fri, 8 Nov 2024 16:09:33 +0100 [thread overview]
Message-ID: <CAH5fLgj6zSDH6Oe3oqfE7F+NQSgSLxh8x7X3ewrrDAdOHOh0YA@mail.gmail.com> (raw)
In-Reply-To: <20241108095933.72400ee1@gandalf.local.home>
On Fri, Nov 8, 2024 at 3:59 PM Steven Rostedt <rostedt@goodmis.org> wrote:
>
> On Fri, 8 Nov 2024 15:21:49 +1100
> Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> > Hi all,
> >
> > After merging the ftrace tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> >
> > ERROR: modpost: missing MODULE_LICENSE() in samples/rust/rust_print_events.o
> > ERROR: modpost: "__tracepoint_rust_sample_loaded" [samples/rust/rust_print.ko] undefined!
> > ERROR: modpost: "rust_do_trace_rust_sample_loaded" [samples/rust/rust_print.ko] undefined!
> >
> > Caused by commit
> >
> > 91d39024e1b0 ("rust: samples: add tracepoint to Rust sample")
>
> Alice,
>
> Can you send a patch to fix this?
I'm working on it as we speak, but I haven't figured out how to
reproduce the problem yet. Using allmodconfig builds fine for me. Any
ideas?
Stephen, is there any more information you can share about this? What
versions of rustc, bindgen, and clang are you using?
Alice
next parent reply other threads:[~2024-11-08 15:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241108152149.28459a72@canb.auug.org.au>
[not found] ` <20241108095933.72400ee1@gandalf.local.home>
2024-11-08 15:09 ` Alice Ryhl [this message]
2024-11-08 20:35 ` linux-next: build failure after merge of the ftrace tree Steven Rostedt
2024-11-08 21:05 ` Miguel Ojeda
2024-11-08 21:53 ` Miguel Ojeda
2024-11-09 11:09 ` Steven Rostedt
2024-11-09 11:55 ` Miguel Ojeda
2024-11-09 13:03 ` Steven Rostedt
2024-11-09 16:57 ` Miguel Ojeda
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=CAH5fLgj6zSDH6Oe3oqfE7F+NQSgSLxh8x7X3ewrrDAdOHOh0YA@mail.gmail.com \
--to=aliceryhl@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=ojeda@kernel.org \
--cc=rostedt@goodmis.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).