You should try 
https://git.yoctoproject.org/meta-lts-mixins/log/?h=kirkstone/rust-1.68
That works well with current meta-virtualization master including netavark 
(currently at 1.7.0).

Peter

From: meta-virtualization@lists.yoctoproject.org 
<meta-virtualization@lists.yoctoproject.org> On Behalf Of Bruce Ashfield via 
lists.yoctoproject.org
Sent: Tuesday, October 10, 2023 15:37
To: Marek Belisko <marek.beli...@gmail.com>
Cc: meta-virtualization@lists.yoctoproject.org
Subject: Re: [meta-virtualization] backporting netavark from master to kirkstone



On Tue, Oct 10, 2023 at 9:17 AM Marek Belisko 
<marek.beli...@gmail.com<mailto:marek.beli...@gmail.com>> wrote:
Hi,

I'm trying to backport netavark recipe 1.8.0 to kirkstone (where is 1.1.0 
present) but facing some issues. I've used cargo bitbake to generate recipe but 
when run build it fails with:
| DEBUG: Executing shell function do_compile
| NOTE: cargo = 
/data/projects/test/project/build/tmp/work/cortexa53-crypto-poky-linux/netavark/1.8.0-r0/recipe-sysroot-native/usr/bin/cargo
| NOTE: rustc =
| NOTE: cargo build -v --target aarch64-poky-linux --release 
--manifest-path=/data/projects/test/project/build/tmp/work/cortexa53-crypto-poky-linux/netavark/1.8.0-r0/git//Cargo.toml
| error: failed to get `anyhow` as a dependency of package `netavark v1.8.0 
(/data/projects/test/project/build/tmp/work/cortexa53-crypto-poky-linux/netavark/1.8.0-r0/git)`
|
| Caused by:
|   failed to load source for dependency `anyhow`
|
| Caused by:
|   Unable to update registry `crates-io`
|
| Caused by:
|   failed to update replaced source registry `crates-io`
|
| Caused by:
|   failed to parse manifest at 
`/data/projects/test/project/build/tmp/work/cortexa53-crypto-poky-linux/netavark/1.8.0-r0/cargo_home/bitbake/regex-1.9.5/Cargo.toml`
|
| Caused by:
|   namespaced features with the `dep:` prefix are only allowed on the nightly 
channel and requires the `-Z namespaced-features` flag on the command-line
| WARNING: exit code 101 from a shell command.


Does that mean I would also need to backport new cargo or so to compile it? Is 
is even possible please?

You'd probably get a better answer by finding the cargo-bitbake maintainers and 
seeing if they've run into a similar situation or have any advice.

We definitely use the tool to generate the crates for meta-virt, but that 
unfortunately doesn't give much insight into the rust or cargo inner workings. 
It is similar with golang .. it is extensively used in meta-virt for recipes, 
etc, but that doesn't mean there's a lot of expert advice on internals of 
golang.

Perhaps the submitter of the recipe will have advice (maybe they used it on the 
older release as well), but otherwise, I do suggest trying oe-core and/or the 
cargo-bitbake maintainers.

Bruce



Thanks and BR,

marek

--
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
twitter: #opennandra
web: http://open-nandra.com




--
- Thou shalt not follow the NULL pointer, for chaos and madness await thee at 
its end
- "Use the force Harry" - Gandalf, Star Trek II
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#8346): 
https://lists.yoctoproject.org/g/meta-virtualization/message/8346
Mute This Topic: https://lists.yoctoproject.org/mt/101874620/21656
Group Owner: meta-virtualization+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-virtualization/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to