[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL3m8eAubOeNBFt75L1HdKdksuM=kYpwE6Zyx4gzTwfYYOsh6Q@mail.gmail.com>
Date: Fri, 18 Apr 2014 22:11:02 -0500
From: M Farkas-Dyck <strake888@...il.com>
To: musl@...ts.openwall.com
Subject: Re: __xmknod, __sysv_signal
On 18/04/2014, Rich Felker <dalias@...c.org> wrote:
> For __xmknod, I think this is just the ABI symbol glibc uses for
> mknod, and we could certainly add it (though I question whether there
> are any useful programs using it that couldn't just be rebuilt against
> musl).
I wish to build ghc against musl, but it's like making yogurt: I need
ghc to build ghc, and the ghc folks in their great wisdom distribute
binaries... dynamic-linked against GNU turds.
I myself doubt whether we ought to include them and pollute the ABI,
but I thought that others might be in a like situation, which is why I
ask. I am now using ghc with a locally-patched musl, so I hope to not
need these symbols further myself, but the ultimate choice is yours.
---
src/stat/__xmknod.c | 6 ++++++
1 file changed, 6 insertions(+)
create mode 100644 src/stat/__xmknod.c
diff --git a/src/stat/__xmknod.c b/src/stat/__xmknod.c
new file mode 100644
index 0000000..62499de
--- /dev/null
+++ b/src/stat/__xmknod.c
@@ -0,0 +1,6 @@
+#include <sys/stat.h>
+
+int __xmknod(int ver, const char *path, mode_t mode, dev_t *dev)
+{
+ return mknod (path, mode, dev);
+}
--
1.8.5.2
---
src/signal/signal.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/src/signal/signal.c b/src/signal/signal.c
index c0f063e..29e03c8 100644
--- a/src/signal/signal.c
+++ b/src/signal/signal.c
@@ -13,3 +13,4 @@ void (*signal(int sig, void (*func)(int)))(int)
}
weak_alias(signal, bsd_signal);
+weak_alias(signal, __sysv_signal);
--
1.8.5.2
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
