From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@rothwell.id.au>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
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 20:03:08 -0700 [thread overview]
Message-ID: <8ed74a96-7309-3370-4b8b-376bface7cc6@infradead.org> (raw)
In-Reply-To: <56341950-abd6-8a9c-42ca-7eb91c55cc90@infradead.org>
On 7/12/21 6:43 PM, Randy Dunlap wrote:
> On 7/12/21 6:10 PM, Stephen Rothwell wrote:
>> Hi Randy,
>>
>> On Mon, 12 Jul 2021 08:24:16 -0700 Randy Dunlap <rdunlap@infradead.org> wrote:
>>>
>>> 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.
>>
>> OK, this is weird. init/Kconfig has not changed from Friday and I
>> don't see these errors at all in my builds. I also have no rust
>> compiler installed. And the kernel ci bot seems happy (well nothing
>> like this anyway).
>>
>
> Hm, OK, I'll check for patch/merge problems (since I am using
> tarballs and patches).
I'm still checking. I see a bunch of build errors in 2021-07-12 but
they could just be source tree problems -- I don't have much confidence
in them. I'll hope for better results tomorrow (07-13) but see if I
can determine what is going on here.
thanks.
--
~Randy
next prev parent reply other threads:[~2021-07-13 3:03 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 ` linux-next: Tree for Jul 12 (no Rust) Randy Dunlap
2021-07-13 1:10 ` Stephen Rothwell
2021-07-13 1:43 ` Randy Dunlap
2021-07-13 3:03 ` Randy Dunlap [this message]
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=8ed74a96-7309-3370-4b8b-376bface7cc6@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 \
--cc=sfr@rothwell.id.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).