From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [Patch v4 2/3] cargo-bootstrap: new package
Date: Sat, 8 Apr 2017 15:20:20 +0200 [thread overview]
Message-ID: <20170408152020.12a89c69@free-electrons.com> (raw)
In-Reply-To: <20170408093406.GB32154@itchy>
Hello,
On Sat, 8 Apr 2017 11:34:06 +0200, Eric Le Bihan wrote:
> Hi!
>
> On 17-04-07 09:06:39, J?rg Krause wrote:
> > Hi Eric,
> >
> > On Sun, 2017-04-02 at 21:46 +0200, Eric Le Bihan wrote:
> > > This new package fetches a binary snapshot of Cargo, suitable for the
> > > host, in order to bootstrap the Rust compiler and Cargo, the package
> > > manager.
> >
> > Why not build it from source?
>
> Cargo uses Cargo as its build system, so you need to have a working
> version of Cargo on the host system to build a new version from the
> source code.
>
> To build the Rust compiler a binary snapshot is enough.
Can you update the commit log to make it clearer? I guess whenever
there's a question on a patch, it often indicates that the commit log
was not detailed enough.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-04-08 13:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-02 19:46 [Buildroot] [Patch v4 0/3] Add support for the Rust programming language Eric Le Bihan
2017-04-02 19:46 ` [Buildroot] [Patch v4 1/3] rust-bootstrap: new package Eric Le Bihan
2017-04-07 7:03 ` Jörg Krause
2017-04-07 8:26 ` Thomas Petazzoni
2017-04-07 8:54 ` Jörg Krause
2017-04-07 9:03 ` Thomas Petazzoni
2017-04-07 9:22 ` Jörg Krause
2017-04-07 10:26 ` Thomas Petazzoni
2017-04-08 9:23 ` Eric Le Bihan
2017-04-02 19:46 ` [Buildroot] [Patch v4 2/3] cargo-bootstrap: " Eric Le Bihan
2017-04-07 7:06 ` Jörg Krause
2017-04-08 9:34 ` Eric Le Bihan
2017-04-08 13:20 ` Thomas Petazzoni [this message]
2017-04-02 19:46 ` [Buildroot] [Patch v4 3/3] rust: " Eric Le Bihan
2017-04-07 7:18 ` Jörg Krause
2017-04-08 10:09 ` Eric Le Bihan
2017-04-10 19:02 ` Jörg Krause
2017-04-10 21:43 ` Arnout Vandecappelle
2017-04-13 6:05 ` Jörg Krause
2017-04-13 16:49 ` Eric Le Bihan
2017-04-13 21:09 ` Arnout Vandecappelle
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170408152020.12a89c69@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.