All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: buildroot@buildroot.org, Eric Le Bihan <eric.le.bihan.dev@free.fr>
Subject: Re: [Buildroot] [PATCH 1/1] package/rust: use cargo environment during installation
Date: Wed, 7 Oct 2026 09:53:44 +0200	[thread overview]
Message-ID: <asX6R74TC4XMSXDo@windsurf> (raw)
In-Reply-To: <20261006195933.2225477-1-james.hilliard1@gmail.com>

On Tue, Oct 06, 2026 at 01:59:33PM -0600, James Hilliard wrote:
> Pass HOST_PKG_CARGO_ENV to x.py dist, as is already done for x.py build.
> This ensures Cargo uses Buildroot's configured CARGO_HOME instead of
> falling back to the user's default cache, and keeps the host RUSTFLAGS
> consistent between the build and installation steps.
> 
> Fixes:
>  - https://autobuild.buildroot.net/results/02b/02b2fc6ba7329852d7bf6ae4935c120c4de47b3e
> 
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>

Thanks for the patch. Since when does this problem exist? Of course it
exists since x.py support was introduced, but did it become visible
because of a new package, or package update?

As it's a fix, we need to have sufficient information in the commit
message about which commit introduced the issue, so that our LTS
branch maintainers can understand whether it needs to be backported or
not.

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-10-07  8:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-06 19:59 [Buildroot] [PATCH 1/1] package/rust: use cargo environment during installation James Hilliard
2026-10-07  7:53 ` Thomas Petazzoni via buildroot [this message]
2026-10-07  9:45   ` James Hilliard

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=asX6R74TC4XMSXDo@windsurf \
    --to=buildroot@buildroot.org \
    --cc=eric.le.bihan.dev@free.fr \
    --cc=james.hilliard1@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.