all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: ludo@gnu.org
Cc: Mark H Weaver <mhw@netris.org>, 32834@debbugs.gnu.org
Subject: [bug#32834] [PATCH] gnu: icecat: Build with rust-1.24.
Date: Sun, 30 Sep 2018 05:44:11 +0000	[thread overview]
Message-ID: <4F179DDB-1E56-44ED-8F7D-A088BB30905E@flashner.co.il> (raw)
In-Reply-To: <87lg7kvuhz.fsf@gnu.org>



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.

>
>Mark, Danny: WDYT?
>
>Thanks,
>Ludo’.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

  parent reply	other threads:[~2018-09-30  5:45 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 [this message]
2018-10-01  9:03     ` Nils Gillmann
2018-10-02  9:16       ` Ludovic Courtès
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F179DDB-1E56-44ED-8F7D-A088BB30905E@flashner.co.il \
    --to=efraim@flashner.co.il \
    --cc=32834@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=mhw@netris.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.