rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Kaviraj Kanagaraj <kavirajkanagaraj@gmail.com>
Cc: Sumera Priyadarsini <sylphrenadin@gmail.com>,
	rust-for-linux@vger.kernel.org
Subject: Re: Build system can't detect rustc
Date: Tue, 16 Mar 2021 18:31:51 +0100	[thread overview]
Message-ID: <CANiq72md387Ce6nwaEDtqtZVSfQcHZYDg9F0f5+tiRnRhikzDw@mail.gmail.com> (raw)
In-Reply-To: <39D26FFA-1635-483F-A43F-3BCF942D0AF8@gmail.com>

On Tue, Mar 16, 2021 at 6:00 PM Kaviraj Kanagaraj
<kavirajkanagaraj@gmail.com> wrote:
>
> The thing that worked for me is to  cp .github/workflows/kernel-x86_64-release.config .config and build again.
>
> Although it would be nice to find out what is causing this when we generate config from make menuconfig (even after following the Quickstart guide)

Yes, soon we will need to sort out any issues from
{def,allyes,allmod}configs, start running them in the CI, plus run
some randconfigs etc. as usual.

For the moment, please run the included configs if you run into trouble. :-)

Cheers,
Miguel

  reply	other threads:[~2021-03-16 17:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-15  6:30 Build system can't detect rustc Sumera Priyadarsini
2021-03-15  7:27 ` Geert Stappers
2021-03-15 12:45 ` Miguel Ojeda
2021-03-16 14:10   ` Sumera Priyadarsini
2021-03-16 15:09     ` Miguel Ojeda
2021-03-16 17:00       ` Kaviraj Kanagaraj
2021-03-16 17:31         ` Miguel Ojeda [this message]
2021-03-17 10:32       ` Sumera Priyadarsini
2021-03-17 13:40         ` Miguel Ojeda
2021-03-17 18:04           ` Sumera Priyadarsini
2021-03-17 15:55     ` Miguel Ojeda
2021-03-17 22:49       ` 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=CANiq72md387Ce6nwaEDtqtZVSfQcHZYDg9F0f5+tiRnRhikzDw@mail.gmail.com \
    --to=miguel.ojeda.sandonis@gmail.com \
    --cc=kavirajkanagaraj@gmail.com \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=sylphrenadin@gmail.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;
as well as URLs for NNTP newsgroup(s).