[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANiq72mJ75ktX_n8jxALM4cVFcwm-OKVK3e6r8+-0AYbEGHk8w@mail.gmail.com>
Date: Wed, 14 Aug 2024 13:30:47 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Matthew Maurer <mmaurer@...gle.com>
Cc: dvyukov@...gle.com, ojeda@...nel.org,
Masahiro Yamada <masahiroy@...nel.org>, Alex Gaynor <alex.gaynor@...il.com>,
Wedson Almeida Filho <wedsonaf@...il.com>, Nathan Chancellor <nathan@...nel.org>, aliceryhl@...gle.com,
samitolvanen@...gle.com, 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>,
Nick Desaulniers <ndesaulniers@...gle.com>, Bill Wendling <morbo@...gle.com>,
Justin Stitt <justinstitt@...gle.com>, linux-kbuild@...r.kernel.org,
linux-kernel@...r.kernel.org, rust-for-linux@...r.kernel.org,
llvm@...ts.linux.dev
Subject: Re: [PATCH v2 1/3] kbuild: rust: Define probing macros for rustc
On Wed, Aug 14, 2024 at 1:27 PM Miguel Ojeda
<miguel.ojeda.sandonis@...il.com> wrote:
>
> I also had `out-dir` [1] since, if I remember correctly, `rustc` may
> create temporary files in a potentially read-only location even in
> this case.
Ah, wait, you are avoiding `try-run` -- is it because of that? I think
we should try to reuse it, even if we have to add the `TMPOUT`. Or
what is the reason for not reusing it?
Cheers,
Miguel
Powered by blists - more mailing lists