From: Masahiro Yamada <masahiroy@kernel.org>
To: qwer trump <vivazsj@gmail.com>
Cc: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
linux-kbuild@vger.kernel.org,
rust-for-linux <rust-for-linux@vger.kernel.org>
Subject: Re: Problem with rust module
Date: Mon, 29 Apr 2024 23:56:41 +0900 [thread overview]
Message-ID: <CAK7LNATt14bK+Fb0AKtVMZb9KoZsuCYJAnZsZmy4A_8NUvXGvg@mail.gmail.com> (raw)
In-Reply-To: <CANcniXtiRnNjcFCwfJpUrnnheep1ZC8yPuCsC6WJSWHgtHQa+w@mail.gmail.com>
On Sun, Apr 28, 2024 at 10:01 AM qwer trump <vivazsj@gmail.com> wrote:
>
> Hi，Miguel
> Thanks for your reply. I really have this config enabled.
Then, you were attempting to build the rust module
with CONFIG_RUST disabled.
RUST depends on !MODVERSIONS.
>
> Best Regards
>
> Miguel Ojeda <miguel.ojeda.sandonis@gmail.com> 于2024年4月26日周五 19:26写道：
> >
> > On Fri, Apr 26, 2024 at 11:46 AM qwer trump <vivazsj@gmail.com> wrote:
> > >
> > > ERROR: modpost: too long symbol
> > > "_RNvNtNtCschHAZg3Q02y_6kernel5print14format_strings4INFO"
> > > [/linux-rust/samples/rust/rust_minimal.ko]
> > >
> > > But I see there are many long symbols in Module.symvers. So I guess there's
> > > something wrong with modpost.
> >
> > This shows up with `CONFIG_MODVERSIONS=y`, but you should not be able
> > to enable the Rust support if you have that enabled (until it gets
> > resolved, see [1][2]).
> >
> > Do you have `CONFIG_MODVERSIONS` enabled?
> >
> > Thanks!
> >
> > Cheers,
> > Miguel
> >
> > [1] https://lore.kernel.org/rust-for-linux/20230111161155.1349375-1-gary@garyguo.net/
> > [2] https://lore.kernel.org/rust-for-linux/20231115185858.2110875-1-mmaurer@google.com/
>
--
Best Regards
Masahiro Yamada
prev parent reply other threads:[~2024-04-29 14:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 9:45 Problem with rust module qwer trump
2024-04-26 11:25 ` Miguel Ojeda
2024-04-28 1:00 ` qwer trump
2024-04-29 14:56 ` Masahiro Yamada [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=CAK7LNATt14bK+Fb0AKtVMZb9KoZsuCYJAnZsZmy4A_8NUvXGvg@mail.gmail.com \
--to=masahiroy@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=vivazsj@gmail.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).