public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Harish.Sadineni@windriver.com, openembedded-core@lists.openembedded.org
Cc: Randy.MacLeod@windriver.com, Sundeep.Kokkonda@windriver.com,
	 Shivaprasad.Moodalappa@windriver.com
Subject: Re: [OE-core] [PATCH V2 1/2] rust: fix for rust multilib sdk configuration
Date: Thu, 16 Jan 2025 15:09:31 +0000	[thread overview]
Message-ID: <29c89cf909ccda3949e0bd1b50a5dbbc0a18094d.camel@linuxfoundation.org> (raw)
In-Reply-To: <20250116134833.1838212-1-Harish.Sadineni@windriver.com>

On Thu, 2025-01-16 at 05:48 -0800, Sadineni, Harish via lists.openembedded.org wrote:
> From: Harish Sadineni <Harish.Sadineni@windriver.com>
> 
> YOCTO [#15061]
> The rust sdk installs both 'rust.sh' and 'cargo.sh' for lib32 and lib64 in the same location.
> This causes below error while installing the lib32 & lib64 binaries:
> 
> Error: Transaction test error:
>   file /usr/local/oe-sdk-hardcoded-buildpath/sysroots/x86_64-pokysdk-linux/environment-setup.d/cargo.sh
> conflicts between attempted installs of rust-cross-canadian-arm-1.67.1-r0.x86_64_nativesdk and
>  rust-cross-canadian-aarch64-1.67.1-r0.x86_64_nativesdk
>   file /usr/local/oe-sdk-hardcoded-buildpath/sysroots/x86_64-pokysdk-linux/environment-setup.d/rust.sh
> conflicts between attempted installs of rust-cross-canadian-arm-1.67.1-r0.x86_64_nativesdk and
> rust-cross-canadian-aarch64-1.67.1-r0.x86_64_nativesdk
> ERROR: Task (virtual:multilib:lib32:/media/build/poky/meta/recipes-sato/images/core-image-sato.bb:do_populate_sdk)
> failed with exit code '1'
> 
> The change includes:
> - Prepending '${RUST_TARGET_SYS}' to 'rust.sh' to differentiate between target systems.
> - Moving the non-target-specific environment variables to 'nativesdk-cargo' and 'nativesdk-rust',
> instead of being managed by the cross-canadian recipe.
> - Removed the redundant cargo config file from the 'rust-cross-canadian.inc' file.
> 
> Signed-off-by: Harish Sadineni <Harish.Sadineni@windriver.com>
> ---
>  meta/recipes-devtools/rust/cargo_1.81.0.bb    | 15 +++++++++++
>  .../rust/rust-cross-canadian.inc              | 27 ++-----------------
>  meta/recipes-devtools/rust/rust_1.81.0.bb     | 13 +++++++++
>  3 files changed, 30 insertions(+), 25 deletions(-)

Thanks for the patch. Just to confirm, are you saying we no longer need
the $CARGO_HOME/config file?

Cheers,

Richard


  parent reply	other threads:[~2025-01-16 15:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-16 13:48 [PATCH V2 1/2] rust: fix for rust multilib sdk configuration Harish.Sadineni
2025-01-16 13:48 ` [PATCH V2 2/2] oeqa/sdk/context: fix for gtk3 test failure during do_testsdk Harish.Sadineni
2025-01-21 15:37   ` [OE-core] " Ross Burton
2025-01-22  8:12     ` Sadineni, Harish
2025-01-16 14:02 ` Patchtest results for [PATCH V2 1/2] rust: fix for rust multilib sdk configuration patchtest
2025-01-16 15:09 ` Richard Purdie [this message]
2025-01-16 15:52   ` Sundeep KOKKONDA
2025-01-22 14:17 ` [OE-core] " Esben Haabendal

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=29c89cf909ccda3949e0bd1b50a5dbbc0a18094d.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=Harish.Sadineni@windriver.com \
    --cc=Randy.MacLeod@windriver.com \
    --cc=Shivaprasad.Moodalappa@windriver.com \
    --cc=Sundeep.Kokkonda@windriver.com \
    --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