#35519 Rust (and librsvg, IceCat, etc.) fails to build on i686-linux

Message #27 received at 35519@debbugs.gnu.org (full text, mbox, reply):

Received: (at 35519) by debbugs.gnu.org; 16 Sep 2019 12:25:00 +0000
From debbugs-submit-bounces@debbugs.gnu.org Mon Sep 16 08:25:00 2019
Received: from localhost ([127.0.0.1]:49344 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces@debbugs.gnu.org>)
	id 1i9q3w-00089o-Bq
	for submit@debbugs.gnu.org; Mon, 16 Sep 2019 08:25:00 -0400
Received: from eggs.gnu.org ([209.51.188.92]:52390)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <ludo@gnu.org>) id 1i9q3v-00089d-8y
 for 35519@debbugs.gnu.org; Mon, 16 Sep 2019 08:24:59 -0400
Received: from fencepost.gnu.org ([2001:470:142:3::e]:49816)
 by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from <ludo@gnu.org>)
 id 1i9q3p-0000dK-E4; Mon, 16 Sep 2019 08:24:53 -0400
Received: from [2001:660:6102:320:e120:2c8f:8909:cdfe] (port=47742 helo=ribbon)
 by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256)
 (Exim 4.82) (envelope-from <ludo@gnu.org>)
 id 1i9q3o-0002wK-TO; Mon, 16 Sep 2019 08:24:53 -0400
From: Ludovic Courtès <ludo@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Subject: Re: bug#35519: librsvg broken on i686-linux
References: <871s1ion48.fsf@netris.org> <87h8a2sc6j.fsf@elephly.net>
Date: Mon, 16 Sep 2019 14:24:48 +0200
In-Reply-To: <87h8a2sc6j.fsf@elephly.net> (Ricardo Wurmus's message of "Fri,
 10 May 2019 14:53:40 +0200")
Message-ID: <87pnk0bf8v.fsf@gnu.org>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-Spam-Score: -2.3 (--)
X-Debbugs-Envelope-To: 35519
Cc: 35519@debbugs.gnu.org, Danny Milosavljevic <dannym@scratchpost.org>
X-BeenThere: debbugs-submit@debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request@debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit@debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request@debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request@debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces@debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
X-Spam-Score: -3.3 (---)

Hello Danny and all,

Ricardo Wurmus <rekado@elephly.net> skribis:

>> Hydra failed to build librsvg on i686-linux, because it depends on Rust
>> which is still broken on i686-linux in Guix.
>
> Danny opened a bug report with the mrustc upstream:
>
>     https://github.com/thepowersgang/mrustc/issues/108
>
> The last message there tells us to try again with current HEAD on
> master.  If this fails I think it’s acceptable to use a binary for the
> very first Rust on i686; we would skip the use of mrustc on i686 then.
> Not great.

I don’t know if it relates but on current ‘core-updates’ Rust 1.19 fails
to build on i686:

--8<---------------cut here---------------start------------->8---
BUILDING curl_sys from curl-sys v0.3.11 with features []
> /gnu/store/2fh0bz69j6gxpgj5nqiqplwmck1dvi47-mrustc-0.8.0/bin/mrustc src/vendor/curl-sys/lib.rs --crate-name curl_sys --crate-type rlib --crate-tag 0_3_11 -g --cfg debug_assertions -O -o output/cargo-build/libcurl_sys-0_3_11.hir -L output/cargo-build -L /gnu/store/44sdci2mizpvd70zyvbfs9ai0maw255z-curl-7.65.3/lib -l curl --extern libz_sys=output/cargo-build/liblibz_sys-1_0_13.hir --extern libc=output/cargo-build/liblibc-0_2_22.hir --extern openssl_sys=output/cargo-build/libopenssl_sys-0_9_12.hir -L output -L /gnu/store/2fh0bz69j6gxpgj5nqiqplwmck1dvi47-mrustc-0.8.0/lib/mrust
BUILDING curl from curl v0.4.6 with features []
> /gnu/store/2fh0bz69j6gxpgj5nqiqplwmck1dvi47-mrustc-0.8.0/bin/mrustc src/vendor/curl/src/lib.rs --crate-name curl --crate-type rlib --crate-tag 0_4_6 -g --cfg debug_assertions -O -o output/cargo-build/libcurl-0_4_6.hir -L output/cargo-build --extern libc=output/cargo-build/liblibc-0_2_22.hir --extern curl_sys=output/cargo-build/libcurl_sys-0_3_11.hir --extern openssl_sys=output/cargo-build/libopenssl_sys-0_9_12.hir --extern openssl_probe=output/cargo-build/libopenssl_probe-0_1_1.hir -L output -L /gnu/store/2fh0bz69j6gxpgj5nqiqplwmck1dvi47-mrustc-0.8.0/lib/mrust
BUILDING crates_io from crates-io v0.9.0 with features []
> /gnu/store/2fh0bz69j6gxpgj5nqiqplwmck1dvi47-mrustc-0.8.0/bin/mrustc src/tools/cargo/src/crates-io/lib.rs --crate-name crates_io --crate-type rlib --crate-tag 0_9_0 -g --cfg debug_assertions -O -o output/cargo-build/libcrates_io-0_9_0.hir -L output/cargo-build --extern curl=output/cargo-build/libcurl-0_4_6.hir --extern error_chain=output/cargo-build/liberror_chain-0_10_0.hir --extern serde=output/cargo-build/libserde-1_0_6.hir --extern serde_derive=output/cargo-build/libserde_derive-1_0_6.hir --extern serde_json=output/cargo-build/libserde_json-1_0_2.hir --extern url=output/cargo-build/liburl-1_4_0.hir -L output -L /gnu/store/2fh0bz69j6gxpgj5nqiqplwmck1dvi47-mrustc-0.8.0/lib/mrust
munmap_chunk(): invalid pointer
src/tools/cargo/src/crates-io/lib.rs:65: BUG:src/expand/proc_macro.cpp:941: Unexpected EOF while reading from child process
BUILD FAILED
command "/gnu/store/2fh0bz69j6gxpgj5nqiqplwmck1dvi47-mrustc-0.8.0/tools/bin/minicargo" "src/tools/cargo" "--vendor-dir" "src/vendor" "--output-dir" "output/cargo-build" "-L" "output/" "-L" "/gnu/store/2fh0bz69j6gxpgj5nqiqplwmck1dvi47-mrustc-0.8.0/lib/mrust" "-j" "1" failed with status 1
builder for `/gnu/store/01mh2n7mif0k49ivj6y3fdq1ssj3d2lq-rust-1.19.0.drv' failed with exit code 1
--8<---------------cut here---------------end--------------->8---

(From
<https://ci.guix.gnu.org/log/cnxzabs1mi42rfvz8gp34lqap0dwi9l6-rust-1.19.0-cargo>.)

Does that ring a bell?  Any ideas of a fix or workaround we could apply?

It’d be great if we could merge ‘core-updates’ soon.  This is
unfortunately not a regression compared to ‘master’, so I don’t think
this is a blocker.

Thoughts?

Ludo’.

Send a report that this bug log contains spam.