Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
To: Deepthi.Hemraj@windriver.com
Cc: openembedded-core@lists.openembedded.org,
	richard.purdie@linuxfoundation.org, Randy.MacLeod@windriver.com,
	Naveen.Gowda@windriver.com, Sundeep.Kokkonda@windriver.com
Subject: Re: [OE-core] [PATCH V3 1/2] rust-cross-canadian: Fix environment setup script conflicts for multilibs
Date: Mon, 2 Dec 2024 09:36:11 +0100	[thread overview]
Message-ID: <Z01xe5AYXZr0A2vE@bootlin-mathieu> (raw)
In-Reply-To: <20241129080820.330411-1-Deepthi.Hemraj@windriver.com>

On Fri, Nov 29, 2024 at 12:08:19AM -0800, Hemraj, Deepthi via lists.openembedded.org wrote:
> From: Deepthi Hemraj <Deepthi.Hemraj@windriver.com>
> 
> YOCTO [#15061]
> The target independent variables like CARGO_HTTP_MULTIPLEXING and
> CARGO_HTTP_CAINFO should be handled by the nativesdk-cargo recipe,
> rather than being managed within rust-cross-canadian.
> 
> The build section of the Cargo configuration file is also
> target-independent and hence moved to nativesdk-cargo.
> 
> The nativesdk-cargo recipe can then gather these entries from the individual
> target-specific files to generate the final cargo_home/config file.
> Target-specific configurations are specific to the rust-cross-canadian
> variant and should remain there.
> 
> Signed-off-by: Deepthi Hemraj <Deepthi.Hemraj@windriver.com>
> ---

Hi,

I believe these patches are breaking some builds on the autobuilder:

...
Caused by:
  could not parse TOML configuration in `/srv/pokybuild/yocto-worker/beaglebone/build/build/tmp/work/beaglebone_yocto-poky-linux-gnueabi/core-image-sato/1.0/testimage-sdk/sysroots/cortexa8hf-neon-poky-linux-gnueabi/home/cargo/config`
Caused by:
  TOML parse error at line 3, column 1
    |
  3 | [target.armv7-poky-linux-gnueabihf]
    | ^
  invalid table header
  dotted key `target` attempted to extend non-table type (string)

https://valkyrie.yoctoproject.org/#/builders/2/builds/558/steps/12/logs/stdio
https://valkyrie.yoctoproject.org/#/builders/60/builds/558/steps/12/logs/stdio
https://valkyrie.yoctoproject.org/#/builders/80/builds/488/steps/13/logs/stdio

oeqa.utils.subprocesstweak.OETestCalledProcessError: Command '. /srv/pokybuild/yocto-worker/genericx86-64/build/build/tmp/work/genericx86_64-poky-linux/core-image-sato/1.0/testimage-sdk/environment-setup-core2-64-poky-linux > /dev/null; cd /srv/pokybuild/yocto-worker/genericx86-64/build/build/tmp/work/genericx86_64-poky-linux/core-image-sato/1.0/testimage-sdk//hello; cargo build;' returned non-zero exit status 101
Standard Output: warning: `/srv/pokybuild/yocto-worker/genericx86-64/build/build/tmp/work/genericx86_64-poky-linux/core-image-sato/1.0/testimage-sdk/sysroots/core2-64-poky-linux/home/cargo/config` is deprecated in favor of `config.toml`
note: if you need to support cargo 1.38 or earlier, you can symlink `config` to `config.toml`
warning: unused config key `build.linker` in `/srv/pokybuild/yocto-worker/genericx86-64/build/build/tmp/work/genericx86_64-poky-linux/core-image-sato/1.0/testimage-sdk/sysroots/core2-64-poky-linux/home/cargo/config`
error: process didn't exit successfully: `rustc -vV` (exit status: 1)
--- stdout
rustc 1.80.1 (3f5fd8dd4 2024-08-06) (built from a source tarball)
binary: rustc
commit-hash: 3f5fd8dd41153bc5fdca9427e9e05be2c767ba23
commit-date: 2024-08-06
host: x86_64-pokysdk-linux-gnu
release: 1.80.1
--- stderr
error: Error loading target specification: Could not find specification for target "x86_64-pokysdk-linux-gnu". Run `rustc --print target-list` for a list of built-in targets

https://valkyrie.yoctoproject.org/#/builders/4/builds/563/steps/12/logs/stdio
https://valkyrie.yoctoproject.org/#/builders/19/builds/559/steps/12/logs/stdio
https://valkyrie.yoctoproject.org/#/builders/31/builds/549/steps/13/logs/stdio
https://valkyrie.yoctoproject.org/#/builders/32/builds/541/steps/13/logs/stdio
https://valkyrie.yoctoproject.org/#/builders/39/builds/546/steps/13/logs/stdio
https://valkyrie.yoctoproject.org/#/builders/41/builds/494/steps/13/logs/stdio

Can you have a look at these issues, please ?

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


      parent reply	other threads:[~2024-12-02  8:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-29  8:08 [PATCH V3 1/2] rust-cross-canadian: Fix environment setup script conflicts for multilibs Deepthi.Hemraj
2024-11-29  8:08 ` [PATCH V3 2/2] " Deepthi.Hemraj
2024-12-02  8:36 ` Mathieu Dubois-Briand [this message]

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=Z01xe5AYXZr0A2vE@bootlin-mathieu \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=Deepthi.Hemraj@windriver.com \
    --cc=Naveen.Gowda@windriver.com \
    --cc=Randy.MacLeod@windriver.com \
    --cc=Sundeep.Kokkonda@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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