From: Richard Weinberger <richard@nod.at>
To: kernel test robot <lkp@intel.com>
Cc: Johannes Berg <johannes.berg@intel.com>,
oe-kbuild-all@lists.linux.dev, linux-mm <linux-mm@kvack.org>
Subject: Re: [linux-next:master 12780/13853] arch/um/drivers/harddog_user.c:6:10: fatal error: stdio.h: No such file or directory
Date: Mon, 24 Apr 2023 23:00:47 +0200 (CEST) [thread overview]
Message-ID: <280967570.292780.1682370047405.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <202304250419.YtCLtUhG-lkp@intel.com>
----- Ursprüngliche Mail -----
> Von: "kernel test robot" <lkp@intel.com>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> master
> head: 3b85b9b39960c08f29fa91b8d984d055dde6017e
> commit: fc54a4f15988e228cf88f888483e985c5f35031e [12780/13853] um: prevent user
> code in modules
> config: um-allmodconfig
> (https://download.01.org/0day-ci/archive/20230425/202304250419.YtCLtUhG-lkp@intel.com/config)
> compiler: gcc-11 (Debian 11.3.0-8) 11.3.0
> reproduce (this is a W=1 build):
> #
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=fc54a4f15988e228cf88f888483e985c5f35031e
> git remote add linux-next
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> git fetch --no-tags linux-next master
> git checkout fc54a4f15988e228cf88f888483e985c5f35031e
> # save the config file
> mkdir build_dir && cp config build_dir/.config
> make W=1 O=build_dir ARCH=um olddefconfig
> make W=1 O=build_dir ARCH=um SHELL=/bin/bash
>
> If you fix the issue, kindly add following tag where applicable
>| Reported-by: kernel test robot <lkp@intel.com>
>| Link: https://lore.kernel.org/oe-kbuild-all/202304250419.YtCLtUhG-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
>>> arch/um/drivers/harddog_user.c:6:10: fatal error: stdio.h: No such file or
>>> directory
> 6 | #include <stdio.h>
> | ^~~~~~~~~
> compilation terminated.
Wild guess, is this a nolibc toolchain?
Thanks,
//richard
next prev parent reply other threads:[~2023-04-24 21:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 20:53 kernel test robot
2023-04-24 21:00 ` Richard Weinberger [this message]
2023-06-09 1:26 ` Yujie Liu
2023-06-09 7:55 ` Johannes Berg
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=280967570.292780.1682370047405.JavaMail.zimbra@nod.at \
--to=richard@nod.at \
--cc=johannes.berg@intel.com \
--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