GNU bug report logs - #39041
cargo-build-system expects build dependencies to be in #:cargo-inputs, but the importer places them to #:cargo-development-inputs

Previous Next

Package: guix;

Reported by: Valentin Ignatev <valentignatev <at> gmail.com>

Date: Wed, 8 Jan 2020 17:28:02 UTC

Severity: normal

To reply to this bug, email your comments to 39041 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-guix <at> gnu.org:
bug#39041; Package guix. (Wed, 08 Jan 2020 17:28:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Valentin Ignatev <valentignatev <at> gmail.com>:
New bug report received and forwarded. Copy sent to bug-guix <at> gnu.org. (Wed, 08 Jan 2020 17:28:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Valentin Ignatev <valentignatev <at> gmail.com>
To: bug-guix <at> gnu.org
Subject: cargo-build-system expects build dependencies to be in
 #:cargo-inputs, but the importer places them to #:cargo-development-inputs
Date: Wed, 8 Jan 2020 20:27:15 +0300
As the subject states, when you import a cargo package from crates.io,
importer places build dependencies to #:cargo-development-inputs, but
when you build the package, cargo fails to find such dependencies. It
works well if you move build deps from #:cargo-development-inputs to
#:cargo-inputs.

One example of this behavior is terminfo package and its phf-codegen
dependency. Another example is x11-dl package and its pkg-config
dependency

Regards,
Valentin




This bug report was last modified 4 years and 81 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.