From: Danny Milosavljevic <dannym@scratchpost.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 35519@debbugs.gnu.org
Subject: bug#35519: librsvg broken on i686-linux
Date: Mon, 16 Sep 2019 18:11:41 +0200 [thread overview]
Message-ID: <20190916181141.40fdebe6@scratchpost.org> (raw)
In-Reply-To: <87pnk0bf8v.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1665 bytes --]
Hi Ludo,
On Mon, 16 Sep 2019 14:24:48 +0200
Ludovic Courtès <ludo@gnu.org> wrote:
> Does that ring a bell?
Yes, I've brought that up upstream and upstream is more than willing to work
on this and debug this problem if there is a system to debug it on.
However, as far as I understand we decided not to give thepowersgang (authors
of mrustc) a login to a Guix machine--therefore, the situation will not improve.
The problem is NOT reproducible in Debian with the same gcc version.
Maybe I'll get my home internet set up next month and put a Guix machine on it,
but right now I only have mobile internet (with very slow upload and behind NAT).
As it is now, I cannot reasonably give someone a Guix machine already setup
to debug this problem.
The problem is 100% reproducible and I estimate would be easy to fix for the
authors--and maybe would fix the similar armhf problems as well.
So if someone could put a Guix machine on the internet and give thepowersgang
access, that would be great. I can't right now.
If that happens, I can instruct thepowersgang how to enter an environment
where this problem can be reproduced and fixed.
Even at the last FOSDEM, Chris Marusich and I saw this problem and fixed
part of it--by now we got upstream attention. (After all this inertia maybe
we lost upstream attention again--we'll see)
> Any ideas of a fix or workaround we could apply?
No, but thepowersgang might find it very quickly. They guess it might be
some C undefined behavior being used by the mrustc->C translator, or a problem
with the struct layout (although I've checked the latter and it should be
fine).
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-09-16 16:12 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 [this message]
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
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=20190916181141.40fdebe6@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=35519@debbugs.gnu.org \
--cc=ludo@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).