From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Nathan Chancellor <nathan@kernel.org>
Cc: llvm@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: Prebuilt LLVM 18.1.0-rc2 uploaded
Date: Tue, 13 Feb 2024 21:37:13 +0100 [thread overview]
Message-ID: <CANiq72npYCD-zKqcXPNOAxnKiUCCXGbFQaGo-8=0-171ni+ncQ@mail.gmail.com> (raw)
In-Reply-To: <20240213025303.GA4006766@dev-arch.thelio-3990X>
On Tue, Feb 13, 2024 at 3:53 AM Nathan Chancellor <nathan@kernel.org> wrote:
>
> Alright, I reuploaded 18.1.0-rc2 with libclang.so included, please let
> me know if this will work for you going forward.
Thanks Nathan, that was quick!
I tried it, and it worked like a charm. bindgen reports:
$ bindgen --version --verbose
bindgen 0.65.1
Clang: ClangBuiltLinux clang version 18.1.0rc
(https://github.com/llvm/llvm-project.git
c6c86965d967886ca5a2ed8968c949cd42cdd49a)
And I built next-20240213 for LoongArch kernel with Rust enabled:
# Linux/loongarch 6.8.0-rc4 Kernel Configuration
CONFIG_CC_VERSION_TEXT="ClangBuiltLinux clang version 18.1.0rc
(https://github.com/llvm/llvm-project.git
c6c86965d967886ca5a2ed8968c949cd42cdd49a)"
CONFIG_WERROR=y
CONFIG_RUST=y
CONFIG_RUSTC_VERSION_TEXT="rustc 1.75.0 (82e1608df 2023-12-21)"
CONFIG_BINDGEN_VERSION_TEXT="bindgen 0.65.1"
I also built our rust-next branch for x86_64 and QEMU-boot tested it
with the couple Rust samples:
[ 0.000000] Linux version 6.8.0-rc1-gf090f0d0eea9
(root@02f0b7650ba6) (ClangBuiltLinux clang version 18.1.0rc
(https://github.com/llvm/llvm-project.git
c6c86965d967886ca5a2ed8968c949cd42cdd49a), ClangBuiltLinux LLD 18.1.0)
#1 SMP PREEMPT_DYNAMIC Tue Feb 13 20:14:57 UTC 2024
[ 1.788925] rust_minimal: My numbers are [72, 108, 200]
I have hooked it up into my small CI to keep using your toolchain in a
subset of the builds :)
Not sure if you pick tags for this sort of thing, but in case it is useful:
Tested-by: Miguel Ojeda <ojeda@kernel.org>
Thanks again!
Cheers,
Miguel
next prev parent reply other threads:[~2024-02-13 20:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-08 0:28 Prebuilt LLVM 18.1.0-rc2 uploaded Nathan Chancellor
2024-02-10 16:36 ` Miguel Ojeda
2024-02-12 23:48 ` Nathan Chancellor
2024-02-13 2:53 ` Nathan Chancellor
2024-02-13 20:37 ` Miguel Ojeda [this message]
2024-02-27 12:32 ` Miguel Ojeda
2024-02-27 15:37 ` Nathan Chancellor
2024-02-27 16:51 ` Miguel Ojeda
2024-02-27 21:56 ` Nathan Chancellor
2024-02-28 18:43 ` Nathan Chancellor
2024-02-29 13:39 ` Miguel Ojeda
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CANiq72npYCD-zKqcXPNOAxnKiUCCXGbFQaGo-8=0-171ni+ncQ@mail.gmail.com' \
--to=miguel.ojeda.sandonis@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).