From: kernel test robot <lkp@intel.com>
To: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, 0day robot <lkp@intel.com>
Subject: error[E0463]: can't find crate for `syn`
Date: Wed, 23 Sep 2026 14:23:58 +0200 [thread overview]
Message-ID: <202609231457.9ssfBSKL-lkp@intel.com> (raw)
tree: https://github.com/intel-lab-lkp/linux/commits/Lorenzo-Stoakes-ARM/kbuild-do-not-allocate-modinfo-in-vmlinux/20260914-102200
head: e4c41ad4c255b1ef4323410ddd136c5beff8ee3f
commit: 799dcd195cfbecb881a8100ad7fb075179b1b030 kbuild: build rust crates in parallel with the rest of the build
date: 9 days ago
config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20260923/202609231457.9ssfBSKL-lkp@intel.com/config)
compiler: clang version 22.1.8 (https://github.com/llvm/llvm-project ca7933e47d3a3451d81e72ac174dcb5aa28b59d1)
rustc: rustc 1.96.0 (ac68faa20 2026-05-25)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260923/202609231457.9ssfBSKL-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202609231457.9ssfBSKL-lkp@intel.com/
All errors (new ones prefixed by >>):
>> error[E0463]: can't find crate for `syn`
--> rust/macros/concat_idents.rs:8:5
|
8 | use syn::{
| ^^^ can't find crate
--
>> error[E0463]: can't find crate for `syn`
--> rust/pin-init/internal/src/lib.rs:13:5
|
13 | use syn::parse_macro_input;
| ^^^ can't find crate
--
>> error[E0463]: can't find crate for `syn`
--> rust/zerocopy-derive/derive/from_bytes.rs:4:5
|
4 | use syn::{
| ^^^ can't find crate
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-09-23 12:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202609231457.9ssfBSKL-lkp@intel.com \
--to=lkp@intel.com \
--cc=ljs@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.