From: Daniel =?unknown-8bit?q?D=C3=ADaz?= <daniel.diaz@linaro.org>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 1/3] Add header file lapi/signal.h
Date: Wed, 20 Feb 2019 09:34:10 -0600 [thread overview]
Message-ID: <20190220153412.18090-1-daniel.diaz@linaro.org> (raw)
Some libc implementations might differ in the definitions they
include. Exempli gratia: MUSL does not define __SIGRTMAX nor
__SIGRTMIN.
This header covers those differences for all tests that
require those definitions.
Signed-off-by: Daniel Díaz <daniel.diaz@linaro.org>
---
include/lapi/signal.h | 24 ++++++++++++++++++++++++
1 file changed, 24 insertions(+)
create mode 100644 include/lapi/signal.h
diff --git a/include/lapi/signal.h b/include/lapi/signal.h
new file mode 100644
index 000000000..d22965a94
--- /dev/null
+++ b/include/lapi/signal.h
@@ -0,0 +1,24 @@
+// SPDX-License-Identifier: GPL-2.0-or-later
+/*
+ * Copyright (c) 2019 Linaro Limited. All rights reserved.
+ * Author: Daniel Díaz <daniel.diaz@linaro.org>
+ */
+
+#ifndef LAPI_SIGNAL_H
+#define LAPI_SIGNAL_H
+
+#include <signal.h>
+
+/*
+ * Some libc implementations might differ in the definitions they include. This
+ * covers those differences for all tests to successfully build.
+ */
+
+#ifndef __SIGRTMIN
+# define __SIGRTMIN 32
+#endif
+#ifndef __SIGRTMAX
+# define __SIGRTMAX (_NSIG - 1)
+#endif
+
+#endif
--
2.17.1
next reply other threads:[~2019-02-20 15:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 15:34 Daniel =?unknown-8bit?q?D=C3=ADaz?= [this message]
2019-02-20 15:34 ` [LTP] [PATCH 2/3] syscalls/sighold02: Include lapi/signal.h for __SIGRT{MIN, MAX} Daniel =?unknown-8bit?q?D=C3=ADaz?=
2019-02-20 15:34 ` [LTP] [PATCH 3/3] syscalls/ptrace05: " Daniel =?unknown-8bit?q?D=C3=ADaz?=
2019-02-20 16:33 ` Petr Vorel
2019-02-20 16:48 ` Daniel =?unknown-8bit?q?D=C3=ADaz?=
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=20190220153412.18090-1-daniel.diaz@linaro.org \
--to=daniel.diaz@linaro.org \
--cc=ltp@lists.linux.it \
/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