rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Manas <manas18244@iiitd.ac.in>
Cc: rust-for-linux@vger.kernel.org
Subject: Re: Missing RUST_EXAMPLE option in linux-next-20210331
Date: Fri, 2 Apr 2021 03:19:30 +0200	[thread overview]
Message-ID: <CANiq72=heqQyTvPKopfmh+S9wFGdBECETAFNfmLjza-3rAdQFg@mail.gmail.com> (raw)
In-Reply-To: <20210402003503.exbxsfickscdvmci@nitro-5>

On Fri, Apr 2, 2021 at 2:35 AM Manas <manas18244@iiitd.ac.in> wrote:
>
> It was also not present.
>
> Nevertheless, I tweaked around a little bit and found that when I enabled
> CONFIG_COMPILE_TEST, then it removed CONFIG_RUST and RUST_EXAMPLE,
> (while HAS_RUST=y).
>
> But CONFIG_COMPILE_TEST's documentation mentions to enable it to build
> everything. This confused me at that moment.

If "Rust support" (CONFIG_RUST) was not there either, it is because
`HAS_RUST` was off, or, as you found out, if `COMPILE_TEST` is
enabled.

The reason we depend on `!COMPILE_TEST` at the moment is to prevent
Rust support from being built in `allmodconfig` builds in linux-next
as a precaution until we are given the go ahead, but this will change
in the future.

Cheers,
Miguel

  reply	other threads:[~2021-04-02  1:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-01  6:18 Missing RUST_EXAMPLE option in linux-next-20210331 Manas
2021-04-01 11:31 ` Geert Stappers
2021-04-01 11:59   ` Manas
2021-04-01 18:38     ` Geert Stappers
2021-04-01 15:07 ` Miguel Ojeda
2021-04-02  0:35   ` Manas
2021-04-02  1:19     ` Miguel Ojeda [this message]
2021-04-02  1:47       ` Manas

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='CANiq72=heqQyTvPKopfmh+S9wFGdBECETAFNfmLjza-3rAdQFg@mail.gmail.com' \
    --to=miguel.ojeda.sandonis@gmail.com \
    --cc=manas18244@iiitd.ac.in \
    --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).