From: "Randy MacLeod" <randy.macleod@windriver.com>
To: anbelski@linux.microsoft.com,
openembedded-core <openembedded-core@lists.openembedded.org>
Cc: "Khem Raj" <raj.khem@gmail.com>,
"Andreas Müller" <schnitzeltony@gmail.com>,
"Vinay Kumar" <vinay.kumar@blackfigtech.com>
Subject: Re: [OE-core] meta-rust -> oe-core
Date: Wed, 17 Feb 2021 16:20:46 -0500 [thread overview]
Message-ID: <2a4a5d44-5013-d74e-f2ed-3fa031c96aeb@windriver.com> (raw)
In-Reply-To: <557d69ebe7e78cc245a3b4a9cd90223e9a2d7021.camel@linux.microsoft.com>
On 2021-02-17 6:45 a.m., Anatol Belski wrote:
> Hi Randy,
>
> thanks for driving progress on this work.
>
> On Tue, 2021-02-16 at 21:40 -0500, Randy MacLeod wrote:
>> I've updated poky-contrib with my merge of meta-rust to oe-core:
>>
>> http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=rmacleod/rust-wip-2021-02-16
>>
>> The build status is fine (shown below) aside from qemuriscv64/musl
>> and qemuppc/musl.
>>
>> Khem is working on the qemuriscv64/musl problem with upstream rust
>> devs.
>> qemuppc/musl fails due to:
>> libunwind.cpp:66:3: error: #error Architecture not supported
>>
>> Known issues if someone is interested:
>>
>> 1. I have an updated librsvg that isn't building using autotools
>> It does build with cargo but I doubt that will produce a library
>> that is usable. See
>> https://github.com/meta-rust/meta-rust/issues/264
>>
>>
>> http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=rmacleod/librsvg-broken-wip-2021-02-16
>>
>> 2. native-sdk support is broken:
>> https://github.com/meta-rust/meta-rust/issues/236
>> As shown in my OE talk last year, you can do rust application
>> development and testing without this but it would be best to
>> fix this bug and have rust behave like other YP toolchains.
>>
> I was working on the SDK support some passt weeks and coincidentially
> filed a PR yesterday
>
> https://github.com/meta-rust/meta-rust/pull/313
>
> This is definitely a wanted feature. If some would have time for a
> review, it'd be great.
That's great! I've been stuck in meetings all day but
I should have time tomorrow to review and test this change.
> Please also let me know how it would best be
> integrated into your patch.
Let's use the meta-rust review process and once it's
merged to master, I'll bring it over to my poky-contrib
branch.
Thanks,
../Randy
>
> Thanks
>
> Anatol
>
>> 3. There's an cargo-fetcher proposal sent to the bitbake
>> list from Andreas but I don't see a patch to meta-rust to
>> make the two patchsets work together. Andreas, is that something
>> that you can do, even if it's just a quick change to get started?
>>
>> 4. We're (Vinay via WR) working on a way to use the rustc test suite.
>> More to come on that later this week.
>>
>> Sorry that this has dragged on for so long.
>> Any help would be appreciated.
>>
>>
>>
>>
>>
>
--
# Randy MacLeod
# Wind River Linux
prev parent reply other threads:[~2021-02-17 21:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 2:40 meta-rust -> oe-core Randy MacLeod
2021-02-17 11:45 ` [OE-core] " Anatol Belski
2021-02-17 21:20 ` Randy MacLeod [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=2a4a5d44-5013-d74e-f2ed-3fa031c96aeb@windriver.com \
--to=randy.macleod@windriver.com \
--cc=anbelski@linux.microsoft.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=schnitzeltony@gmail.com \
--cc=vinay.kumar@blackfigtech.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