From: Randy Dunlap <rdunlap@infradead.org>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Richard Weinberger <richard@nod.at>,
linux-um@lists.infradead.org, LKML <linux-kernel@vger.kernel.org>,
linux-kbuild <linux-kbuild@vger.kernel.org>
Subject: Re: kbuild: ARCH=um archheaders failed
Date: Sat, 4 Aug 2018 08:47:20 -0700 [thread overview]
Message-ID: <29f9908d-06e5-8e88-4433-9bd7935a0d1f@infradead.org> (raw)
In-Reply-To: <CAK7LNARdoeKCNYV7Kp6YLNsJ4rjrjXRWMsf4op58-JzRYUNVtg@mail.gmail.com>
On 08/03/2018 07:23 PM, Masahiro Yamada wrote:
> 2018-08-04 0:41 GMT+09:00 Randy Dunlap <rdunlap@infradead.org>:
>> On 08/02/2018 05:13 PM, Randy Dunlap wrote:
>>> Hi Yamada-san,
>>>
>>> I see this every few weeks. It's not reproducible (it depends
>>> on the moon, Mars, etc.).
>>>
>>> I'm using O=builddir. The build log is short (below).
>>>
>>> Do you see a makefile problem here? (nothing to do with mmotm;
>>> I see it more frequently with linux-next since I do many daily
>>> builds with it)
>>
>> BTW, this is just um defconfig with -j4.
>>
>> --
>> ~Randy
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
> I will send a patch with commit description later
> after more testing,
> but the following patch should fix the issue.
>
>
> diff --git a/arch/um/Makefile b/arch/um/Makefile
> index d3975e7..1cec053 100644
> --- a/arch/um/Makefile
> +++ b/arch/um/Makefile
> @@ -120,7 +120,7 @@ archheaders:
> $(Q)$(MAKE) -f $(srctree)/scripts/Makefile.asm-generic \
> kbuild-file=$(HOST_DIR)/include/uapi/asm/Kbuild \
> obj=$(HOST_DIR)/include/generated/uapi/asm
> - $(Q)$(MAKE) KBUILD_SRC= ARCH=$(HEADER_ARCH) archheaders
> + $(Q)$(MAKE) -f $(srctree)/Makefile ARCH=$(HEADER_ARCH) archheaders
>
>
> archprepare: include/generated/user_constants.h
>
>
>
I tested this patch and it works. :)
but then it's difficult to reproduce the problem.
Thanks!
--
~Randy
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
prev parent reply other threads:[~2018-08-04 15:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-03 0:13 kbuild: ARCH=um archheaders failed Randy Dunlap
2018-08-03 15:41 ` Randy Dunlap
2018-08-04 2:23 ` Masahiro Yamada
2018-08-04 15:47 ` Randy Dunlap [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=29f9908d-06e5-8e88-4433-9bd7935a0d1f@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=richard@nod.at \
--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;
as well as URLs for NNTP newsgroup(s).