From: Pasha Tatashin <pasha.tatashin@soleen.com>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [akpm-mm:mm-nonmm-unstable 86/104] liveupdate.c:21:10: fatal error: errno.h: No such file or directory
Date: Sun, 23 Nov 2025 12:57:15 -0500 [thread overview]
Message-ID: <CA+CK2bAsNp2j=U4o9pAfC87TSE+1sPRA4Gd6AjCUW2ZGKffTgw@mail.gmail.com> (raw)
In-Reply-To: <aSKvbLiFT0aParmU@rli9-mobl>
> Note: the akpm-mm/mm-nonmm-unstable HEAD 5b8dc8b45ebd9e7f3fea3adefeccd9ce94215103 builds fine.
> It only hurts bisectability.
>
> All errors (new ones prefixed by >>):
>
> >> liveupdate.c:21:10: fatal error: errno.h: No such file or directory
> 21 | #include <errno.h>
> | ^~~~~~~~~
> compilation terminated.
I am not sure what needs to be done here. I have tried to reproduce
this, and every single other selftest that includes standard libraries
(most of them) spits out exactly the same error.
Pasha
prev parent reply other threads:[~2025-11-23 17:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-23 6:53 kernel test robot
2025-11-23 17:57 ` Pasha Tatashin [this message]
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='CA+CK2bAsNp2j=U4o9pAfC87TSE+1sPRA4Gd6AjCUW2ZGKffTgw@mail.gmail.com' \
--to=pasha.tatashin@soleen.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--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