All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [nolibc:for-next 22/25] nolibc-test.c:12:10: fatal error: stdio.h: No such file or directory
Date: Mon, 12 Jan 2026 03:13:04 +0100	[thread overview]
Message-ID: <202601120334.gadyryQ9-lkp@intel.com> (raw)

:::::: 
:::::: Manual check reason: "low confidence bisect report"
:::::: Manual check reason: "only suspicious fbc files changed"
:::::: 

BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: "Thomas Weißschuh" <linux@weissschuh.net>

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/nolibc/linux-nolibc.git for-next
head:   a5f00be9b3b07d92c6689997403851a32e1874cc
commit: 6fe8360b16acbfb50c703f52568cad46759be2ed [22/25] selftests/nolibc: also test libc-test through regular selftest framework
:::::: branch date: 14 hours ago
:::::: commit date: 16 hours ago
config: powerpc64-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20260112/202601120334.gadyryQ9-lkp@intel.com/config)
compiler: powerpc64-linux-gcc (GCC) 15.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260112/202601120334.gadyryQ9-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/r/202601120334.gadyryQ9-lkp@intel.com/

Note: the nolibc/for-next HEAD a5f00be9b3b07d92c6689997403851a32e1874cc builds fine.
      It only hurts bisectability.

All errors (new ones prefixed by >>):

>> nolibc-test.c:12:10: fatal error: stdio.h: No such file or directory
      12 | #include <stdio.h>
         |          ^~~~~~~~~
   compilation terminated.
>> nolibc-test-linkage.c:5:10: fatal error: errno.h: No such file or directory
       5 | #include <errno.h>
         |          ^~~~~~~~~
   compilation terminated.

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

                 reply	other threads:[~2026-01-12  2:13 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=202601120334.gadyryQ9-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=oe-kbuild@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.