From: Eric Le Bihan <eric.le.bihan.dev@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] rust: new package
Date: Thu, 16 Jun 2016 22:31:53 +0200 [thread overview]
Message-ID: <20160616223153.363fb47b@itchy> (raw)
In-Reply-To: <A3C625A2-C5F3-40DA-B192-73424F71B9B8@exablox.com>
Hi!
Le Wed, 15 Jun 2016 15:42:13 -0700,
Charles Hardin <ckhardin@exablox.com> a ?crit :
> We are already building rust 1.9.0 derived from Eric?s patches - he
> updated them a bit ago and we modified them slightly.
>
> I haven?t tried to post any other patches since I don?t want to
> confuse the issue with our changes on his changes on buildroot
> changes.
A new version of the patch series, with support for Rust 1.9.0, will be
posted shortly. Feel free to comment/review it when available.
> BTW - I would also really want to know what the proper method is for
> making an EXTERNAL rust toolchain option because that llvm compiles
> is at least 5 expressos long and by the time it is down - well the
> hands just jitter.
Maybe we could introduce a virtual package named "rust-toolchain". Then
there will be two packages which provides it:
- rust: build Rust from source
- rust-external: download the official pre-built release or use one
provided by the user.
Regards,
--
ELB
next prev parent reply other threads:[~2016-06-16 20:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-24 14:39 [Buildroot] [PATCH 0/2] Add support for Rust programming language Eric Le Bihan
2016-04-24 14:39 ` [Buildroot] [PATCH 1/2] python: enable bzip2 in host variant Eric Le Bihan
2016-06-15 22:01 ` Thomas Petazzoni
2016-06-16 20:43 ` Eric Le Bihan
2016-06-16 20:55 ` Thomas Petazzoni
2016-04-24 14:39 ` [Buildroot] [PATCH 2/2] rust: new package Eric Le Bihan
2016-06-15 22:09 ` Thomas Petazzoni
2016-06-15 22:42 ` Charles Hardin
2016-06-16 20:31 ` Eric Le Bihan [this message]
2016-06-16 20:25 ` Eric Le Bihan
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=20160616223153.363fb47b@itchy \
--to=eric.le.bihan.dev@free.fr \
--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.