[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKwvOdndYxQ+KgVhC8F3vWnHDT8pD3px8cKjinu-khn25_FSYw@mail.gmail.com>
Date: Mon, 22 Aug 2022 13:09:00 -0700
From: Nick Desaulniers <ndesaulniers@...gle.com>
To: Miguel Ojeda <ojeda@...nel.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
rust-for-linux@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org, patches@...ts.linux.dev,
Jarkko Sakkinen <jarkko@...nel.org>,
Alex Gaynor <alex.gaynor@...il.com>,
Wedson Almeida Filho <wedsonaf@...gle.com>,
Finn Behrens <me@...enk.de>, Miguel Cano <macanroj@...il.com>,
Tiago Lam <tiagolam@...il.com>,
Boqun Feng <boqun.feng@...il.com>, Gary Guo <gary@...yguo.net>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>
Subject: Re: [PATCH v9 20/27] scripts: add `rust_is_available.sh`
On Fri, Aug 5, 2022 at 8:46 AM Miguel Ojeda <ojeda@...nel.org> wrote:
>
> This script tests whether the Rust toolchain requirements are in place
> to enable Rust support.
With this, I get:
$ make LLVM=1 rustavailable
***
*** libclang (used by the Rust bindings generator 'bindgen')
*** version does not match Clang's. This may be a problem.
*** libclang version: 15.0.0
*** Clang version: 16.0.0
***
Rust is available!
because I'm using clang built from source from ToT. Is this supposed
to mean that I can't use clang-16, clang-14, clang-13, clang-12, or
clang-11 (in the kernel we support clang-11+) in order to use rust?
I'm guessing that's going to hinder adoption. Is there a way to
specify which libclang version bindgen should be using?
I have libclang built in my clang sources,
llvm-project/llvm/build/lib/libclang.so. I also tried:
$ CLANG_PATH=/android0/llvm-project/llvm/build/lib/libclang.so.15 make
LLVM=1 -j72 rustavailable
$ CLANG_PATH=/android0/llvm-project/llvm/build/lib/libclang.so make
LLVM=1 -j72 rustavailable
--
Thanks,
~Nick Desaulniers
Powered by blists - more mailing lists