From: Jelle Licht <jlicht@fsfe.org>
To: Adam Van Ymeren <adam@vany.ca>
Cc: 29522@debbugs.gnu.org
Subject: bug#29522: rustc-1.16.0 broken after jemalloc updated to 5.0.1
Date: Mon, 4 Dec 2017 01:01:29 +0100 [thread overview]
Message-ID: <CAPsKtf+A0cH3GhGtNgz8309odVVdsAUPC78PmZBiBD8xyKFuOQ@mail.gmail.com> (raw)
In-Reply-To: <87h8tb4cf1.fsf@vany.ca>
[-- Attachment #1: Type: text/plain, Size: 1144 bytes --]
2017-11-30 23:41 GMT+01:00 Adam Van Ymeren <adam@vany.ca>:
> I haven't had time to dig in to this further, but in case anyone wants
> to fix rustc-1.16.0, it's broken after the upgrade of jemalloc to 5.0.1.
>
> Reverting commit 475b99fa5cf402430aa93a40e406e854ad2ff6e4 which reverts
> jemalloc back to 4.5.0 causes rustc to build successfully again. It has
> been broken for some time.
>
> https://hydra.gnu.org/job/gnu/master/rustc-1.16.0.x86_64-linux
>
>
>
>
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.
[0]: https://github.com/rust-lang/rust/issues/43586
[1]: https://gist.github.com/marmistrz/a6e503a5491df80a493030e0a0e702d2
[-- Attachment #2: Type: text/html, Size: 1951 bytes --]
next prev parent reply other threads:[~2017-12-04 0:02 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 [this message]
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
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=CAPsKtf+A0cH3GhGtNgz8309odVVdsAUPC78PmZBiBD8xyKFuOQ@mail.gmail.com \
--to=jlicht@fsfe.org \
--cc=29522@debbugs.gnu.org \
--cc=adam@vany.ca \
/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.