From: Vaelatern <Vaelatern@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] sysdig: upstream added musl support
Date: Fri, 11 Sep 2020 14:34:22 +0200 [thread overview]
Message-ID: <20200911123422.QJ7MCxj-BEW6cPNtDRGK3zM_YB6BisuMut6PkqbKX3o@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24830@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 488 bytes --]
There is an updated pull request by Vaelatern against master on the void-packages repository
https://github.com/Vaelatern/void-packages sysdig-now-supports-musl
https://github.com/void-linux/void-packages/pull/24830
sysdig: upstream added musl support
Will be active in the next release
upstream commits: https://github.com/draios/sysdig/pull/1682
73554b9c48b06612eb50494ee6fa5b779c57edc0
A patch file from https://github.com/void-linux/void-packages/pull/24830.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-sysdig-now-supports-musl-24830.patch --]
[-- Type: text/x-diff, Size: 1263 bytes --]
From cd3004641ed882e2fe3e9cc435677b1d83c7a116 Mon Sep 17 00:00:00 2001
From: Toyam Cox <Vaelatern@voidlinux.org>
Date: Fri, 11 Sep 2020 08:32:22 -0400
Subject: [PATCH] sysdig: upstream added musl support
Will be active in the next release
upstream commits: https://github.com/draios/sysdig/pull/1682
73554b9c48b06612eb50494ee6fa5b779c57edc0
---
srcpkgs/sysdig/template | 9 ++++++++-
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/srcpkgs/sysdig/template b/srcpkgs/sysdig/template
index ce4a214c03f..50e515a71ec 100644
--- a/srcpkgs/sysdig/template
+++ b/srcpkgs/sysdig/template
@@ -2,7 +2,7 @@
pkgname=sysdig
version=0.27.0
revision=2
-archs="i686 x86_64 ppc64le"
+archs="i686* x86_64* ppc64le*"
build_style=cmake
configure_args="-DSYSDIG_VERSION=${version} -DUSE_BUNDLED_DEPS=OFF
-DUSE_BUNDLED_B64=ON -DUSE_BUNDLED_JQ=ON -DBUILD_DRIVER=OFF
@@ -24,6 +24,10 @@ disable_parallel_build=yes
dkms_modules="sysdig ${version}"
nocross=yes
+case "$XBPS_TARGET_MACHINE" in
+ *-musl) configure_args+=" -DMUSL_OPTIMIZED_BUILD=On"
+esac
+
# Avoid excessive warnings spam to the log
CXXFLAGS="-Wno-deprecated-declarations"
@@ -40,3 +44,6 @@ post_install() {
vlicense COPYING
vlicense NOTICES
}
+
+# REMARKS:
+# Is there a reason no arm?
next prev parent reply other threads:[~2020-09-11 12:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 12:32 [PR PATCH] " Vaelatern
2020-09-11 12:34 ` Vaelatern [this message]
2020-10-05 8:33 ` [PR PATCH] [Closed]: " leahneukirchen
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=20200911123422.QJ7MCxj-BEW6cPNtDRGK3zM_YB6BisuMut6PkqbKX3o@z \
--to=vaelatern@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).