From: Danny Milosavljevic <dannym@scratchpost.org>
To: Marius Bakke <mbakke@fastmail.com>
Cc: 38106@debbugs.gnu.org
Subject: [bug#38106] [PATCH] gnu: mrustc: Update to 0.8.1.
Date: Mon, 20 Jan 2020 20:12:45 +0100 [thread overview]
Message-ID: <20200120201245.6f716a2c@scratchpost.org> (raw)
In-Reply-To: <20200119231048.039dbad7@scratchpost.org>
[-- Attachment #1: Type: text/plain, Size: 760 bytes --]
Hi Marius,
I'm still not done with the 0.9 version.
The current problem is that a glibc update apparently removed <sys/ustat.h>--so
I would have to patch upstream rust@1.19.0
(rustc-1.19.0-src/src/compiler-rt/lib/sanitizer_common/sanitizer_platform_limits_posix.cc:163)
on staging.
Is that known already? Does Rust work on staging (without my changes)?
The 0.8.1 mrustc should work--but I don't have the free CPU/memory capacity to test it now.
I have an account on bayfront but cannot compile guix there (from manual checkout). I get:
error: failed to load 'guix/scripts/pack.scm':
ice-9/eval.scm:293:34: no binding `zip' to hide in module (gnu packages compression)
even after removing all .go files and removing ~/.cache/guile .
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-01-20 19:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 18:19 [bug#38106] [PATCH] gnu: mrustc: Update to 0.8.1 Danny Milosavljevic
2019-12-04 16:55 ` Ludovic Courtès
2019-12-04 18:31 ` Brett Gilio
2020-01-19 21:36 ` Marius Bakke
2020-01-19 22:11 ` Danny Milosavljevic
2020-01-20 19:12 ` Danny Milosavljevic [this message]
2020-01-20 19:45 ` Danny Milosavljevic
2020-01-21 7:35 ` bug#38106: " Danny Milosavljevic
2020-01-21 16:41 ` [bug#38106] " Marius Bakke
2020-01-21 16:47 ` Danny Milosavljevic
2020-01-21 20:23 ` Danny Milosavljevic
2020-01-21 21:29 ` Marius Bakke
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=20200120201245.6f716a2c@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=38106@debbugs.gnu.org \
--cc=mbakke@fastmail.com \
/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).