From: wangp <wangp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: mold: update to 2.4.1
Date: Sun, 03 Mar 2024 02:43:37 +0100 [thread overview]
Message-ID: <20240303014338.00F1A2BE12@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49046@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1187 bytes --]
New comment by wangp on void-packages repository
https://github.com/void-linux/void-packages/pull/49046#issuecomment-1974972605
Comment:
```diff
diff --git a/srcpkgs/mold/template b/srcpkgs/mold/template
index b759f84b962..d898e1b1119 100644
--- a/srcpkgs/mold/template
+++ b/srcpkgs/mold/template
@@ -3,10 +3,8 @@ pkgname=mold
version=2.4.1
revision=1
build_style=cmake
-configure_args="-DMOLD_USE_SYSTEM_MIMALLOC=ON
- -Dmimalloc_DIR=${XBPS_CROSS_BASE}/cmake/mimalloc-2.0
- -DMOLD_USE_SYSTEM_TBB=ON"
-makedepends="mimalloc-devel openssl-devel zlib-devel libzstd-devel tbb-devel"
+configure_args="-DMOLD_USE_SYSTEM_MIMALLOC=ON -DMOLD_USE_SYSTEM_TBB=ON"
+makedepends="mimalloc-devel zlib-devel libzstd-devel tbb-devel"
# It's probably not worth pulling in clang/llvm to run the few tests that
# depend on them.
checkdepends="tar zstd libdwarf gdb"
```
mold doesn't use openssl any more so you can remove `openssl-devel` (https://github.com/rui314/mold/issues/1088)
You can delete the `mimalloc_DIR` variable. The path doesn't exist in the current mimalloc package, so maybe it was never really necessary.
You can replace me as the maintainer if you like.
next prev parent reply other threads:[~2024-03-03 1:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-02 22:50 [PR PATCH] " cinerea0
2024-03-03 1:43 ` wangp [this message]
2024-03-05 19:01 ` [PR PATCH] [Updated] " cinerea0
2024-03-05 19:03 ` cinerea0
2024-03-07 18:22 ` [PR PATCH] [Merged]: " cinerea0
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=20240303014338.00F1A2BE12@inbox.vuxu.org \
--to=wangp@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).