From: Sumera Priyadarsini <sylphrenadin@gmail.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: rust-for-linux@vger.kernel.org
Subject: Re: Build system can't detect rustc
Date: Wed, 17 Mar 2021 23:34:38 +0530 [thread overview]
Message-ID: <CACAkLurXhRBUF8jFCPTwK8eXHHDtN-15Btw21FcUqOOJKifdBQ@mail.gmail.com> (raw)
In-Reply-To: <CANiq72nNJgZJ2Be4NWk8MWpxhBbCA6Ry8o88KsgzkZwGCUxNvQ@mail.gmail.com>
On Wed, Mar 17, 2021 at 7:10 PM Miguel Ojeda
<miguel.ojeda.sandonis@gmail.com> wrote:
>
> On Wed, Mar 17, 2021 at 11:32 AM Sumera Priyadarsini
> <sylphrenadin@gmail.com> wrote:
> >
> > Specifying clang did work, thanks! I used "make nconfig" but I am
> > guessing it would be the same as what 'defconfig' would have given.
> > Here is a paste if you want to take a look:
> > https://paste.ubuntu.com/p/dMb3bb34Qf/
>
> Please note that `menuconfig` (and similar commands) should be run
> with `CC=clang` as well, so that configuration is done properly for
> Clang.
>
> It would be great if you can confirm `make nconfig CC=clang` would
> have worked for you (to start from scratch, including removing the
> configuration, use `make mrproper`).
Sorry, I missed out on this- yes, I did specify CC=clang with 'make
nconfig' as well.
Without that, 'make -j4 CC=clang' started asking for config options as
expected XD
Thanks for all the help :)
Cheers,
Sumera
>
> Thanks!
>
> Cheers,
> Miguel
next prev parent reply other threads:[~2021-03-17 18:05 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
2021-03-17 10:32 ` Sumera Priyadarsini
2021-03-17 13:40 ` Miguel Ojeda
2021-03-17 18:04 ` Sumera Priyadarsini [this message]
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=CACAkLurXhRBUF8jFCPTwK8eXHHDtN-15Btw21FcUqOOJKifdBQ@mail.gmail.com \
--to=sylphrenadin@gmail.com \
--cc=miguel.ojeda.sandonis@gmail.com \
--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).