From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
"linux-um@lists.infradead.org" <linux-um@lists.infradead.org>
Subject: Re: linux-next: Tree for Oct 18 ('make' error on ARCH=um)
Date: Mon, 18 Oct 2021 14:14:59 -0700 [thread overview]
Message-ID: <a1b2bdda-d1cf-807b-6a84-73a3e347639c@infradead.org> (raw)
In-Reply-To: <20211018203023.036d8362@canb.auug.org.au>
On 10/18/21 2:30 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20211015:
>
UML (arch=um) with SUBARCH of i386 or x86_64,
using gcc, not clang:
make[1]: Entering directory '/work/lnx/next/linux-next-20211018/UM64'
../scripts/Makefile.clang:19: *** Specify CROSS_COMPILE or add '--target=' option to scripts/Makefile.clang. Stop.
make[1]: Leaving directory '/work/lnx/next/linux-next-20211018/UM64'
make: *** [Makefile:226: __sub-make] Error 2
Just use a make target of defconfig:
make ARCH=um SUBARCH=x86_64 O=UM64 defconfig
--
~Randy
next prev parent reply other threads:[~2021-10-18 21:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-18 9:30 linux-next: Tree for Oct 18 Stephen Rothwell
2021-10-18 21:14 ` Randy Dunlap [this message]
2021-10-18 21:58 ` linux-next: Tree for Oct 18 ('make' error on ARCH=um) Stephen Rothwell
2021-10-18 22:18 ` Miguel Ojeda
2021-10-20 4:56 ` Stephen Rothwell
2021-10-20 14:23 ` Randy Dunlap
2021-10-20 14:46 ` Randy Dunlap
2021-10-20 14:48 ` Miguel Ojeda
2021-10-20 20:59 ` Stephen Rothwell
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=a1b2bdda-d1cf-807b-6a84-73a3e347639c@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-um@lists.infradead.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).