From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Otavio Salvador <otavio@ossystems.com.br>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH v2 2/2] cargo-cross-canadian: Use SDK's flags during target linking
Date: Mon, 18 Jul 2022 13:45:37 +0100 [thread overview]
Message-ID: <e642480e892b0b411acb509c0de11aa7e52d4412.camel@linuxfoundation.org> (raw)
In-Reply-To: <20220710164300.953098-2-otavio@ossystems.com.br>
On Sun, 2022-07-10 at 13:43 -0300, Otavio Salvador wrote:
> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
> ---
>
> (no changes since v1)
>
> .../cargo/cargo-cross-canadian.inc | 20 ++++++++++++++++++-
> 1 file changed, 19 insertions(+), 1 deletion(-)
I did look into this with some local testing. With:
SDKAMCHINE = "aarch64"
MACHINE = "qemuarm64"
bitbake rust-cross-canadian-aarch64
still fails so there is still something wrong with the SDK builds :/
Cheers,
Richard
next prev parent reply other threads:[~2022-07-18 12:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-10 16:42 [PATCH v2 1/2] rust-common: Fix use of target definitions for SDK generation Otavio Salvador
2022-07-10 16:43 ` [PATCH v2 2/2] cargo-cross-canadian: Use SDK's flags during target linking Otavio Salvador
2022-07-18 12:45 ` Richard Purdie [this message]
2022-07-18 15:49 ` [OE-core] " Otavio Salvador
2022-07-18 15:59 ` Richard Purdie
2022-07-18 19:25 ` Otavio Salvador
2022-07-18 21:18 ` Richard Purdie
2022-07-18 21:41 ` Otavio Salvador
2022-07-18 22:54 ` Richard Purdie
2022-07-19 0:07 ` Otavio Salvador
2022-07-20 17:21 ` Richard Purdie
2022-07-20 18:11 ` Otavio Salvador
2022-07-20 18:26 ` Richard Purdie
2022-07-20 19:13 ` Otavio Salvador
2022-07-13 16:05 ` [PATCH v2 1/2] rust-common: Fix use of target definitions for SDK generation Sundeep KOKKONDA
2022-07-14 0:08 ` [OE-core] " Alejandro Enedino Hernandez Samaniego
2022-07-14 11:24 ` Otavio Salvador
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=e642480e892b0b411acb509c0de11aa7e52d4412.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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