From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-fs/duperemove/, sys-fs/duperemove/files/
Date: Mon, 23 Oct 2023 01:44:13 +0000 (UTC) [thread overview]
Message-ID: <1698024222.9d5e256f7ced00e674bfcb69b463d6a753e16202.sam@gentoo> (raw)
commit: 9d5e256f7ced00e674bfcb69b463d6a753e16202
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Mon Oct 23 01:23:42 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Oct 23 01:23:42 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9d5e256f
sys-fs/duperemove: fix musl build
Closes: https://bugs.gentoo.org/916078
Signed-off-by: Sam James <sam <AT> gentoo.org>
sys-fs/duperemove/duperemove-0.13.ebuild | 4 ++++
sys-fs/duperemove/files/duperemove-0.13-musl.patch | 23 ++++++++++++++++++++++
2 files changed, 27 insertions(+)
diff --git a/sys-fs/duperemove/duperemove-0.13.ebuild b/sys-fs/duperemove/duperemove-0.13.ebuild
index 82e6d1da0fdb..f984cc9d8e66 100644
--- a/sys-fs/duperemove/duperemove-0.13.ebuild
+++ b/sys-fs/duperemove/duperemove-0.13.ebuild
@@ -24,6 +24,10 @@ DEPEND="${RDEPEND}"
S=${WORKDIR}/${P/_/.}
+PATCHES=(
+ "${FILESDIR}"/${P}-musl.patch
+)
+
src_compile() {
emake VERSION="${PV}" IS_RELEASE=1 CC="$(tc-getCC)" CFLAGS="${CFLAGS} -Wall"
}
diff --git a/sys-fs/duperemove/files/duperemove-0.13-musl.patch b/sys-fs/duperemove/files/duperemove-0.13-musl.patch
new file mode 100644
index 000000000000..2fbf6782579f
--- /dev/null
+++ b/sys-fs/duperemove/files/duperemove-0.13-musl.patch
@@ -0,0 +1,23 @@
+https://bugs.gentoo.org/916078
+https://github.com/markfasheh/duperemove/issues/310
+https://github.com/markfasheh/duperemove/commit/b275a365545a45f317280153a43bf02a55f89de6
+
+From b275a365545a45f317280153a43bf02a55f89de6 Mon Sep 17 00:00:00 2001
+From: psykose <alice@ayaya.dev>
+Date: Thu, 12 Oct 2023 08:37:47 +0000
+Subject: [PATCH] dbfile: include <sys/types.h> for dev_t
+
+fixes build on musl
+
+closes #310
+--- a/dbfile.h
++++ b/dbfile.h
+@@ -5,6 +5,7 @@
+ #include <stdint.h>
+ #include <sqlite3.h>
+ #include <stdbool.h>
++#include <sys/types.h>
+ #include "util.h"
+
+ struct filerec;
+
next reply other threads:[~2023-10-23 1:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 1:44 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-13 12:38 [gentoo-commits] repo/gentoo:master commit in: sys-fs/duperemove/, sys-fs/duperemove/files/ Michał Górny
2023-11-21 18:06 Sam James
2018-09-06 21:22 Michał Górny
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=1698024222.9d5e256f7ced00e674bfcb69b463d6a753e16202.sam@gentoo \
--to=sam@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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