From: Adam Van Ymeren <adam@vany.ca>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Jelle Licht <jlicht@fsfe.org>, 29522@debbugs.gnu.org
Subject: bug#29522: rustc-1.16.0 broken after jemalloc updated to 5.0.1
Date: Mon, 04 Dec 2017 14:35:07 -0500 [thread overview]
Message-ID: <878teixp5g.fsf@vany.ca> (raw)
In-Reply-To: <878teimmvv.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Mon, 04 Dec 2017 18:19:32 +0100")
ludo@gnu.org (Ludovic Courtès) writes:
> Adam Van Ymeren <adam@vany.ca> skribis:
>
>> ludo@gnu.org (Ludovic Courtès) writes:
>>
>>> Hi,
>>>
>>> Jelle Licht <jlicht@fsfe.org> skribis:
>
> [...]
>
>>>> It seems that the bundled copy of jemalloc in the rustc repo is currently
>>>> 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 affects
>>>> 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 with
>>>> 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.
Sounds good, I have a patch that does this and also bumps rust to latest
upstream, but the build is taking forever. Will post once I've built it
successfully.
>
> Ludo’.
prev parent reply other threads:[~2017-12-04 19:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 22:41 bug#29522: rustc-1.16.0 broken after jemalloc updated to 5.0.1 Adam Van Ymeren
2017-12-04 0:01 ` Jelle Licht
2017-12-04 9:09 ` Ludovic Courtès
2017-12-04 16:10 ` Adam Van Ymeren
2017-12-04 17:19 ` Ludovic Courtès
2017-12-04 19:35 ` Adam Van Ymeren [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878teixp5g.fsf@vany.ca \
--to=adam@vany.ca \
--cc=29522@debbugs.gnu.org \
--cc=jlicht@fsfe.org \
--cc=ludo@gnu.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.