From: "Sundeep KOKKONDA" <sundeep.kokkonda@windriver.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH V2 1/2] rust: fix for rust multilib sdk configuration
Date: Thu, 16 Jan 2025 07:52:53 -0800 [thread overview]
Message-ID: <1047.1737042773418542532@lists.openembedded.org> (raw)
In-Reply-To: <29c89cf909ccda3949e0bd1b50a5dbbc0a18094d.camel@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 163 bytes --]
The config file has options to set the linker for the target, which is anyway getting set with the sdk environment. So, the config file is redundant and removed.
[-- Attachment #2: Type: text/html, Size: 174 bytes --]
next prev parent reply other threads:[~2025-01-16 15:53 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 ` [OE-core] " Richard Purdie
2025-01-16 15:52 ` Sundeep KOKKONDA [this message]
2025-01-22 14:17 ` 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=1047.1737042773418542532@lists.openembedded.org \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.