unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ng0 <ng0@libertad.pw>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: rust: Crate Dependencies
Date: Thu, 29 Dec 2016 12:33:11 +0000	[thread overview]
Message-ID: <87k2ai6hko.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <20161229121255.750fa1e3@scratchpost.org>

Danny Milosavljevic <dannym@scratchpost.org> writes:

> Hi David,
>
> On Thu, 29 Dec 2016 11:49:19 +0100
> David Craven <david@craven.ch> wrote:
>
>> It matters very
>> much which versions of rustc and cargo are used
>
> I used the versions in your v2 patch. I also tried ng0's update which didn't improve things.

Same here for libc crate after the update, but I guess that's
because cargo is currently packaged and used from the bootstrap
rust, which is dated one version before the actual rustc you can
use now, so 0.13.0 cargo and 0.14.0 rustc.
I hope packaging cargo on its own will add the support for
namespaces.

>
> How does rustc find the (Rust) dependencies when building a package in cargo-build-system? There doesn't seem to be a RUST* or CARGO* environment variable or anything when I do "guix environment rust-c-vec --fallback". (Note that I picked rust-c-vec to fix first because it has only rust-libc as dependency)
>
> I read that there are actual Rust binary libraries, seldomly used, and everything-included-only-as-source otherwise. How do I specify which it is?
>
> Or is that not implemented yet?
>
> I tried specifying the latter as native-inputs - which doesn't seems to work either...
>
>

-- 
♥Ⓐ  ng0
PGP keys and more: https://n0is.noblogs.org/ http://ng0.chaosnet.org

  parent reply	other threads:[~2016-12-29 12:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-28 14:51 rust: Crate Dependencies Danny Milosavljevic
2016-12-29 10:49 ` David Craven
2016-12-29 11:12   ` Danny Milosavljevic
2016-12-29 11:35     ` David Craven
2016-12-29 12:33     ` ng0 [this message]
2016-12-29 17:35       ` David Craven
2016-12-29 20:10         ` ng0

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k2ai6hko.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me \
    --to=ng0@libertad.pw \
    --cc=dannym@scratchpost.org \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).