unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Ryan Sundberg <ryan@arctype.co>
Cc: 49167-done@debbugs.gnu.org
Subject: bug#49167: [PATCH core-updates] gnu: jemalloc: --disable-initial-exec-tls
Date: Fri, 03 Sep 2021 12:06:25 +0200	[thread overview]
Message-ID: <87k0jy2cta.fsf_-_@gnu.org> (raw)
In-Reply-To: <bfa98853-d450-8d6b-1ace-2f88335af50d@arctype.co> (Ryan Sundberg's message of "Mon, 21 Jun 2021 22:58:24 -0700")

Hi Ryan,

Ryan Sundberg <ryan@arctype.co> skribis:

> From 8b97b60ab78ba1e616efaf477e629cfa2457b1a9 Mon Sep 17 00:00:00 2001
> From: Ryan Sundberg <ryan@arctype.co>
> Date: Fri, 29 Jan 2021 21:18:56 -0800
> Subject: [PATCH] gnu: jemalloc: --disable-initial-exec-tls
>
> Disable the thread local storage model in jemalloc 5 to prevent
> shared libraries linked to libjemalloc from crashing on dlopen().
> https://github.com/jemalloc/jemalloc/issues/937
>
> This bug affects both Java JNI and python libraries which link to
> jemalloc 5, such as RocksDB, which will crash the program when loaded.
>
> * gnu/packages/jemalloc.scm (jemalloc)[arguments]: Add --disable-initial-exec-tls
> configure flag.

It took a long while, but it’s now in ‘core-updates-frozen’ as
68dd6d809398297dc2ebef522186c9b9f2566739 (with minor tweaks so it would
apply and so that ‘jemalloc-4.5.0’ remains public.)

Thanks!

Ludo’.




  reply	other threads:[~2021-09-03 10:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-22  5:44 [bug#49167] [PATCH core-updates] gnu: jemalloc: --disable-initial-exec-tls Ryan Sundberg via Guix-patches via
2021-06-22  5:52 ` Ryan Sundberg via Guix-patches via
2021-06-22  5:58   ` Ryan Sundberg via Guix-patches via
2021-09-03 10:06     ` Ludovic Courtès [this message]
     [not found] ` <handler.49167.D49167.16306636041607.notifdone@debbugs.gnu.org>
2021-09-04 23:40   ` [bug#49167] closed (Re: bug#49167: [PATCH core-updates] gnu: jemalloc: --disable-initial-exec-tls) Ryan Sundberg via Guix-patches via

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k0jy2cta.fsf_-_@gnu.org \
    --to=ludo@gnu.org \
    --cc=49167-done@debbugs.gnu.org \
    --cc=ryan@arctype.co \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).