From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Craven Subject: Re: rust: cargo build-system: how to handle libraries Date: Wed, 28 Dec 2016 10:59:20 +0100 Message-ID: References: <8760m5c4dv.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> <87eg0ss8xl.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> <87bmvws8tf.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:40429) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cMB14-00012e-IH for guix-devel@gnu.org; Wed, 28 Dec 2016 04:59:27 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cMB0z-0002vu-Tl for guix-devel@gnu.org; Wed, 28 Dec 2016 04:59:26 -0500 Received: from mail-qk0-x236.google.com ([2607:f8b0:400d:c09::236]:33931) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cMB0z-0002vo-PH for guix-devel@gnu.org; Wed, 28 Dec 2016 04:59:21 -0500 Received: by mail-qk0-x236.google.com with SMTP id h201so101624191qke.1 for ; Wed, 28 Dec 2016 01:59:21 -0800 (PST) In-Reply-To: <87bmvws8tf.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: ng0 Cc: guix-devel > Of course I meant Cargo.lock, not Cargo.toml ... so I know what I > have to search for, and this makes it a bit easier than the > previous search. See cargo workspaces: https://github.com/rust-lang/libc/blob/master/Cargo.toml https://github.com/rust-lang/rfcs/blob/master/text/1525-cargo-workspace.md It's a fairly new thing, you'll have to track down the relevant commits in cargo and check if the cargo version we are using is new enough and understand it's semantics and how it applies to the cargo build system. My recommendation to fix this issue is to not run the tests if there isn't a Cargo.lock file, but this is likely not going to solve the underlying cause in this case. You can also package version 0.2.16 which does not use workspaces.