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 11:22:01 +0200 [thread overview]
Message-ID: <1491556921.1058.3.camel@embedded.rocks> (raw)
In-Reply-To: <20170407110356.108f4c78@free-electrons.com>
On Fri, 2017-04-07 at 11:03 +0200, Thomas Petazzoni wrote:
> Hello,
>
> On Fri, 07 Apr 2017 10:54:04 +0200, J?rg Krause wrote:
>
> > > > 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?
>
> If there's no prebuilt Rust compiler for PowerPC, then no, it will
> simply not be possible.
Fetching and extracting the PowerPC release tarball [1]:
[joerg at nzxt rust-1.16.0-powerpc64-unknown-linux-gnu]$ file
rustc/bin/rustc?
rustc/bin/rustc: ELF 64-bit MSB shared object, 64-bit PowerPC or cisco
7500, version 1 (SYSV), dynamically linked, interpreter
/lib64/ld64.so.1, for GNU/Linux 3.2.0,
BuildID[sha1]=39357ec02406358be73f28d80dabfdd9e9816de9, not stripped,
with debug_info
> We have already lots of things in Buildroot that depend on x86 or
> x86-64. Check all packages/options that use BR2_HOSTARCH.
>
> So, it's fine for Rust to also require a x86/x86-64 machine, as long as
> the proper BR2_HOSTARCH dependency is present in the Config.in.
As I am running x64 it is fine for me, too. Just wondered why to limit
the hosts archs if there are binaries available.
[1] https://static.rust-lang.org/dist/rust-1.16.0-powerpc64-unknown-lin
ux-gnu.tar.gz
J?rg
next prev parent reply other threads:[~2017-04-07 9:22 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 [this message]
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=1491556921.1058.3.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