From: "Sundeep KOKKONDA" <sundeep.kokkonda@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2 1/2] rust-common: Fix use of target definitions for SDK generation
Date: Wed, 13 Jul 2022 09:05:57 -0700 [thread overview]
Message-ID: <13068.1657728357681872556@lists.openembedded.org> (raw)
In-Reply-To: <20220710164300.953098-1-otavio@ossystems.com.br>
[-- Attachment #1: Type: text/plain, Size: 484 bytes --]
Hello Otavio,
Are there any build/test issues with previous implementation? Can you let me know what are the regression caused by below commits. I want to understand the reason for the changes in this patch.
Fixes: ef566af964 ("rust: fix issue building cross-canadian tools for aarch64 on x86_64")
Fixes: bd36593ba3 ("rust-common: Drop LLVM_TARGET and simplify")
Fixes: 8ed000debb ("rust-common: Fix for target definitions returning 'NoneType' for arm")
Thanks,
Sundeep K.
[-- Attachment #2: Type: text/html, Size: 614 bytes --]
next prev parent reply other threads:[~2022-07-13 16:06 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 ` [OE-core] " Richard Purdie
2022-07-18 15:49 ` 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 ` Sundeep KOKKONDA [this message]
2022-07-14 0:08 ` [OE-core] [PATCH v2 1/2] rust-common: Fix use of target definitions for SDK generation 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=13068.1657728357681872556@lists.openembedded.org \
--to=sundeep.kokkonda@gmail.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