From 0d37a1ef234c38b27faba43bc3a22f985d311deb Mon Sep 17 00:00:00 2001 From: davidovski Date: Wed, 17 May 2023 17:01:27 +0100 Subject: Remove all firmware --- repo/fakeroot/do-not-redefine-id_t.patch | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 repo/fakeroot/do-not-redefine-id_t.patch (limited to 'repo/fakeroot/do-not-redefine-id_t.patch') diff --git a/repo/fakeroot/do-not-redefine-id_t.patch b/repo/fakeroot/do-not-redefine-id_t.patch new file mode 100644 index 0000000..4d3bab1 --- /dev/null +++ b/repo/fakeroot/do-not-redefine-id_t.patch @@ -0,0 +1,21 @@ +musl defines id_t as unsigned but doesn't use the _ID_T to detect its +definition. This causes the type to be redefined as an int by fakeroot +which causes a compilation error. + +diff -upr fakeroot-1.27.orig/libfakeroot.c fakeroot-1.27/libfakeroot.c +--- fakeroot-1.27.orig/libfakeroot.c 2022-01-30 11:30:25.198506844 +0100 ++++ fakeroot-1.27/libfakeroot.c 2022-01-30 11:30:41.928524429 +0100 +@@ -133,13 +133,6 @@ + #define INT_SEND_STAT(a,b) SEND_STAT(a,b,_STAT_VER) + #define INT_SEND_GET_XATTR(a,b) SEND_GET_XATTR(a,b,_STAT_VER) + #define INT_SEND_GET_STAT(a,b) SEND_GET_STAT(a,b) +- +-/* 10.10 uses id_t in getpriority/setpriority calls, so pretend +- id_t is used everywhere, just happens to be int on some OSes */ +-#ifndef _ID_T +-#define _ID_T +-typedef int id_t; +-#endif + #endif + + #include -- cgit v1.2.1