Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Janne Grunau <j@jannau.net>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [asahilinux:bits/250-aop 28/79] error: cannot find macro `vec` in this scope
Date: Fri, 28 Aug 2026 12:17:07 +0800	[thread overview]
Message-ID: <202608281210.zhnKMxsR-lkp@intel.com> (raw)

tree:   https://github.com/AsahiLinux/linux bits/250-aop
head:   e793b14f66e33b70363166d84886d82d462f1987
commit: ade253cc58e6089f3650bc816b34863e60d3ca13 [28/79] rust: alloc: vec: Add TryFrom trait
config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20260828/202608281210.zhnKMxsR-lkp@intel.com/config)
compiler: clang version 22.1.3 (https://github.com/llvm/llvm-project e9846648fd6183ee6d8cbdb4502213fcf902a211)
rustc: rustc 1.96.0 (ac68faa20 2026-05-25)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260828/202608281210.zhnKMxsR-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/202608281210.zhnKMxsR-lkp@intel.com/

All errors (new ones prefixed by >>):

>> error: cannot find macro `vec` in this scope
   --> rust/doctests_kernel_generated.rs:1744:19
   |
   1744 | assert_eq!(r, Err(vec![0, 1, 2, 3, 4, 5, 6, 7, 8, 9]));
   |                   ^^^
--
>> error: cannot find macro `vec` in this scope
   --> rust/doctests_kernel_generated.rs:1691:12
   |
   1691 | assert_eq!(vec![1, 2, 3].try_into(), Ok([1, 2, 3]));
   |            ^^^
--
>> error[E0107]: struct takes 2 generic arguments but 1 generic argument was supplied
   --> rust/doctests_kernel_generated.rs:1692:13
   |
   1692 | assert_eq!(<Vec<i32>>::new().try_into(), Ok([]));
   |             ^^^ --- supplied 1 generic argument
   |             |
   |             expected 2 generic arguments
   |
   note: struct defined here, with 2 generic parameters: `T`, `A`
   --> rust/kernel/alloc/kvec.rs:130:12
   |
   130 | pub struct Vec<T, A: Allocator> {
   |            ^^^ -  -
   help: add missing generic argument
   |
   1692 | assert_eq!(<Vec<i32, A>>::new().try_into(), Ok([]));
   |                    +++
--
>> error[E0107]: struct takes 2 generic arguments but 1 generic argument was supplied
   --> rust/doctests_kernel_generated.rs:1743:48
   |
   1743 | let r: Result<[i32; 4], _> = (0..10).collect::<Vec<_>>().try_into();
   |                                                ^^^ - supplied 1 generic argument
   |                                                |
   |                                                expected 2 generic arguments
   |
   note: struct defined here, with 2 generic parameters: `T`, `A`
   --> rust/kernel/alloc/kvec.rs:130:12
   |
   130 | pub struct Vec<T, A: Allocator> {
   |            ^^^ -  -
   help: add missing generic argument
   |
   1743 | let r: Result<[i32; 4], _> = (0..10).collect::<Vec<_, _>>().try_into();
   |                                                     +++
--
>> error[E0433]: cannot find type `String` in this scope
   --> rust/doctests_kernel_generated.rs:1795:13
   |
   1795 | let mut v = String::from("hello world").into_bytes();
   |             ^^^^^^ use of undeclared type `String`

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2026-08-28  4:17 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=202608281210.zhnKMxsR-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=j@jannau.net \
    --cc=llvm@lists.linux.dev \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox