linux-kernel - Re: [PATCH] rust: query the compiler for dylib path

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CANiq72n+mWOP3xNUU4Mep-n5QtJ8zQiwP9JZ-KX68+fOC0GMmw@mail.gmail.com>
Date: Sat, 12 Oct 2024 15:41:03 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Daniel Gomez <da.gomez@...sung.com>
Cc: Tamir Duberstein <tamird@...il.com>, rust-for-linux@...r.kernel.org, 
	Fiona Behrens <me@...enk.dev>, Masahiro Yamada <masahiroy@...nel.org>, 
	Nathan Chancellor <nathan@...nel.org>, Nicolas Schier <nicolas@...sle.eu>, Miguel Ojeda <ojeda@...nel.org>, 
	Alex Gaynor <alex.gaynor@...il.com>, 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@...nel.org>, 
	Alice Ryhl <aliceryhl@...gle.com>, Trevor Gross <tmgross@...ch.edu>, 
	"David S. Miller" <davem@...emloft.net>, Kris Van Hees <kris.van.hees@...cle.com>, 
	Íñigo Huguet <ihuguet@...hat.com>, 
	Thomas Weißschuh <linux@...ssschuh.net>, 
	Vegard Nossum <vegard.nossum@...cle.com>, 
	Laurent Pinchart <laurent.pinchart@...asonboard.com>, linux-kernel@...r.kernel.org, 
	linux-kbuild@...r.kernel.org
Subject: Re: [PATCH] rust: query the compiler for dylib path

On Thu, Oct 10, 2024 at 10:31 AM Daniel Gomez <da.gomez@...sung.com> wrote:
>
> Building Linux in macOS is now supported for arm64 (targets tested: allyesconfig
> and defconfig). The upstream policy is to use the build system variables to
> configure the necessary tweaks to support building in macOS. However, this
> will not always be possible then, patches are welcome from the build system
> maintainer to support "portability" across OSes. But not full integration.
> Please, let me know if this is not clear.

Thanks for writing this -- it seems similar to the summary you wrote
elsewhere, but it does confirm we should probably be using build
variables instead (i.e. I don't think the overall macOS support
questions are answered, but we don't need to answer them here).

In other words, it sounds to me like the solution here is to simply
provide a variable with the current name as the default, and let
out-of-tree override that if they need, rather than query `rustc`.

Thus upstream can keep the variable working very easily, and
out-of-tree can maintain/test the overall macOS support.

Does that sound reasonable for everyone?

Cheers,
Miguel