From: Danny Milosavljevic <dannym@scratchpost.org>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Rust 1.19 fails to build on i686 on ‘staging’
Date: Mon, 11 Feb 2019 22:34:56 +0100 [thread overview]
Message-ID: <20190211223456.0779cf68@scratchpost.org> (raw)
In-Reply-To: <20190205123510.510731a6@scratchpost.org>
[-- Attachment #1: Type: text/plain, Size: 3043 bytes --]
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
>Hmm... works for me, using gcc (Debian 6.3.0-18+deb9u1) 6.3.0 20170516 on linux 4.9.0-8-686-pae
>Compiling cargo ran sucessfully.
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?
My laptop is currently trying to survive the merge of staging to master and keeps
running out of memory if I try to start a rust build in parallel, even with swap.
The patch to use mrustc master is:
diff --git a/gnu/packages/rust.scm b/gnu/packages/rust.scm
index e128bb22b..f2a01ded6 100644
--- a/gnu/packages/rust.scm
+++ b/gnu/packages/rust.scm
@@ -97,17 +97,35 @@
(package
(name "mrustc")
(version "0.8.0")
+ ;(source (origin
+ ; (method git-fetch)
+ ; (uri (git-reference
+ ; (url "https://github.com/thepowersgang/mrustc.git")
+ ; (commit (string-append "v" version))))
+ ; (file-name (git-file-name name version))
+ ; (sha256
+ ; (base32
+ ; "0a7v8ccyzp1sdkwni8h1698hxpfz2sxhcpx42n6l2pbm0rbjp08i"))
+ ; (patches
+ ; (search-patches "mrustc-0.8.0-fix-use-after-free.patch"
+ ; "mrustc-0.8.0-fix-variable-length-integer-receiving.patch"
+ ; "mrustc-0.8.0-fix-emulated-i128-multiply-divide.patch"
+ ; "mrustc-0.8.0-fix-i128-overflow-handling.patch"))))
(source (origin
(method git-fetch)
(uri (git-reference
(url "https://github.com/thepowersgang/mrustc.git")
- (commit (string-append "v" version))))
+ (commit "7b6fa5c6e7d6838c2479280dd3f8d14a43c13899")))
(file-name (git-file-name name version))
(sha256
(base32
- "0a7v8ccyzp1sdkwni8h1698hxpfz2sxhcpx42n6l2pbm0rbjp08i"))
+ "0ki5jv76gmvd0q9y2lixzn4xhy1jamba3f77bk8cz2k4ix6yx5z1"))
(patches
- (search-patches "mrustc-0.8.0-fix-variable-length-integer-receiving.patch"))))
+ (search-patches ;"mrustc-0.8.0-fix-use-after-free.patch"
+ ;"mrustc-0.8.0-fix-variable-length-integer-receiving.patch"
+ ;"mrustc-0.8.0-fix-emulated-i128-multiply-divide.patch"
+ ;"mrustc-0.8.0-fix-i128-overflow-handling.patch"
+ ))))
Also have to make rust@1.19.0 public or use an "-e" expression.
If you don't have time, no worries, I'll eventually get to it.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-02-11 21:35 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 [this message]
2019-02-12 11:47 ` Chris Marusich
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=20190211223456.0779cf68@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=cmmarusich@gmail.com \
--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.