From: ludo@gnu.org (Ludovic Courtès)
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 32822@debbugs.gnu.org
Subject: [bug#32822] [PATCH 0/4] Finish rust bootstrapping.
Date: Tue, 25 Sep 2018 17:31:11 +0200 [thread overview]
Message-ID: <87h8id4mrk.fsf@gnu.org> (raw)
In-Reply-To: <20180925100149.0e481122@scratchpost.org> (Danny Milosavljevic's message of "Tue, 25 Sep 2018 10:01:49 +0200")
Hello,
Danny Milosavljevic <dannym@scratchpost.org> skribis:
> On Mon, 24 Sep 2018 21:38:21 +0200
> ludo@gnu.org (Ludovic Courtès) wrote:
>
>> Danny Milosavljevic <dannym@scratchpost.org> skribis:
>>
>> > Danny Milosavljevic (4):
>> > gnu: rust: Hide "ar" entry from rust@1.21.0.
>> > gnu: rust@1.23.0: Bootstrap by rust@1.22.0.
>> > gnu: rust@1.23.0: Use rust-bootstrapped-package.
>> > gnu: rust: Remove binary bootstrapper.
>>
>> Do I get it right that mrustc is capable enough to build Rust 1.19, and
>> from there on we have the full chain?
>
> Yes (except for MIPS, where mrustc doesn't have the target settings in
> upstreeam - but I do, but untested).
Woohoo! Impressive.
>> That sounds really exciting! And worth a blog post :-), if only to
>> share with those who care about building from source: #bootstrappable,
>> Debian, and other reproducible build people.
>
> Sure. Should I just E-Mail the text or how do I get it into the blog?
You can send a .md file or a patch against guix-artwork.git (under
website/posts) to guix-blog@gnu.org for feedback (though currently it’s
just Jelle, Ricardo, and myself IIRC.) And then you can push to
guix-artwork.git and I can do the CVS dance to put it on-line.
>> FWIW the patches LGTM. I suppose you could push them to wip-rust, then
>> we let hydra and berlin build it, and once it’s built (could be 36h
>> later?) we merge into master.
>
> Okay. I've pushed them to wip-rust. How do we make hydra and berlin build it?
If I didn’t make any mistake it should show up at:
https://hydra.gnu.org/jobset/gnu/wip-rust
https://berlin.guixsd.org/jobset/wip-rust
Thanks for all the work!
Ludo’.
prev parent reply other threads:[~2018-09-25 15:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-24 14:47 [bug#32822] [PATCH 0/4] Finish rust bootstrapping Danny Milosavljevic
2018-09-24 15:01 ` [bug#32822] [PATCH 1/4] gnu: rust: Hide "ar" entry from rust@1.21.0 Danny Milosavljevic
2018-09-24 15:01 ` [bug#32822] [PATCH 2/4] gnu: rust@1.23.0: Bootstrap by rust@1.22.0 Danny Milosavljevic
2018-09-24 15:01 ` [bug#32822] [PATCH 3/4] gnu: rust@1.23.0: Use rust-bootstrapped-package Danny Milosavljevic
2018-09-24 15:01 ` [bug#32822] [PATCH 4/4] gnu: rust: Remove binary bootstrapper Danny Milosavljevic
2018-09-24 19:38 ` [bug#32822] [PATCH 0/4] Finish rust bootstrapping Ludovic Courtès
2018-09-25 8:01 ` Danny Milosavljevic
2018-09-25 15:31 ` Ludovic Courtès [this message]
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=87h8id4mrk.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=32822@debbugs.gnu.org \
--cc=dannym@scratchpost.org \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
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.