[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJ-ks9khX7Ha4iGWOkbHeXzJLPisE9r=+q54Z9HMQkojR=-a8Q@mail.gmail.com>
Date: Tue, 15 Oct 2024 11:05:38 -0400
From: Tamir Duberstein <tamird@...il.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
Cc: Masahiro Yamada <masahiroy@...nel.org>, Daniel Gomez <da.gomez@...sung.com>,
rust-for-linux@...r.kernel.org, Fiona Behrens <me@...enk.dev>,
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
I did more digging and I don't think this is going to be readily
fixable upstream:
see https://github.com/rust-lang/rust/issues/131720#issuecomment-2414179941.
A symlink fixes the problem if we *never* specify a path to
libmacros.so, is that how we want to proceed? Note that currently we do
specify it in one place in rust/Makefile and again in
generate_rust_analyzer.py, so those would need updates.
Tamir
Powered by blists - more mailing lists