Skip to contentSkip to conversation

Getting Rust to work

PATCH Pavel Machek 2 participants 7 messages Mar 21, 2021 – Mar 22, 2021

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

Hi!

First try was on x86-32. It took me a whlie to figure out the problem, hence the diff below.

Next I was not sure what to do with rustup. I'm not sure if advice below is good.

Then I got failure because libclang (?) was not installed. I installed it. But I guess that should be mentioned in docs as dependency.

With CONFIG_RUST unset, kernel builds for me. With CONFIG_RUST=y + RUST_EXAMPLE=y... I get errors:

RUSTC L rust/core.o
BINDGEN rust/bindings_generated.rs
error: unknown argument: '-fmacro-prefix-map=./='
error: unknown warning option '-Wno-frame-address'; did you mean '-Wno-address'? [-Wunknown-warning-option] ./arch/x86/include/asm/bitops.h:138:9: error: 'asm goto' constructs are not supported yet ./arch/x86/include/asm/bitops.h:162:9: error: 'asm goto' constructs are not supported yet ./arch/x86/include/asm/bitops.h:201:9: error: 'asm goto' constructs are not supported yet ./include/linux/list.h:282:9: warning: duplicate 'const' declaration specifier [-Wduplicate-decl-specifier] ./include/linux/list.h:318:27: warning: duplicate 'const' declaration specifier [-Wduplicate-decl-specifier] ./include/linux/list.h:821:10: warning: duplicate 'const' declaration specifier [-Wduplicate-decl-specifier] ./include/linux/list.h:830:10: warning: duplicate 'const' declaration specifier [-Wduplicate-decl-specifier] ./arch/x86/include/asm/atomic.h:83:9: error: 'asm goto' constructs are not supported yet ./arch/x86/include/asm/atomic.h:123:9: error: 'asm goto' constructs are not supported yet ./arch/x86/include/asm/atomic.h:137:9: error: 'asm goto' constructs are not supported yet ./arch/x86/include/asm/atomic.h:152:9: error: 'asm goto' constructs are not supported yet

$ gcc --version
gcc (Debian 8.3.0-6) 8.3.0
$ rustc --version
rustc 1.52.0-nightly (61edfd591 2021-03-20)

Ideas?

Best regards,
Pavel

Documentation/rust/quick-start.rst +4 -0
index 33b5cd33ecc5..d034369b3d43 100644
@@ -16,6 +16,8 @@ Some of these requirements might be available from your Linux distribution
 under names like ``rustc``, ``rust-src``, ``rust-bindgen``, etc. However,
 at the time of writing, they are likely to not be recent enough.
 
+You need to have x86-64 or arm64 system.
+
 
 rustc
 *****
@@ -32,6 +34,8 @@ Otherwise, fetch a standalone installer or install ``rustup`` from:
 
     https://www.rust-lang.org
 
+    (if you have multiple toolchains, do rustup default nightly-i686-unknown-linux-gnu )
+
 
 Rust standard library source
 ****************************
Signature · 1 line
http://www.livejournal.com/~pavelmachek
#1 lore raw

Hi Pavel,

Quoted 3 lines · Pavel Machek

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! :-)

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.

Quoted 2 lines

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.

Quoted 2 lines

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?

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.

Cheers,
Miguel

#2 lore raw

Hi!

Quoted 4 lines
Quoted 2 lines

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 :-).

Quoted 6 lines

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.

Quoted 6 lines
Quoted 2 lines

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.

Quoted 7 lines
Quoted 2 lines

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.

Quoted 3 lines

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

Signature · 1 line
http://www.livejournal.com/~pavelmachek
#3 lore raw
Quoted 2 lines · Pavel Machek

Thanks for your work :-).

You're welcome! We're trying our best :-)

Quoted 1 line

Actually x86-32 would be useful for me. That's my test machine.

Sorry... :-( x86 32-bits, ppc64el, s390x... are some of the ones we will look into soon, but possibly after the RFC.

Quoted 2 lines

I tried, but newest in my distribution is clang-7, and kernel needs clang-10.

If you are under Debian-like distributions, these apt repos are easy to set up (we use them in the CI, in fact):

    https://apt.llvm.org/

Cheers,
Miguel

#4 lore raw
In reply to Pavel Machek
Quoted 2 lines · Pavel Machek

Done, in a private message.

I tried your config and it worked, so it looks like the problem is your old libclang (7) does not recognize some of the flags. If you can try a newer LLVM installation, it would be great to confirm it.

Nevertheless, thanks a lot for providing it -- it was useful to test it.

Cheers,
Miguel

#5 lore raw
Quoted 4 lines · Miguel Ojeda

I tried your config and it worked, so it looks like the problem is your old libclang (7) does not recognize some of the flags. If you can try a newer LLVM installation, it would be great to confirm it.

Yeah, LLVM introduced asm goto in 9.0 [1], which makes sense if you were running libclang-7.

[1] https://lists.llvm.org/pipermail/llvm-dev/2019-September/135304.html

Cheers,
Miguel