Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: "Benhur T" <benhur.tessele@est.tech>,
	<openembedded-core@lists.openembedded.org>
Cc: "Randy MacLeod" <Randy.MacLeod@windriver.com>
Subject: Re: [OE-core] [PATCH 0/2] rust: add rust-analyzer support
Date: Thu, 01 Oct 2026 16:08:08 +0200	[thread overview]
Message-ID: <DLTK70W1LZPD.1WPEJTEXRP8Q1@bootlin.com> (raw)
In-Reply-To: <20261001125630.760962-1-benhur.tessele@est.tech>

On Thu Oct 1, 2026 at 2:56 PM CEST, Benhur T wrote:
> rust-analyzer is built as part of the Rust tools but was neither
> installed nor packaged. This series packages it and wires it into the
> Rust SDK next to clippy and rustfmt.
>
> Patch 1 adds a rust-tools-analyzer package for the target and nativesdk
> variants. Beyond the frontend binary it also ships the proc-macro server
> and depends on the standard library sources, both of which are required
> for rust-analyzer to actually function.
>
> Patch 2 adds it to the cross-canadian toolchain so that an SDK built with
> SDK_FEATURES = "rust" provides rust-analyzer out of the box.
>
> Testing:
>  - Patches validated with patchset.
>  - Built an SDK with SDK_FEATURES = "rust", installed it in a container,
>    and confirmed rust-analyzer resolves the standard library and expands
>    proc-macros end to end: diagnostics/analysis-stats on a crate using a
>    derive macro succeed, with the proc-macro server started from
>    <sysroot>/libexec.
>  - Built core-image-minimal with rust-tools-analyzer installed, booted it
>    under qemu, and confirmed the rust-analyzer frontend and the
>    rust-analyzer-proc-macro-srv binary are present with their libraries
>    resolving.
>
> Benhur Tessele (2):
>   rust: package rust-analyzer as rust-tools-analyzer
>   packagegroup-rust-cross-canadian: add rust-analyzer to the SDK
>
>  .../packagegroup-rust-cross-canadian.bb       |  1 +
>  meta/recipes-devtools/rust/rust_1.98.1.bb     | 19 ++++++++++++++++---
>  2 files changed, 17 insertions(+), 3 deletions(-)

Hi Benhur,

Thanks for your patch.

I believe this is breaking build on some platforms. Maybe all ARM 32
bits?

ERROR: rust-1.98.1-r0 do_install: Execution of '/srv/pokybuild/yocto-worker/beaglebone-alt/build/build/tmp/work/cortexa8t2hf-neon-poky-linux-gnueabi/rust/1.98.1/temp/run.do_install.3194208' failed with exit code 1
...
| error[E0658]: use of unstable library feature `stdarch_arm_neon_intrinsics`
|   --> /rust/deps/simd-adler32-0.3.9/src/imp/neon.rs:23:7
|    |
| 23 |   use core::arch::arm::*;
|    |       ^^^^^^^^^^^^^^^
|    |
|    = note: see issue #111800 <https://github.com/rust-lang/rust/issues/111800> for more information
|    = help: add `#![feature(stdarch_arm_neon_intrinsics)]` to the crate attributes to enable
|    = note: this compiler was built on 2026-09-01; consider upgrading it if it is out of date
...
| -------------
| error: could not compile `simd-adler32` (lib) due to 67 previous errors
| warning: build failed, waiting for other jobs to finish...
...

https://autobuilder.yoctoproject.org/valkyrie/#/builders/10/builds/4734
https://autobuilder.yoctoproject.org/valkyrie/#/builders/74/builds/4706

Can you have a look at the issue?

Thanks,
Mathieu

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



  parent reply	other threads:[~2026-10-01 14:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-01 12:56 [PATCH 0/2] rust: add rust-analyzer support Benhur Tessele
2026-10-01 12:56 ` [PATCH 1/2] rust: package rust-analyzer as rust-tools-analyzer Benhur Tessele
2026-10-01 12:56 ` [PATCH 2/2] packagegroup-rust-cross-canadian: add rust-analyzer to the SDK Benhur Tessele
2026-10-01 14:08 ` Mathieu Dubois-Briand [this message]
2026-10-02  9:05   ` [OE-core] [PATCH 0/2] rust: add rust-analyzer support Paul Barker
2026-10-02 14:54     ` Benhur T
2026-10-01 14:13 ` Paul Barker
2026-10-01 15:47   ` Benhur T
2026-10-02  9:00     ` Paul Barker

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=DLTK70W1LZPD.1WPEJTEXRP8Q1@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=Randy.MacLeod@windriver.com \
    --cc=benhur.tessele@est.tech \
    --cc=openembedded-core@lists.openembedded.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