From: Danny Milosavljevic <dannym@scratchpost.org>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: 35519@debbugs.gnu.org, Marius Bakke <mbakke@fastmail.com>
Subject: bug#35519: guix master 4de63cf3fc0a831d75cb507456821104f24800c2: rust 1.19.0 build failure on i686-linux
Date: Sun, 20 Dec 2020 14:22:00 +0100 [thread overview]
Message-ID: <20201220142043.2049b1d9@scratchpost.org> (raw)
In-Reply-To: <877dpfkuq9.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 732 bytes --]
Hi,
On Fri, 18 Dec 2020 16:19:10 +0100
Mathieu Othacehe <othacehe@gnu.org> wrote:
> The CI is spending a considerable amount of time trying to build Rust
> packages for "i686-linux". As this is currently broken, what do you
> think about applying the attached patch?
Sure, for the time being.
But seriously, mrustc supports a lot of other architectures (including
defining custom architectures in config), and also can bootstrap Rust
1.29.0 directly. It's better to just update mrustc.
(Marius Bakke already tried to integrate the mrustc update to
core-updates--not sure what the roadblock was. Even if there was a
roadblock, mrustc upstream was committed to 7 days ago--maybe the roadblock
is gone now ?)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-12-20 13:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-01 3:43 bug#35519: librsvg broken on i686-linux Mark H Weaver
2019-05-10 12:53 ` Ricardo Wurmus
2019-05-11 0:00 ` Danny Milosavljevic
2019-05-11 8:03 ` Mark H Weaver
2019-05-11 14:16 ` Danny Milosavljevic
2019-05-11 14:08 ` Danny Milosavljevic
2019-09-16 12:24 ` Ludovic Courtès
2019-09-16 16:11 ` Danny Milosavljevic
2019-09-16 20:48 ` Ludovic Courtès
2020-03-18 20:45 ` bug#35519: guix master 4de63cf3fc0a831d75cb507456821104f24800c2: rust 1.19.0 build failure " Danny Milosavljevic
2020-12-18 15:19 ` Mathieu Othacehe
2020-12-20 13:22 ` Danny Milosavljevic [this message]
2021-10-19 21:44 ` bug#35519: Rust (and librsvg, IceCat, etc.) fails to build " scottworley
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=20201220142043.2049b1d9@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=35519@debbugs.gnu.org \
--cc=mbakke@fastmail.com \
--cc=othacehe@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 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).