From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] [Patch v4 1/3] rust-bootstrap: new package
Date: Fri, 07 Apr 2017 10:54:04 +0200 [thread overview]
Message-ID: <1491555244.1058.1.camel@embedded.rocks> (raw)
In-Reply-To: <20170407102613.7a8c96b3@free-electrons.com>
Hi,
On Fri, 2017-04-07 at 10:26 +0200, Thomas Petazzoni wrote:
> Hello,
>
> On Fri, 07 Apr 2017 09:03:34 +0200, J?rg Krause wrote:
> > On Sun, 2017-04-02 at 21:46 +0200, Eric Le Bihan wrote:
> > > This new package fetches a binary snapshot of the Rust compiler,
> > > suitable for the host, in order to bootstrap the Rust compiler.
> > >
> > > Signed-off-by: Eric Le Bihan <eric.le.bihan.dev@free.fr>
> > > ---
> > > ?DEVELOPERS?????????????????????????????????|??1 +
> > > ?package/rust-bootstrap/rust-bootstrap.hash |??5 ++++
> > > ?package/rust-bootstrap/rust-bootstrap.mk???| 37
> > > ++++++++++++++++++++++++++++++
> > > ?3 files changed, 43 insertions(+)
>
> It would be nice if you could fix your e-mail client to not rewrap the
> text you are replying to :)
Naughty mail client. Told him not do such bad things anymore :-)
> > > +ifeq ($(HOSTARCH),x86_64)
> > > +RUST_BOOTSTRAP_ARCH = x86_64
> > > +else ifeq ($(HOSTARCH),x86)
> > > +RUST_BOOTSTRAP_ARCH = i686
> > > +endif
> >
> > Is there any necessity to limit the bootstrap compiler to those host
> > archs only?
>
> The bootstrap compiler is provided as a binary only thing,
> pre-compiled. So it works only on the architectures it was compiled
> for. At least, that's why I remember from previous series on this topic.
But, if I am running Buildroot on a PowerPC it should be able to fetch
and run the binary for PowerPC, right?
> > > +RUST_BOOTSTRAP_SOURCE = rustc-$(RUST_BOOTSTRAP_LABEL).tar.gz
> > > +RUST_BOOTSTRAP_LICENSE = Apache-2.0 or MIT
> > > +RUST_BOOTSTRAP_LICENSE_FILES = LICENSE-APACHE LICENSE-MIT
> > > +RUST_BOOTSTRAP_LIBSTD_SOURCE= rust-std-
> > > $(RUST_BOOTSTRAP_LABEL).tar.gz
> > > +RUST_BOOTSTRAP_LIBSTD_ROOT = rust-std-$(RUST_BOOTSTRAP_LABEL)/rust-
> > > std-$(RUST_BOOTSTRAP_TRIPLE)
> >
> > Why not make a seperate package?
>
> It apparently needs to be extracted within the bootstrap compiler tree,
> i.e in $(@D)/rustc, I guess that's why. But Eric can give more details
> here.
Maybe the path to the rust libraries could be added to LD_LIBRARY_PATH?
J?rg
next prev parent reply other threads:[~2017-04-07 8:54 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 [this message]
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
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=1491555244.1058.1.camel@embedded.rocks \
--to=joerg.krause@embedded.rocks \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox