From: Danny Milosavljevic <dannym@scratchpost.org>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: librsvg & Rust
Date: Fri, 8 Mar 2019 02:52:05 +0100 [thread overview]
Message-ID: <20190308025205.1b5f4b8a@scratchpost.org> (raw)
In-Reply-To: <87tvgfd0ce.fsf@netris.org>
[-- Attachment #1: Type: text/plain, Size: 707 bytes --]
Hi Mark,
On Wed, 06 Mar 2019 18:55:18 -0500
Mark H Weaver <mhw@netris.org> wrote:
> Marius Bakke <mbakke@fastmail.com> writes:
> > I wanted to ask about this: is Rust supported on all the platforms we
> > support at the moment?
>
> On hydra.gnu.org, our rust packages can only successfully be built on
> x86_64-linux. They fail to build on i686-linux and armhf-linux. I
> don't know about aarch64-linux.
Right.
I've talked to upstream and they acknowledge that there is a problem
but they haven't found it yet.
Since there was no improvement in a reasonable time frame, let's
re-add a binary-only bootstrap rust and use it in case of non-x86_64
in order to have working rust.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-03-08 1:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190220161027.17460.87383@vcs0.savannah.gnu.org>
[not found] ` <20190220161038.3F54B2040C@vcs0.savannah.gnu.org>
2019-03-06 11:05 ` librsvg & Rust Ludovic Courtès
2019-03-06 15:46 ` Marius Bakke
2019-03-06 16:24 ` ng0
2019-03-06 23:55 ` Mark H Weaver
2019-03-07 20:12 ` Efraim Flashner
2019-03-08 1:52 ` Danny Milosavljevic [this message]
2019-03-08 2:17 ` Danny Milosavljevic
2019-03-15 11:27 ` Ludovic Courtès
2019-03-15 11:29 ` Ludovic Courtès
2019-03-15 13:39 ` Marius Bakke
2019-03-15 15:14 ` Ivan Petkov
2019-03-23 16:53 ` Ludovic Courtès
2019-03-23 22:44 ` Marius Bakke
2019-04-03 21:30 ` Ludovic Courtès
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=20190308025205.1b5f4b8a@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=guix-devel@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 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).