From: kernel test robot <lkp@intel.com>
To: "Thomas Weißschuh " <linux@weissschuh.net>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [thomas-weissschuh:b4/nolibc-rcutorture 40/40] kernel/rcu/rcutorture-init.c:3:10: fatal error: 'unistd.h' file not found
Date: Thu, 26 Mar 2026 16:22:49 +0800 [thread overview]
Message-ID: <202603261643.Ha4DqhvA-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/thomas.weissschuh/linux.git b4/nolibc-rcutorture
head: a55c66cad77542e2efcb3248af724efce7cc2d87
commit: a55c66cad77542e2efcb3248af724efce7cc2d87 [40/40] rcurorture init
config: hexagon-randconfig-001-20260326 (https://download.01.org/0day-ci/archive/20260326/202603261643.Ha4DqhvA-lkp@intel.com/config)
compiler: clang version 23.0.0git (https://github.com/llvm/llvm-project 054e11d1a17e5ba88bb1a8ef32fad3346e80b186)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260326/202603261643.Ha4DqhvA-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/202603261643.Ha4DqhvA-lkp@intel.com/
All errors (new ones prefixed by >>):
>> kernel/rcu/rcutorture-init.c:3:10: fatal error: 'unistd.h' file not found
3 | #include <unistd.h>
| ^~~~~~~~~~
1 error generated.
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for GEN_INIT_CPIO
Depends on [n]: BLK_DEV_INITRD [=n]
Selected by [y]:
- RCU_TORTURE_TEST [=y] && DEBUG_KERNEL [=y]
vim +3 kernel/rcu/rcutorture-init.c
2
> 3 #include <unistd.h>
4 #include <stdio.h>
5 #include <sys/time.h>
6
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-03-26 8:23 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=202603261643.Ha4DqhvA-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux@weissschuh.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