mailing list of musl libc
 help / color / mirror / code / Atom feed
From: M Farkas-Dyck <strake888@gmail.com>
To: musl@lists.openwall.com
Subject: Re: __xmknod, __sysv_signal
Date: Fri, 18 Apr 2014 22:11:02 -0500	[thread overview]
Message-ID: <CAL3m8eAubOeNBFt75L1HdKdksuM=kYpwE6Zyx4gzTwfYYOsh6Q@mail.gmail.com> (raw)
In-Reply-To: <20140419025204.GS26358@brightrain.aerifal.cx>

On 18/04/2014, Rich Felker <dalias@libc.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


  reply	other threads:[~2014-04-19  3:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-19  2:18 M Farkas-Dyck
2014-04-19  2:52 ` Rich Felker
2014-04-19  3:11   ` M Farkas-Dyck [this message]
2014-05-01  0:32     ` Rich Felker
2014-05-06 16:55       ` M Farkas-Dyck
2014-05-07  3:17         ` Rich Felker
2014-05-07 10:18           ` Rob Landley
2014-05-07 22:58             ` Rich Felker

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='CAL3m8eAubOeNBFt75L1HdKdksuM=kYpwE6Zyx4gzTwfYYOsh6Q@mail.gmail.com' \
    --to=strake888@gmail.com \
    --cc=musl@lists.openwall.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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).