From: Pavel Machek <pavel@ucw.cz>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: Miguel Ojeda <ojeda@kernel.org>,
Alex Gaynor <alex.gaynor@gmail.com>,
rust-for-linux@vger.kernel.org,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Getting Rust to work
Date: Sun, 21 Mar 2021 21:56:19 +0100 [thread overview]
Message-ID: <20210321205619.GB28813@duo.ucw.cz> (raw)
In-Reply-To: <CANiq72n=XNwH8JrPfpzTMrHujhCYVzk5BgVmifiVcTk3W_=L2A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1650 bytes --]
Hi!
> > First try was on x86-32. It took me a whlie to figure out the problem,
> > hence the diff below.
>
> Thanks a lot for trying it out and for the feedback! :-)
Thanks for your work :-).
> The supported architectures are in
> Documentation/rust/arch-support.rst, so we should link to that.
>
> x86 32-bit and other architectures should eventually work -- we need
> to put some time into them and setting up a few things. For the moment
> we focused on x86_64 and arm64.
Actually x86-32 would be useful for me. That's my test machine.
> > Then I got failure because libclang (?) was not installed. I installed
> > it. But I guess that should be mentioned in docs as dependency.
>
> Yeah, this is mentioned on the bindgen section in quick-start.rst, I
> will try to improve make it more clear, perhaps I'll a section for
> libclang itself.
Aha, sorry, it is possible I was not careful enough reading the docs.
> > With CONFIG_RUST unset, kernel builds for me. With CONFIG_RUST=y +
> > RUST_EXAMPLE=y... I get errors:
>
> Typically it is due to a kernel option that enables some GCC flag that
> libclang does not know about -- I have a hack in place to make it
> work, but requires manual maintenance. Can you please attach your
> kernel config?
Done, in a private message.
> Meanwhile, please try building with Clang or LLVM instead, the GCC
> builds are very, very experimental. I'll make it even more explicit in
> the quick-start.
I tried, but newest in my distribution is clang-7, and kernel needs
clang-10.
Best regards,
Pavel
--
http://www.livejournal.com/~pavelmachek
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2021-03-21 20:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-21 19:37 Getting Rust to work Pavel Machek
2021-03-21 20:03 ` Miguel Ojeda
2021-03-21 20:56 ` Pavel Machek [this message]
2021-03-21 21:26 ` Miguel Ojeda
2021-03-21 21:58 ` Miguel Ojeda
2021-03-21 22:05 ` Miguel Ojeda
2021-03-22 2:34 ` 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=20210321205619.GB28813@duo.ucw.cz \
--to=pavel@ucw.cz \
--cc=alex.gaynor@gmail.com \
--cc=linux-kernel@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).