From: Belisko Marek <marek.belisko@gmail.com>
To: meta-virtualization@lists.yoctoproject.org
Subject: backporting netavark from master to kirkstone
Date: Tue, 10 Oct 2023 15:17:18 +0200 [thread overview]
Message-ID: <CAAfyv36CATBWC1vL6Bucq-JsJW4djFK50-kRHX6MxwizV9m2+g@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1745 bytes --]
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?
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
[-- Attachment #2: Type: text/html, Size: 2180 bytes --]
next reply other threads:[~2023-10-10 13:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 13:17 Belisko Marek [this message]
2023-10-10 13:37 ` [meta-virtualization] backporting netavark from master to kirkstone Bruce Ashfield
2023-10-10 14:30 ` Marko, Peter
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=CAAfyv36CATBWC1vL6Bucq-JsJW4djFK50-kRHX6MxwizV9m2+g@mail.gmail.com \
--to=marek.belisko@gmail.com \
--cc=meta-virtualization@lists.yoctoproject.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).