mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Masahiro Yamada <yamada.masahiro@socionext.com>,
	linux-kbuild <linux-kbuild@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Cc: Richard Weinberger <richard@nod.at>, linux-um@lists.infradead.org
Subject: kbuild: ARCH=um archheaders failed
Date: Thu, 2 Aug 2018 17:13:59 -0700	[thread overview]
Message-ID: <be4f41de-c27a-abac-4b23-369c400e016e@infradead.org> (raw)

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)


thanks.
-- 
make[1]: Entering directory '/home/rdunlap/mmotm-2018-0802-1529/UM64'
  UPD     include/generated/uapi/linux/version.h
  WRAP    arch/x86/include/generated/asm/dma-contiguous.h
  WRAP    arch/x86/include/generated/asm/export.h
  WRAP    arch/x86/include/generated/asm/early_ioremap.h
  WRAP    arch/x86/include/generated/asm/mcs_spinlock.h
  WRAP    arch/x86/include/generated/asm/mm-arch-hooks.h
  WRAP    arch/x86/include/generated/uapi/asm/bpf_perf_event.h
  WRAP    arch/x86/include/generated/uapi/asm/poll.h
  GEN     ./Makefile
make[2]: *** No rule to make target 'archheaders'.  Stop.
arch/um/Makefile:119: recipe for target 'archheaders' failed
make[1]: *** [archheaders] Error 2
make[1]: *** Waiting for unfinished jobs....
  UPD     include/config/kernel.release
make[1]: *** wait: No child processes.  Stop.
Makefile:146: recipe for target 'sub-make' failed
make: *** [sub-make] Error 2


             reply	other threads:[~2018-08-03  0:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-03  0:13 Randy Dunlap [this message]
2018-08-03 15:41 ` Randy Dunlap
2018-08-04  2:23   ` Masahiro Yamada
2018-08-04 15:47     ` Randy Dunlap

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=be4f41de-c27a-abac-4b23-369c400e016e@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

all inboxes | Powered by JetHome®