mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Yang Shi" <yang.s@alibaba-inc.com>
To: dianders@chromium.org
Cc: Arnd Bergmann <arnd@arndb.de>,
	mingo@kernel.org, linux@roeck-us.net,
	yamada.masahiro@socionext.com,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: [BUG] Build error for 4.15-rc3 kernel caused by patch "kbuild: Add a cache for generated variables"
Date: Sun, 17 Dec 2017 06:35:24 +0800	[thread overview]
Message-ID: <8d9a5c09-23e2-253b-860d-7bc9d20f5317@alibaba-inc.com> (raw)

Hi folks,

I just upgraded gcc to 6.4 on my centos 7 machine by Arnd's suggestion. 
But, I ran into the below compile error with 4.15-rc3 kernel:

In file included from ./include/uapi/linux/uuid.h:21:0,
                  from ./include/linux/uuid.h:19,
                  from ./include/linux/mod_devicetable.h:12,
                  from scripts/mod/devicetable-offsets.c:2:
./include/linux/string.h:8:20: fatal error: stdarg.h: No such file or 
directory
  #include <stdarg.h>

I bisected to commit 3298b690b21cdbe6b2ae8076d9147027f396f2b1 ("kbuild: 
Add a cache for generated variables"). Once I revert this commit, kernel 
build is fine.

gcc 4.8.5 is fine to build kernel with this commit.

I'm not quite sure if this is a bug or my gcc install is skewed although 
it can build kernel without that commit since that commit might 
exacerbate the case.

Any hint is appreciated

Regards,
Yang

             reply	other threads:[~2017-12-16 22:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-16 22:35 Yang Shi [this message]
2017-12-18 14:56 ` Masahiro Yamada
2017-12-18 15:50   ` Masahiro Yamada
2017-12-18 17:17     ` Doug Anderson
2017-12-18 17:22       ` Yang Shi
2017-12-20 16:55         ` Doug Anderson
2017-12-21  3:47           ` Masahiro Yamada
2017-12-20  2:29       ` Masahiro Yamada
2017-12-20 17:07         ` Doug Anderson
2017-12-21  4:01           ` Masahiro Yamada
2017-12-22  2:18             ` Doug Anderson
2017-12-18 17:19     ` Yang Shi

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=8d9a5c09-23e2-253b-860d-7bc9d20f5317@alibaba-inc.com \
    --to=yang.s@alibaba-inc.com \
    --cc=arnd@arndb.de \
    --cc=dianders@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=mingo@kernel.org \
    --cc=yamada.masahiro@socionext.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

all inboxes | Powered by JetHome®