[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: How to debug a failed build of rust application under cargo-build-sy
From: |
Nils Landt |
Subject: |
Re: How to debug a failed build of rust application under cargo-build-system? |
Date: |
Thu, 15 Feb 2024 15:42:51 +0100 (CET) |
> Tomas Volf <~@wolfsden.cz> hat am 15.02.2024 14:26 CET geschrieben:
>
>
> On 2024-02-15 13:06:23 +0000, woshilapin wrote:
> > Hi,
> >
> > It is indeed a code error which looks weird. Are you sure the 2
> > compilations compile the same source code?
>
> Well, technically I am not sure. I ran the `guix import crate -r netavark'
> and
> used the output from that. My expectation was that it would walk the
> dependencies, and produce the same dependency tree cargo would use. Is that a
> correct expectation?
Not necessarily correct, no.
cargo install does not use the lockfile, see
https://doc.rust-lang.org/cargo/commands/cargo-install.html#dealing-with-the-lockfile
The cargo-build-system also doesn't use it.
The crate importer also doesn't use it :)
> > > Could someone nudge me in the right direction regarding how to debug this
> > > issue?
> > > I am not really sure where to start.
First, I'd try to make sure that guix build rust-tonic works.
This page helped me a lot in getting started:
https://guix.gnu.org/manual/en/html_node/Debugging-Build-Failures.html
I tried to reproduce this locally (import and build), building rust-tonic works
fine for me.
Funnily enough, I'm running into a completely different error, related to
https://github.com/hyperium/tonic/blob/408f46d5f2e1a25547831eb4b064bdeaf3868979/tonic-build/src/lib.rs#L47-L60