From: "Ludovic Courtès" <ludo@gnu.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 35519@debbugs.gnu.org
Subject: bug#35519: librsvg broken on i686-linux
Date: Mon, 16 Sep 2019 22:48:42 +0200 [thread overview]
Message-ID: <877e682cid.fsf@gnu.org> (raw)
In-Reply-To: <20190916181141.40fdebe6@scratchpost.org> (Danny Milosavljevic's message of "Mon, 16 Sep 2019 18:11:41 +0200")
Hi Danny,
Danny Milosavljevic <dannym@scratchpost.org> skribis:
> 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.
What about giving them “guix pack mrustc”, or a guix-install.sh + pull
command sequence, or a VM image?
The instructions would be:
1. Download and run <https://guix.gnu.org/install.sh>. It will
perform the steps described at
<https://guix.gnu.org/manual/en/html_node/Binary-Installation.html>.
2. Write this to a file:
(list (channel
(name 'guix)
(url "https://git.savannah.gnu.org/git/guix.git")
(commit
"0b2ea78173f05c417a9002e52e2b36b139074124")))
3. Run ‘guix pull -C that-file.scm -p ~/core-updates’.
4. Run ‘~/core-updates/bin/guix build rust -s i686-linux -K’.
Investigate as per
<https://guix.gnu.org/manual/en/html_node/Debugging-Build-Failures.html>.
Perhaps you could propose them to do that, and if that’s too much to
ask, we can meet halfway somehow.
Of course we can also provide guidance on #guix on IRC.
WDYT?
> 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).
Would Valgrind or ASan be able to flag the potential issue?
Thanks,
Ludo’.
next prev parent reply other threads:[~2019-09-16 20:49 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 [this message]
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=877e682cid.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=35519@debbugs.gnu.org \
--cc=dannym@scratchpost.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).