Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: El Mehdi YOUNES <elmehdi.younes@smile.fr>
Cc: buildroot@buildroot.org, Eric Le Bihan <eric.le.bihan.dev@free.fr>
Subject: Re: [Buildroot] [RFC PATCH 5/5] linux: Add Rust support
Date: Tue, 3 Feb 2026 15:08:17 +0100	[thread overview]
Message-ID: <aYH9Ids-J7BuJl0u@windsurf> (raw)
In-Reply-To: <20250808133112.3212687-6-elmehdi.younes@smile.fr>

On Fri, Aug 08, 2025 at 03:31:12PM +0200, El Mehdi YOUNES via buildroot wrote:

> +ifeq ($(BR2_LINUX_KERNEL_RUST_SUPPORT),y)
> +LINUX_DEPENDENCIES += host-rustc host-rust-bindgen
> +LINUX_MAKE_FLAGS += \
> +	RUSTC=$(HOST_DIR)/bin/rustc \
> +	BINDGEN=$(HOST_DIR)/bin/bindgen \
> +	RUST_LIB_SRC=$(HOST_DIR)/lib/rustlib/src/rust/library \

You'll have to update this to $(HOST_DIR)/src/rust if that ends up
working (see our comments on PATCH 2/5).

Make sure to test this with both pre-compiled Rust compiler and
compiled-from-source Rust compiler.

And finally, we would like to have a test in support/testing/ to
verify that this continues to work. You don't need a test that boots
the kernel, but at least something that builds the kernel with Rust
support. Of course if there's some HW-agnostic kernel feature in Rust
that we can test in Qemu, it would be nice. Maybe binder? But I'm not
sure how to use it under a pure Linux system. But don't spend too much
time on this: a compile-time only test will be good enough.

Thanks a lot!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2026-02-03 14:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-08 13:31 [Buildroot] [RFC PATCH 0/5] Add Rust for Linux support El Mehdi YOUNES via buildroot
2025-08-08 13:31 ` [Buildroot] [RFC PATCH 1/5] package/rust-bindgen: add host-clang dependency El Mehdi YOUNES via buildroot
2026-02-03 11:11   ` Thomas Petazzoni via buildroot
2026-02-13 19:37   ` Thomas Perale via buildroot
2025-08-08 13:31 ` [Buildroot] [RFC PATCH 2/5] package/rust-bin: add Rust sources El Mehdi YOUNES via buildroot
2026-02-03 13:33   ` Thomas Petazzoni via buildroot
2026-02-03 14:27     ` El Mehdi YOUNES via buildroot
2025-08-08 13:31 ` [Buildroot] [RFC PATCH 3/5] package/rust-bin: install rustfmt El Mehdi YOUNES via buildroot
2026-02-03 13:35   ` Thomas Petazzoni via buildroot
2026-02-03 14:27     ` El Mehdi YOUNES via buildroot
2025-08-08 13:31 ` [Buildroot] [RFC PATCH 4/5] linux: split HOSTCC from flags El Mehdi YOUNES via buildroot
2026-02-03 13:50   ` Thomas Petazzoni via buildroot
2026-02-03 14:29     ` El Mehdi YOUNES via buildroot
2025-08-08 13:31 ` [Buildroot] [RFC PATCH 5/5] linux: Add Rust support El Mehdi YOUNES via buildroot
2026-02-03 14:08   ` Thomas Petazzoni via buildroot [this message]
2026-02-03 14:34     ` El Mehdi YOUNES via buildroot
2026-02-03 15:09       ` Thomas Petazzoni via buildroot

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=aYH9Ids-J7BuJl0u@windsurf \
    --to=buildroot@buildroot.org \
    --cc=elmehdi.younes@smile.fr \
    --cc=eric.le.bihan.dev@free.fr \
    --cc=thomas.petazzoni@bootlin.com \
    /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