From: ng0 <ng0@infotropique.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: Ricardo Wurmus <rekado@elephly.net>, 28433@debbugs.gnu.org
Subject: [bug#28433] [WIP] Rust update
Date: Sat, 28 Oct 2017 15:36:23 +0000 [thread overview]
Message-ID: <20171028153623.jpup557ubcbo6xlw@abyayala> (raw)
In-Reply-To: <20171026101728.6493ef46@scratchpost.org>
[-- Attachment #1: Type: text/plain, Size: 777 bytes --]
Danny Milosavljevic transcribed 8.7K bytes:
> Hi,
…
> So I guess my actual question is how to do this cross compilation correctly.
Note that the rust bootstrap compiler are binaries from upstream.
(There's a project "mrust" <https://github.com/thepowersgang/mrustc>
that is a reimplementation of Rust in C++ that we could use in the long
term in order to remove this binary)
In the long term this would be nice. It was my first idea when
I learned about this project, but as you can read in the
bug I opened in the last 2(?) months in the mrustc bugtracker
it still requires rustc to work.
--
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://dist.ng0.infotropique.org/dist/keys/
https://www.infotropique.org https://ng0.infotropique.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-10-28 15:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-12 16:50 [bug#28433] [WIP] Rust update Danny Milosavljevic
2017-10-25 14:19 ` Ricardo Wurmus
2017-10-26 8:17 ` Danny Milosavljevic
2017-10-28 10:42 ` Danny Milosavljevic
2017-10-28 11:31 ` Danny Milosavljevic
2017-10-28 11:57 ` Danny Milosavljevic
2017-10-28 18:26 ` Ludovic Courtès
2017-10-30 11:35 ` Danny Milosavljevic
2017-10-30 15:38 ` Ludovic Courtès
2017-10-30 16:14 ` Danny Milosavljevic
2017-11-28 6:35 ` ng0
2017-11-28 10:12 ` Danny Milosavljevic
2017-11-29 8:04 ` Danny Milosavljevic
2017-10-28 15:36 ` ng0 [this message]
2017-10-28 18:32 ` Ludovic Courtès
2017-10-30 19:18 ` [bug#28433] [WIP] v2 " Danny Milosavljevic
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=20171028153623.jpup557ubcbo6xlw@abyayala \
--to=ng0@infotropique.org \
--cc=28433@debbugs.gnu.org \
--cc=dannym@scratchpost.org \
--cc=rekado@elephly.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.
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).