Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

.rust.o.cmd: No such file or directory #9

Closed
Skallwar opened this issue Feb 28, 2021 · 5 comments
Closed

.rust.o.cmd: No such file or directory #9

Skallwar opened this issue Feb 28, 2021 · 5 comments

Comments

@Skallwar
Copy link

Hello,

While trying to build, I get this error:
.rust.o.cmd: No such file or directory

Linux version: uname -r = 5.10.19-1-lts

@jbaublitz
Copy link
Owner

Can you please show me how you're invoking the build?

@Skallwar
Copy link
Author

Skallwar commented Mar 1, 2021

Can you please show me how you're invoking the build?

I just ran make after setting up nightly as my default toolchain

@jbaublitz
Copy link
Owner

I can't reproduce this on my system. I've been digging into out of tree kernel module builds so I'll update you with more information as I come up with it.

@joroec
Copy link

joroec commented Apr 21, 2021

There was a kernel commit (around version 5.8), not sure exactly, that changed a missing .o.cmd file from a warning to an error.
I can reproduce the error on an Ubuntu 20.04 system (kernel 5.8.0-50-generic #56~20.04.1-Ubuntu SMP Mon Apr 12 21:46:35 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux) with Rust toolchain rustc 1.53.0-nightly (6df26f897 2021-04-20).
A quick fix is to generate the empty file manually. This tells Kbuild that there are no build dependencies for this file:

touch src/.rust.o.cmd

and repeat the build with make. The build should now succeed.

Here are some more information.

Note, however, that the toolchain rustc 1.53.0-nightly (6df26f897 2021-04-20) still generates wrong relocation symbols. See this issue for more information.

@jbaublitz
Copy link
Owner

Fixed by 449c36d.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants