From mboxrd@z Thu Jan 1 00:00:00 1970 From: Danny Milosavljevic Subject: bug#35519: librsvg broken on i686-linux Date: Mon, 16 Sep 2019 18:11:41 +0200 Message-ID: <20190916181141.40fdebe6@scratchpost.org> References: <871s1ion48.fsf@netris.org> <87h8a2sc6j.fsf@elephly.net> <87pnk0bf8v.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/PLh5eK0_YKp0mFhNC4E_toX"; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:39266) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1i9tbh-0005rx-Mn for bug-guix@gnu.org; Mon, 16 Sep 2019 12:12:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1i9tbg-0003aA-HV for bug-guix@gnu.org; Mon, 16 Sep 2019 12:12:05 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:42080) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1i9tbg-0003a5-3Z for bug-guix@gnu.org; Mon, 16 Sep 2019 12:12:04 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1i9tbe-0003m0-4E for bug-guix@gnu.org; Mon, 16 Sep 2019 12:12:03 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87pnk0bf8v.fsf@gnu.org> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 35519@debbugs.gnu.org --Sig_/PLh5eK0_YKp0mFhNC4E_toX Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Ludo, On Mon, 16 Sep 2019 14:24:48 +0200 Ludovic Court=C3=A8s 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 (autho= rs of mrustc) a login to a Guix machine--therefore, the situation will not imp= rove. 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 thepowersga= ng 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 prob= lem with the struct layout (although I've checked the latter and it should be fine). --Sig_/PLh5eK0_YKp0mFhNC4E_toX Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEds7GsXJ0tGXALbPZ5xo1VCwwuqUFAl1/tD0ACgkQ5xo1VCww uqWJ1Af/fMLcbj/bUBkHbVNKpYbrU+46A8Yrnth9IMdnbByGw3FcUCAZt7khyHvJ U1wGLd4eG9iJxHxjMehWrckUia9d7OMg+WSNhdeHWL9cQ4vg/5TTr4yf63q/i/SC SD5f4cdWy+N7Eo4tkn3KcVkdQVmnrYfj7PIoiPaZ6aTXw1KlpCgIyEo9Pvc200g0 OTDly2IZkvM3YeJkBQ/QenOwu6TJ39PbGmvtsytfogloN16/ybxT7WHBrmM+MDiJ fXzPoDub3DuxFqstMslPvUfjdVrgNiZlClpUIo7YJiKNJxLTtVDafLvpq66aPi2x vPNDvh9P/31kZh1krORE4VGeii5rLw== =A47n -----END PGP SIGNATURE----- --Sig_/PLh5eK0_YKp0mFhNC4E_toX--