From: Chris Marusich <cmmarusich@gmail.com>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Rust 1.19 fails to build on i686 on ‘staging’
Date: Tue, 12 Feb 2019 03:47:53 -0800 [thread overview]
Message-ID: <87o97hz0ra.fsf@gmail.com> (raw)
In-Reply-To: <20190211223456.0779cf68@scratchpost.org> (Danny Milosavljevic's message of "Mon, 11 Feb 2019 22:34:56 +0100")
[-- Attachment #1: Type: text/plain, Size: 949 bytes --]
Hi Danny,
Danny Milosavljevic <dannym@scratchpost.org> writes:
> Hi Chris,
>
> upstream says that compiling rust 1.19.0 works fine for them on i686 with their mrustc
> master (since they have applied our variable-length integer decoding patch):
>
> https://github.com/thepowersgang/mrustc/issues/108
Good to hear they're working with us!
> Would you have some time and a free computer to be able to build rust 1.19.0 with
>
> ./pre-inst-env guix build -K -s i686-linux rust@1.19.0
>
> on guix master with the patch below?
I have a spare computer. It only has 2 GB of RAM and 2 GB of swap,
though. Will it be enough?
By the way, unfortunately your patch did not apply cleanly to the
current master branch head (c86b5f1b9bdfdd478ba15804f9343feb8d9c019b).
If you think my little computer will be able to crunch through the
build, I'm happy to let it run if you can supply a clean patch.
Thank you!
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2019-02-12 11:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 14:39 Rust 1.19 fails to build on i686 on ‘staging’ Ludovic Courtès
2019-01-28 15:22 ` Danny Milosavljevic
2019-01-28 15:27 ` Danny Milosavljevic
2019-01-28 15:35 ` Danny Milosavljevic
2019-01-29 8:36 ` Ludovic Courtès
2019-01-30 17:59 ` Danny Milosavljevic
2019-02-05 11:28 ` Danny Milosavljevic
2019-02-05 11:35 ` Danny Milosavljevic
2019-02-11 21:34 ` Danny Milosavljevic
2019-02-12 11:47 ` Chris Marusich [this message]
2019-02-12 12:06 ` Danny Milosavljevic
2019-02-13 2:59 ` Chris Marusich
2019-02-13 5:49 ` Chris Marusich
2019-02-14 4:35 ` Chris Marusich
2019-02-14 17:14 ` Danny Milosavljevic
2019-02-15 9:11 ` Chris Marusich
2019-02-15 10:51 ` Danny Milosavljevic
2019-02-16 10:53 ` Chris Marusich
2019-02-18 14:38 ` Danny Milosavljevic
2019-05-24 13:55 ` Danny Milosavljevic
2019-07-19 5:53 ` Chris Marusich
2019-07-21 17:53 ` Ricardo Wurmus
2019-01-28 15:50 ` Danny Milosavljevic
2019-01-28 18:41 ` Ricardo Wurmus
2019-01-28 20:25 ` Danny Milosavljevic
2019-01-31 5:51 ` Mark H Weaver
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=87o97hz0ra.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--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.