From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) Subject: bug#29522: rustc-1.16.0 broken after jemalloc updated to 5.0.1 Date: Mon, 04 Dec 2017 18:19:32 +0100 Message-ID: <878teimmvv.fsf@gnu.org> References: <87h8tb4cf1.fsf@vany.ca> <878teirh99.fsf@gnu.org> <87d13uxyn1.fsf@vany.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41629) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eLuPV-00078z-Ot for bug-guix@gnu.org; Mon, 04 Dec 2017 12:20:11 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eLuPS-0001lA-Hs for bug-guix@gnu.org; Mon, 04 Dec 2017 12:20:05 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:37074) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eLuPS-0001l4-EA for bug-guix@gnu.org; Mon, 04 Dec 2017 12:20:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1eLuPS-0006At-7h for bug-guix@gnu.org; Mon, 04 Dec 2017 12:20:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87d13uxyn1.fsf@vany.ca> (Adam Van Ymeren's message of "Mon, 04 Dec 2017 11:10:10 -0500") 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: Adam Van Ymeren Cc: Jelle Licht , 29522@debbugs.gnu.org Adam Van Ymeren skribis: > ludo@gnu.org (Ludovic Court=C3=A8s) writes: > >> Hi, >> >> Jelle Licht skribis: [...] >>> It seems that the bundled copy of jemalloc in the rustc repo is current= ly >>> pinned at 4.5.0 partially >>> because of this specific issue as well. >>> >>> I did find an issue on the rust GH repo [0], and it seems this also aff= ects >>> the nix-rust project, >>> who seem to have the same errors as our currently failing build [1]. >>> >>> A temporary workaround could be to have a custom version of jemalloc wi= th >>> the c++ features disabled >>> by building with `--disable-cxx'. Alternatively, we could just make use= of >>> jemalloc 4.5.0 for rustc only >>> until this is all sorted our by upstream. >> >> Using a --disable-cxx variant of the latest jemalloc sounds preferable >> to me over running an old jemalloc. > > I feel like if rust is pegged at jemalloc 4.5.0 then that's what we > should be feeding it. The changelog suggestst that jemalloc 5 has some > pretty significant changes, changing rust to use that theoretically lead > to some subtle bugs, I feel like I'd rather wait for upstream to make > the upgrade themselves. Right, that makes sense. In that case, we should reintroduce jemalloc 4.5 and use that in Rust. Ludo=E2=80=99.