From: Randy Dunlap <rdunlap@xenotime.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>, linux-kbuild@vger.kernel.org
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Michal Marek <mmarek@suse.cz>,
sam@ravnborg.org
Subject: Re: linux-next: Tree for May 2 (uml builds fail)
Date: Mon, 2 May 2011 08:19:48 -0700 [thread overview]
Message-ID: <20110502081948.1ccb9aef.rdunlap@xenotime.net> (raw)
In-Reply-To: <20110502150150.d932642f.sfr@canb.auug.org.au>
On Mon, 2 May 2011 15:01:50 +1000 Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20110429:
uml builds on i386 or x86_64 fail with: (I'm using O=outputdir if it matters)
GEN /lnx/src/NEXT/linux-next-20110502/UM64/Makefile
scripts/kconfig/conf --silentoldconfig arch/um/Kconfig.x86
GEN /lnx/src/NEXT/linux-next-20110502/UM64/Makefile
/lnx/src/NEXT/linux-next-20110502/scripts/Makefile.asm-generic:9: /lnx/src/NEXT/linux-next-20110502/arch/um/include/asm/Kbuild: No such file or directory
make[2]: *** No rule to make target `/lnx/src/NEXT/linux-next-20110502/arch/um/include/asm/Kbuild'. Stop.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-05-02 15:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-02 5:01 linux-next: Tree for May 2 Stephen Rothwell
2011-05-02 15:19 ` Randy Dunlap [this message]
2011-05-02 16:04 ` linux-next: Tree for May 2 (uml builds fail) Michal Marek
2011-05-02 16:09 ` Randy Dunlap
2011-05-02 16:52 ` Sam Ravnborg
2011-05-02 20:33 ` Michal Marek
2011-05-02 15:34 ` linux-next: Tree for May 2 (rcutiny) Randy Dunlap
2011-05-02 22:34 ` Paul E. McKenney
2011-05-02 15:37 ` linux-next: Tree for May 2 (xen) Randy Dunlap
2011-05-02 16:15 ` linux-next: Tree for May 2 (uml irqs) Randy Dunlap
2011-05-02 16:34 ` Thomas Gleixner
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=20110502081948.1ccb9aef.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=sam@ravnborg.org \
--cc=sfr@canb.auug.org.au \
/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).