From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ludovic =?UTF-8?Q?Court=C3=A8s?= <ludo@gnu.org>
Subject: bug#35519: librsvg broken on i686-linux
Date: Mon, 16 Sep 2019 22:48:42 +0200
Message-ID: <877e682cid.fsf@gnu.org>
References: <871s1ion48.fsf@netris.org> <87h8a2sc6j.fsf@elephly.net>
 <87pnk0bf8v.fsf@gnu.org> <20190916181141.40fdebe6@scratchpost.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:470:142:3::10]:55883)
 by lists.gnu.org with esmtp (Exim 4.90_1)
 (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1i9xvj-0007UT-BN
 for bug-guix@gnu.org; Mon, 16 Sep 2019 16:49:04 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
 (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1i9xvi-0002BH-0j
 for bug-guix@gnu.org; Mon, 16 Sep 2019 16:49:03 -0400
Received: from debbugs.gnu.org ([209.51.188.43]:42331)
 by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
 (Exim 4.71) (envelope-from <Debian-debbugs@debbugs.gnu.org>)
 id 1i9xvh-0002BB-SW
 for bug-guix@gnu.org; Mon, 16 Sep 2019 16:49:01 -0400
Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2)
 (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1i9xvh-0000ju-Nl
 for bug-guix@gnu.org; Mon, 16 Sep 2019 16:49:01 -0400
Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
Resent-Message-ID: <handler.35519.B35519.15686669332818@debbugs.gnu.org>
In-Reply-To: <20190916181141.40fdebe6@scratchpost.org> (Danny Milosavljevic's
 message of "Mon, 16 Sep 2019 18:11:41 +0200")
List-Id: Bug reports for GNU Guix <bug-guix.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-guix>,
 <mailto:bug-guix-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/bug-guix>
List-Post: <mailto:bug-guix@gnu.org>
List-Help: <mailto:bug-guix-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-guix>,
 <mailto:bug-guix-request@gnu.org?subject=subscribe>
Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org
Sender: "bug-Guix" <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 35519@debbugs.gnu.org

Hi Danny,

Danny Milosavljevic <dannym@scratchpost.org> skribis:

> Yes, I've brought that up upstream and upstream is more than willing to w=
ork
> 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 (aut=
hors
> of mrustc) a login to a Guix machine--therefore, the situation will not i=
mprove.

What about giving them =E2=80=9Cguix pack mrustc=E2=80=9D, or a guix-instal=
l.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 =E2=80=98guix pull -C that-file.scm -p ~/core-updates=E2=80=99.

  4. Run =E2=80=98~/core-updates/bin/guix build rust -s i686-linux -K=E2=80=
=99.
     Investigate as per
     <https://guix.gnu.org/manual/en/html_node/Debugging-Build-Failures.htm=
l>.

Perhaps you could propose them to do that, and if that=E2=80=99s 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 pr=
oblem
> 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=E2=80=99.