From: "Ludovic Courtès" <ludo@gnu.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel@gnu.org
Subject: Re: Rust bootstrapping TODO
Date: Sat, 25 Jan 2020 18:30:00 +0100 [thread overview]
Message-ID: <877e1fa1gn.fsf@gnu.org> (raw)
In-Reply-To: <20200121194849.42616d44@scratchpost.org> (Danny Milosavljevic's message of "Tue, 21 Jan 2020 19:48:49 +0100")
Hi,
Danny Milosavljevic <dannym@scratchpost.org> skribis:
> (1) For all Mozilla Rusts except the latest one, pass
> "--disable-docs --disable-compilerdocs" in order to disable building (and
> especially TESTING) the docs. Testing the docs takes a very long time
> and no one will ever read the docs of the compilers used for bootstrapping.
I guess this kind of change could go in a topic branch that we’d merge
once IceCat is built.
> (2) Bootstrap rust 1.29.0 directly via mrustc 0.9.
> See https://github.com/thepowersgang/mrustc/issues/140 for why that is
> currently not working.
That’d be nice!
BTW, there’s a bounty program currently to get a Rust front-end in GCC,
which would be sweet.
> (3) Parallelize things again. In the past I've disabled parts of the
> parallel build because of bugs and/or memory constraints, but after (2) we
> could check whether they are working now.
OK.
> (4) Factor out the mrustc bootstrapper into a mrustc-bootstrapped-package
> procedure which changes a package in order to use mrustc, including the
> phases. That way, we can easily choose which of the Mozilla Rusts we want
> to bootstrap.
Interesting.
BTW, the other day on #guix there was someone from Fedora wondering
about how we’re bootstrapping Rust and looking to adapt it. Would be
worth joining forces!
Thanks for the update,
Ludo’.
prev parent reply other threads:[~2020-01-25 17:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-21 18:48 Rust bootstrapping TODO Danny Milosavljevic
2020-01-25 17:30 ` 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=877e1fa1gn.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=dannym@scratchpost.org \
--cc=guix-devel@gnu.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.