From: Florian Weimer <fweimer@redhat.com>
To: libc-alpha@sourceware.org
Subject: [PATCH] <signal.h>: Add deprecation message for sigpause
Date: Mon, 12 Dec 2022 11:43:45 +0100 [thread overview]
Message-ID: <87r0x4ucke.fsf@oldenburg.str.redhat.com> (raw)
Current compilers merely issue an implicit function declaration warning
without -D_XOPEN_SOURCE_EXTENDED, which is not very illuminating.
Tested on i686-linux-gnu and x86_64-linux-gnu.
---
signal/signal.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/signal/signal.h b/signal/signal.h
index 78d0d819aa..1299d7e0bc 100644
--- a/signal/signal.h
+++ b/signal/signal.h
@@ -155,6 +155,9 @@ extern int __sigpause (int __sig_or_mask, int __is_sig);
/* Remove a signal from the signal mask and suspend the process. */
# define sigpause(sig) __sigpause ((sig), 1)
# endif
+#elif defined __USE_MISC
+extern int sigpause (int __sig)
+ __attribute_deprecated_msg__ ("Use the sigsuspend function instead");
#endif
base-commit: 4e21c2075193e406a92c0d1cb091a7c804fda4d9
next reply other threads:[~2022-12-12 10:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 10:43 Florian Weimer [this message]
2023-01-05 17:25 ` Florian Weimer
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=87r0x4ucke.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=libc-alpha@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).