From: ludo@gnu.org (Ludovic Courtès)
To: Nils Gillmann <ng0@n0.is>
Cc: Mark H Weaver <mhw@netris.org>, 32834@debbugs.gnu.org
Subject: [bug#32834] [PATCH] gnu: icecat: Build with rust-1.24.
Date: Tue, 02 Oct 2018 11:16:04 +0200 [thread overview]
Message-ID: <87r2h8so8b.fsf@gnu.org> (raw)
In-Reply-To: <20181001090338.aflixd7cezx2sicp@abyayala> (Nils Gillmann's message of "Mon, 1 Oct 2018 09:03:38 +0000")
Nils Gillmann <ng0@n0.is> skribis:
> Efraim Flashner transcribed 782 bytes:
>>
>>
>> On September 29, 2018 9:55:36 PM UTC, ludo@gnu.org wrote:
>> >Hi Efraim,
>> >
>> >Efraim Flashner <efraim@flashner.co.il> skribis:
>> >
>> >> * gnu/packages/gnuzilla.scm (icecat)[native-inputs]: Use the oldest
>> >> compatable rust over newer releases when building icecat.
>> >
>> >[...]
>> >
>> >> + ;; Icecat 60 checkes for rust>=1.24
>> >> + `(("rust" ,rust-1.24)
>> >> + ("cargo" ,rust-1.24 "cargo")
>> >
>> >I suppose the goal is to reduce the build chain, right?
>>
>> Right. Currently each round of rust takes about 12 hours on my fast aarch64 board. This built successfully on aarch64 and ng0 was able to build and test it on x86_64.
>
> It is convenient (less than 36 hours build, build only one version of
> rust), but I have to second the doubt about CVEs.
> Mark, have you considered asking Mozilla about their recommended
> strategy wrt chosing the right rust for a Firefox-based browser
> building and implications of using an older rust for crates already
> in Firefox?
I suspect Mozilla is not paying attention to bootstrapping issues the
way we do, so they’d probably recommend just using the latest Rust
version.
Ludo’.
next prev parent reply other threads:[~2018-10-02 9:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-25 4:49 [bug#32834] [PATCH] gnu: icecat: Build with rust-1.24 Efraim Flashner
2018-09-29 21:55 ` Ludovic Courtès
2018-09-29 22:55 ` Danny Milosavljevic
2018-09-30 3:20 ` Mark H Weaver
2018-09-30 19:27 ` Ludovic Courtès
2018-09-30 5:44 ` Efraim Flashner
2018-10-01 9:03 ` Nils Gillmann
2018-10-02 9:16 ` Ludovic Courtès [this message]
2018-10-02 9:47 ` Nils Gillmann
2018-10-03 3:48 ` Joe Hillenbrand
2018-10-09 0:18 ` Mark H Weaver
2018-10-14 6:59 ` bug#32834: " Efraim Flashner
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=87r2h8so8b.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=32834@debbugs.gnu.org \
--cc=mhw@netris.org \
--cc=ng0@n0.is \
/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).