rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Stappers <stappers@stappers.nl>
To: rust-for-linux@vger.kernel.org
Subject: Re: Build system can't detect rustc
Date: Mon, 15 Mar 2021 08:27:29 +0100	[thread overview]
Message-ID: <20210315072729.irq3yciok4qyqe2l@gpm.stappers.nl> (raw)
In-Reply-To: <20210315063044.ur3lvxv7emo2egu4@adolin>

On Mon, Mar 15, 2021 at 12:00:44PM +0530, Sumera Priyadarsini wrote:
> Hi all,
> 
> I was trying to build the rust-for-linux as per the instructions here
> (https://github.com/Rust-for-Linux/linux/blob/rust/Documentation/rust/quick-start.rst)
> but CONFIG_RUST doesn't show up in General setup menu when I try to 
> setup the config file with `make nconfig`. Since it says the build
> system is supposed to be able to locate rustc, I am guessing make is
> unable to find rustc. 
> 
> Could you point me to where make is trying to find rust
> or how I can try fixing this?
> Is there anything else I might have missed out on?

State which Linux kernel source tree you are using.

The reply that is expect is a git clone URL and git branch name.


> I have the latest rust nightly installed.

Tell more about where it is installed.

The reply that is expect is a Linux distro name plus version.



Regards
Geert Stappers
First posting on this mailinglist.
Completely fine with other replies as expected.
Did not a "reply to all", did a "reply to list".
-- 
Silence is hard to parse

  reply	other threads:[~2021-03-15  7:35 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 [this message]
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
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=20210315072729.irq3yciok4qyqe2l@gpm.stappers.nl \
    --to=stappers@stappers.nl \
    --cc=rust-for-linux@vger.kernel.org \
    /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).