Compilation error: can't find crate for `std`; the `x86_64-linux-kernel` target may not be installed

[rust-for-linux]

Compilation error: can't find crate for `std`; the `x86_64-linux-kernel` target may not be installed

[kloenk]

This should resolve itself, when #25 gets resolved.

[wecing]

@kloenk Is it possible to workaround this issue before #25 lands?

[ojeda]

@wecing It may work now since we don't depend on shlex anymore and we use our own target. I also rewrote the quick start guide a bit, in case you want to take a look.

[wecing]

@ojeda Thank you! Unfortunately it still doesn't work for me:

> git log -1
commit 514443c678e50021917dfe5b9e4a427559e9ec82 (HEAD -> rust, origin/rust, origin/HEAD)
Merge: 2874653450f 5c3df5ae897
Author: Miguel Ojeda
Date:   Sun Nov 29 00:03:27 2020 +0100

    Merge pull request #37 from Rust-for-Linux/rust-ci-builddir

    CI: test O= builds too
> make menuconfig
> make clean
> make LLVM=1
  ...
  CALL    scripts/checksyscalls.sh
  CALL    scripts/atomic/check-atomics.sh
  DESCEND  objtool
  CHK     include/generated/compile.h
  CARGO     arch/x86/entry/vdso/libvdso-image.a
error: manifest path `./arch/x86/entry/vdso/Cargo.toml` does not exist
make[3]: *** [scripts/Makefile.build:329: arch/x86/entry/vdso/libvdso-image.a] Error 101
make[2]: *** [scripts/Makefile.build:529: arch/x86/entry/vdso] Error 2
make[1]: *** [scripts/Makefile.build:529: arch/x86/entry] Error 2
make: *** [Makefile:1833: arch/x86] Error 2

Since the previous error message I saw was about rust std, I actually did try to compile that from latest rust source code:

> ./x.py build --stage 1 --host x86_64-unknown-linux-gnu --target x86_64-linux-kernel library/std
Assembling stage1 compiler (x86_64-unknown-linux-gnu)
Building stage1 std artifacts (x86_64-unknown-linux-gnu -> x86_64-linux-kernel)
   Compiling libc v0.2.79
   ...
   Compiling object v0.22.0
   Compiling addr2line v0.14.0
   Compiling std v0.0.0 (/home/$USER/Code/sources/rust/library/std)
warning: dropping unsupported crate type `dylib` for target `x86_64-linux-kernel`

error[E0432]: unresolved imports `libc::c_int`, `libc::c_void`
  --> library/std/src/sys_common/net.rs:17:12
   |
17 | use libc::{c_int, c_void};
   |            ^^^^^  ^^^^^^ no `c_void` in the root
   |            |
   |            no `c_int` in the root

Not sure what was causing that failure, but it probably doesn't matter anymore.

[ojeda]

@wecing Thanks for trying again!

CARGO arch/x86/entry/vdso/libvdso-image.a

@kloenk This is triggered by the $(obj)/lib%.a change, now it matches things we don't want.

[kloenk]

@kloenk This is triggered by the $(obj)/lib%.a change, now it matches things we don't want.

Oh, not good. But without that change it also does not work. So no idea on how to fix it from my side at this time.

I changed it so, it detects if it's a module or a builtin.