From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: Kees Cook <keescook@chromium.org>
Cc: Jeff Dike <jdike@addtoit.com>,
Richard Weinberger <richard@nod.at>,
linux-um@lists.infradead.org,
Randy Dunlap <rdunlap@infradead.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Michal Marek <michal.lkml@markovi.net>,
Sam Ravnborg <sam@ravnborg.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] um: fix parallel building with O= option
Date: Tue, 18 Sep 2018 13:01:48 +0900 [thread overview]
Message-ID: <CAK7LNASW+cKjoUGpTvBwf-4J38VhF0AMpNBX1Tny_2mguLBmaw@mail.gmail.com> (raw)
In-Reply-To: <CAGXu5jK4aNuZ+RR4eC80yUQ2zxSoU9=ioaJBtt=VaX=_oZC=ew@mail.gmail.com>
Hi Kees,
2018-09-16 3:47 GMT+09:00 Kees Cook <keescook@chromium.org>:
> On Fri, Aug 3, 2018 at 9:47 PM, Masahiro Yamada
> <yamada.masahiro@socionext.com> wrote:
>> Randy Dunlap reports UML occasionally fails to build with -j<N> and
>> O=<builddir> options.
>
> With v4.19-rc2 I'm still seeing a failure (for any parallelism) under ARCH=um
>
> $ make -j8 ARCH=um O=/tmp/foo
> ...
> /home/kees/src/linux-build/um/Makefile:1185: *** Headers not
> exportable for the um architecture. Stop.
>
> Am I missing something?
This is a different problem.
I sent a patch:
https://patchwork.kernel.org/patch/10603707/
--
Best Regards
Masahiro Yamada
next prev parent reply other threads:[~2018-09-18 4:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-04 4:47 [PATCH 0/3] Kbuild: fix and clean-up arch/um/Makefile Masahiro Yamada
2018-08-04 4:47 ` [PATCH 1/3] um: fix parallel building with O= option Masahiro Yamada
2018-08-04 4:51 ` Masahiro Yamada
2018-09-15 18:47 ` Kees Cook
2018-09-18 4:01 ` Masahiro Yamada [this message]
2018-08-04 4:47 ` [PATCH 2/3] kbuild: add %asm-generic to no-dot-config-targets Masahiro Yamada
2018-08-04 4:47 ` [PATCH 3/3] um: clean up archheaders recipe Masahiro Yamada
2018-08-05 0:58 ` [PATCH 0/3] Kbuild: fix and clean-up arch/um/Makefile Randy Dunlap
2018-08-06 20:54 ` Richard Weinberger
2018-08-08 1:24 ` Masahiro Yamada
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=CAK7LNASW+cKjoUGpTvBwf-4J38VhF0AMpNBX1Tny_2mguLBmaw@mail.gmail.com \
--to=yamada.masahiro@socionext.com \
--cc=geert@linux-m68k.org \
--cc=jdike@addtoit.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=michal.lkml@markovi.net \
--cc=rdunlap@infradead.org \
--cc=richard@nod.at \
--cc=sam@ravnborg.org \
/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).