[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANiq72nNTc+XLBZxcSBD9beZ+OocEEYQcNOM_e7Be55LuJ1M4A@mail.gmail.com>
Date: Sun, 12 Jan 2025 19:32:39 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Andreas Hindborg <a.hindborg@...nel.org>
Cc: Masahiro Yamada <masahiroy@...nel.org>, Miguel Ojeda <ojeda@...nel.org>,
Wedson Almeida Filho <wedsonaf@...il.com>, Alex Gaynor <alex.gaynor@...il.com>,
Nathan Chancellor <nathan@...nel.org>, Nicolas Schier <nicolas@...sle.eu>, Boqun Feng <boqun.feng@...il.com>,
Gary Guo <gary@...yguo.net>, Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Benno Lossin <benno.lossin@...ton.me>, Andreas Hindborg <a.hindborg@...sung.com>,
Alice Ryhl <aliceryhl@...gle.com>, linux-kbuild@...r.kernel.org,
rust-for-linux@...r.kernel.org, linux-kernel@...r.kernel.org,
patches@...ts.linux.dev
Subject: Re: [PATCH 2/3] kbuild: rust: apply `CONFIG_WERROR` to all Rust targets
On Fri, Jan 10, 2025 at 2:33 PM Andreas Hindborg <a.hindborg@...nel.org> wrote:
>
> @Miguel: Should I look into exempting host programs, or do you already
> have an idea of how to implement?
I will send a v2. I may take the chance to already apply the first
patch into `rust-next`, since that could go in already.
> Regarding host programs, it would be nice to set werror for those. How
> does C do this? Is W=e enough?
Neither `CONFIG_WERROR` nor `W=e` apply to C host programs.
However, you may already do:
make ... HOSTCFLAGS=-Werror
And for Rust:
make ... HOSTRUSTFLAGS=-Dwarnings
I could perhaps add that into the docs.
I hope that helps, and thanks for the tags!
Cheers,
Miguel
Powered by blists - more mailing lists