From: Johannes Berg <johannes@sipsolutions.net>
To: "Liu, Yujie" <yujie.liu@intel.com>, Richard Weinberger <richard@nod.at>
Cc: lkp <lkp@intel.com>,
"oe-kbuild-all@lists.linux.dev" <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: Fri, 09 Jun 2023 09:55:27 +0200 [thread overview]
Message-ID: <075e9d3d9c63f57dc5b9006b87c62ea1aef807c2.camel@sipsolutions.net> (raw)
In-Reply-To: <ZIJ/vvquEQXN8NBf@yujie-X299>
Hi Yujie,
> > >
> > > > > 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?
>
> The bot is using the gcc-11 provided by debian distribution, so we think
> it is not a "nolibc toolchain".
>
> compiler: gcc-11 (Debian 11.3.0-8) 11.3.0
>
> We can reproduce it on commit fc54a4f15988, and its parent commit is
> clean. Please help give some guidance if anything wrong in our test
> flow. Thanks.
>
That was just a misinterpretation. The real issue was fixed by commit
73a23d771033 ("um: harddog: fix modular build").
johannes
prev parent reply other threads:[~2023-06-09 7:55 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
2023-06-09 1:26 ` Yujie Liu
2023-06-09 7:55 ` Johannes Berg [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=075e9d3d9c63f57dc5b9006b87c62ea1aef807c2.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=richard@nod.at \
--cc=yujie.liu@intel.com \
/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