* bug#29522: rustc-1.16.0 broken after jemalloc updated to 5.0.1
@ 2017-11-30 22:41 Adam Van Ymeren
2017-12-04 0:01 ` Jelle Licht
0 siblings, 1 reply; 6+ messages in thread
From: Adam Van Ymeren @ 2017-11-30 22:41 UTC (permalink / raw)
To: 29522
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#29522: rustc-1.16.0 broken after jemalloc updated to 5.0.1
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
0 siblings, 1 reply; 6+ messages in thread
From: Jelle Licht @ 2017-12-04 0:01 UTC (permalink / raw)
To: Adam Van Ymeren; +Cc: 29522
[-- 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 --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#29522: rustc-1.16.0 broken after jemalloc updated to 5.0.1
2017-12-04 0:01 ` Jelle Licht
@ 2017-12-04 9:09 ` Ludovic Courtès
2017-12-04 16:10 ` Adam Van Ymeren
0 siblings, 1 reply; 6+ messages in thread
From: Ludovic Courtès @ 2017-12-04 9:09 UTC (permalink / raw)
To: Jelle Licht; +Cc: Adam Van Ymeren, 29522
Hi,
Jelle Licht <jlicht@fsfe.org> skribis:
> 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.
Using a --disable-cxx variant of the latest jemalloc sounds preferable
to me over running an old jemalloc.
How does that sound?
Thanks,
Ludo’.
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#29522: rustc-1.16.0 broken after jemalloc updated to 5.0.1
2017-12-04 9:09 ` Ludovic Courtès
@ 2017-12-04 16:10 ` Adam Van Ymeren
2017-12-04 17:19 ` Ludovic Courtès
0 siblings, 1 reply; 6+ messages in thread
From: Adam Van Ymeren @ 2017-12-04 16:10 UTC (permalink / raw)
To: Ludovic Courtès; +Cc: Jelle Licht, 29522
ludo@gnu.org (Ludovic Courtès) writes:
> Hi,
>
> Jelle Licht <jlicht@fsfe.org> skribis:
>
>> 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.
>
> 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.
>
> How does that sound?
>
> Thanks,
> Ludo’.
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#29522: rustc-1.16.0 broken after jemalloc updated to 5.0.1
2017-12-04 16:10 ` Adam Van Ymeren
@ 2017-12-04 17:19 ` Ludovic Courtès
2017-12-04 19:35 ` Adam Van Ymeren
0 siblings, 1 reply; 6+ messages in thread
From: Ludovic Courtès @ 2017-12-04 17:19 UTC (permalink / raw)
To: Adam Van Ymeren; +Cc: Jelle Licht, 29522
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.
Ludo’.
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#29522: rustc-1.16.0 broken after jemalloc updated to 5.0.1
2017-12-04 17:19 ` Ludovic Courtès
@ 2017-12-04 19:35 ` Adam Van Ymeren
0 siblings, 0 replies; 6+ messages in thread
From: Adam Van Ymeren @ 2017-12-04 19:35 UTC (permalink / raw)
To: Ludovic Courtès; +Cc: Jelle Licht, 29522
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’.
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2017-12-04 19:36 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
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.