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>,
Masahiro Yamada <masahiroy@kernel.org>,
Miguel Ojeda <ojeda@kernel.org>
Subject: Re: linux-next: Tree for Jul 12 (no Rust)
Date: Mon, 12 Jul 2021 08:24:16 -0700 [thread overview]
Message-ID: <c47a7f0b-4b5a-30c3-ee1e-2973793a9534@infradead.org> (raw)
In-Reply-To: <20210712120828.5c480cdc@canb.auug.org.au>
On 7/11/21 7:08 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20210709:
>
> The rust tree gained a conflict against Linus' tree.
>
I am getting no builds completing. I see this:
Error: No compiler specified.
Usage:
../scripts/rust-version.sh <rust-command>
init/Kconfig:71: syntax error
init/Kconfig:70: invalid statement
and then 'bc' running continuously until I kill it.
Since I don't have any Rust compiler or tools installed,
this fixes the build problems for me for now:
---
init/Kconfig | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- linux-next-20210712.orig/init/Kconfig
+++ linux-next-20210712/init/Kconfig
@@ -62,12 +62,12 @@ config LLD_VERSION
config HAS_RUST
depends on ARM64 || CPU_32v6 || CPU_32v6K || (PPC64 && CPU_LITTLE_ENDIAN) || X86_64 || RISCV
- def_bool $(success,$(RUSTC) --version)
+ def_bool false
config RUSTC_VERSION
depends on HAS_RUST
int
- default $(shell,$(srctree)/scripts/rust-version.sh $(RUSTC))
+ default 0
config CC_CAN_LINK
bool
next prev parent reply other threads:[~2021-07-12 15:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-12 2:08 linux-next: Tree for Jul 12 Stephen Rothwell
2021-07-12 15:24 ` Randy Dunlap [this message]
2021-07-13 1:10 ` linux-next: Tree for Jul 12 (no Rust) Stephen Rothwell
2021-07-13 1:43 ` Randy Dunlap
2021-07-13 3:03 ` Randy Dunlap
2021-07-13 3:31 ` Randy Dunlap
2021-07-13 17:36 ` Miguel Ojeda
2021-07-13 20:20 ` Randy Dunlap
2021-07-13 20:31 ` Miguel Ojeda
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=c47a7f0b-4b5a-30c3-ee1e-2973793a9534@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=ojeda@kernel.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).