rust-embedded / rust-embedded/meta-rust-bin
Cannot build eSDK due to conflicting cargo bins
Nobody has claimed this yet.
- Dominant language
- BitBake
- Stars
- 124
- Forks
- 92
- Avg merge
- 6h 54m
- Merged PRs (30d)
- 2
Description
I am trying to build and extensible sdk for other devs to use based on a custom image we have. While building I am getting the following error:
ERROR: luci-sdk-image-1.0-r0 do_sdk_depends: The file /usr/bin/cargo is installed by both cargo-native and cargo-bin-cross-aarch64, aborting
ERROR: Logfile of failure stored in: /home/kevin/source/yocto-kirkstone/build/tmp/work/luci_som_imx8-fsl-linux/luci-sdk-image/1.0-r0/temp/log.do_sdk_depends.54708
ERROR: Task (/home/kevin/source/yocto-kirkstone/sources/meta-luci/recipes-core/images/luci-sdk-image.bb:do_sdk_depends) failed with exit code '1'
It looks like since some packages rely on cargo-native while our packages rely on cargo-bin-cross-aarch64. Is there a way to tell the eSDK builder which of these files to include?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the failure log at .../luci-sdk-image/1.0-r0/temp/log.do_sdk_depends.54708 and the meta-luci/recipes-core/images/luci-sdk-image.bb recipe; inspect how cargo-native and cargo-bin-cross-aarch64 are pulled into the eSDK. Done means the eSDK build completes without both packages claiming /usr/bin/cargo.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100