From: Herman Rimm via Guix-patches via <guix-patches@gnu.org>
To: 75098@debbugs.gnu.org
Cc: Efraim Flashner <efraim@flashner.co.il>
Subject: [bug#75098] [PATCH rust-team 1/2] gnu: rust-tikv-jemalloc-sys-0.6: Use override-jemalloc phases.
Date: Wed, 25 Dec 2024 21:35:45 +0100 [thread overview]
Message-ID: <3b9879c4b8ba7850b0d39cd03f110bffccdacfb3.1735158599.git.herman@rimm.ee> (raw)
In-Reply-To: <cover.1735158599.git.herman@rimm.ee>
* gnu/packages/crates-io.scm (rust-tikv-jemalloc-sys-0.6): Adjust.
Change-Id: I579e7ac913f5b5123ee29ebd0889fea2ab18e363
---
gnu/packages/crates-io.scm | 11 +----------
1 file changed, 1 insertion(+), 10 deletions(-)
diff --git a/gnu/packages/crates-io.scm b/gnu/packages/crates-io.scm
index 13d222c5de..58cfd7f1c8 100644
--- a/gnu/packages/crates-io.scm
+++ b/gnu/packages/crates-io.scm
@@ -88910,16 +88910,7 @@ (define-public rust-tikv-jemalloc-sys-0.6
(arguments
`(#:cargo-inputs (("rust-cc" ,rust-cc-1)
("rust-libc" ,rust-libc-0.2))
- #:phases
- (modify-phases %standard-phases
- (add-after 'configure 'override-jemalloc
- (lambda* (#:key inputs #:allow-other-keys)
- (let ((jemalloc (assoc-ref inputs "jemalloc")))
- ;; This flag is needed when not using the bundled jemalloc.
- ;; https://github.com/tikv/jemallocator/issues/19
- (setenv "CARGO_FEATURE_UNPREFIXED_MALLOC_ON_SUPPORTED_PLATFORMS" "1")
- (setenv "JEMALLOC_OVERRIDE"
- (string-append jemalloc "/lib/libjemalloc_pic.a"))))))))
+ #:phases ,override-jemalloc))
(inputs (list jemalloc))
(home-page "https://github.com/tikv/jemallocator")
(synopsis "Rust FFI bindings to jemalloc")
--
2.45.2
next prev parent reply other threads:[~2024-12-25 20:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-25 20:34 [bug#75098] [PATCH rust-team 0/2] Use override-jemalloc Herman Rimm via Guix-patches via
2024-12-25 20:35 ` Herman Rimm via Guix-patches via [this message]
2024-12-25 20:35 ` [bug#75098] [PATCH rust-team 2/2] gnu: rust-tikv-jemallocator-0.6: Use override-jemalloc phases Herman Rimm 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=3b9879c4b8ba7850b0d39cd03f110bffccdacfb3.1735158599.git.herman@rimm.ee \
--to=guix-patches@gnu.org \
--cc=75098@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
--cc=herman@rimm.ee \
/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).