From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: pgowda.cve@gmail.com, openembedded-core@lists.openembedded.org
Cc: Randy.MacLeod@windriver.com, vinay.m.engg@gmail.com
Subject: Re: [PATCH] rust: Fix cross compilation error for rust-testuite
Date: Sun, 04 Sep 2022 22:41:35 +0100 [thread overview]
Message-ID: <18246fa7e54cb51ecc6e1db0db7ac03bf276d5d3.camel@linuxfoundation.org> (raw)
In-Reply-To: <20220904070859.2706350-1-pgowda.cve@gmail.com>
On Sun, 2022-09-04 at 12:38 +0530, pgowda.cve@gmail.com wrote:
> From: pgowda <pgowda.cve@gmail.com>
>
> Fixes the following error while building the rust-testuite
> error: linker cc not found
>
> Signed-off-by: pgowda <pgowda.cve@gmail.com>
> ---
> meta/recipes-devtools/rust/rust.inc | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/meta/recipes-devtools/rust/rust.inc b/meta/recipes-devtools/rust/rust.inc
> index 284347dedc..a3d93eca4a 100644
> --- a/meta/recipes-devtools/rust/rust.inc
> +++ b/meta/recipes-devtools/rust/rust.inc
> @@ -116,6 +116,9 @@ python do_configure() {
> # Whether or not to optimize the compiler and standard library
> config.set("rust", "optimize", e(True))
>
> + # Override default linker cc.
> + config.set("rust", "default-linker", e(d.expand("${RUST_BUILD_CCLD}")))
> +
> # [build]
> config.add_section("build")
> config.set("build", "submodules", e(False))
I suspect this is resulting in:
WARNING: rust-1.63.0-r0 do_package_qa: QA Issue: File /usr/lib/librustc_driver-f2e4e0d5a644441f.so in package rust contains reference to TMPDIR [buildpaths]
https://autobuilder.yoctoproject.org/typhoon/#/builders/52/builds/5731
https://autobuilder.yoctoproject.org/typhoon/#/builders/64/builds/5809
and more. Certainly one of the patches is causing this :(
Cheers,
Richard
prev parent reply other threads:[~2022-09-04 21:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-04 7:08 [PATCH] rust: Fix cross compilation error for rust-testuite pgowda.cve
2022-09-04 21:41 ` Richard Purdie [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=18246fa7e54cb51ecc6e1db0db7ac03bf276d5d3.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=Randy.MacLeod@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=pgowda.cve@gmail.com \
--cc=vinay.m.engg@gmail.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