It would help to come up with a set of reproducible steps, e.g.:

- check out revision X
- bitbake cargo-native
- check out revision Y (as close to X as possible)
- bitbake cargo-native which reliably fails

and file a ticket in bugzilla for it. The issue is definitely real.

Alex

On Fri, 14 Feb 2025 at 12:19, Alex Kiernan <alex.kier...@gmail.com> wrote:
>
> If you're seeing the same failure as me, its cargo-native and
> python3-cryptography-native - I've just pulled the latest changes and
> both failed to build here, cleaning them up seems to have fixed it.
>
> On Tue, Feb 11, 2025 at 2:00 PM Alexander Kanavin via
> lists.yoctoproject.org <alex.kanavin=gmail....@lists.yoctoproject.org>
> wrote:
> >
> > Run bitbake -c clean cargo and try again. Something in those recipes 
> > doesn’t do incremental builds properly.
> >
> > Alex
> >
> > On Tue 11. Feb 2025 at 14.55, David Daniel via lists.yoctoproject.org 
> > <david.daniel=vrag...@lists.yoctoproject.org> wrote:
> >>
> >> Hi all
> >> Some problem with the build of cargo just popped up. I am doing
> >> currently builds on the master branches. It turns out after a sync of
> >> my sources cargo does not build anymore. It spits weird error messages
> >> that it cannot find the crate for libc:
> >>
> >>     can't find crate for `libc`
> >>
> >> Somehow things got mixed:
> >>
> >>     error[E0460]: found possibly newer version of crate `std` which 
> >> `libnghttp2_sys` depends on
> >>
> >> I attached the build output in case of interest.
> >>
> >> Has anyone an idea how I can fix this?
> >> Thanks for any hints!
> >>
> >> Greets
> >> Dave
> >>
> >>
> >>
> >
> > 
> >
>
>
> --
> Alex Kiernan
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#64813): https://lists.yoctoproject.org/g/yocto/message/64813
Mute This Topic: https://lists.yoctoproject.org/mt/111122235/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to