public inbox for glibc-cvs@sourceware.org help / color / mirror / Atom feed
From: Florian Weimer <fw@sourceware.org> To: glibc-cvs@sourceware.org Subject: [glibc] posix: Make posix_spawn extensions available by default Date: Fri, 4 Nov 2022 12:30:37 +0000 (GMT) [thread overview] Message-ID: <20221104123037.42B57385841B@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=2ff48a4025515e93d722947a9eabb114f4a65b22 commit 2ff48a4025515e93d722947a9eabb114f4a65b22 Author: Florian Weimer <fweimer@redhat.com> Date: Fri Nov 4 07:43:59 2022 +0100 posix: Make posix_spawn extensions available by default Some sources merely include <spawn.h> without -D_GNU_SOURCE and expect declarations for posix_spawn_file_actions_addchdir_np to be available. For consistency, declare posix_spawn_file_actions_addfchdir_np, posix_spawn_file_actions_addclosefrom_np, posix_spawn_file_actions_addtcsetpgrp_np as well. Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org> Diff: --- posix/spawn.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/posix/spawn.h b/posix/spawn.h index c4a81227b0..f3bcbc56be 100644 --- a/posix/spawn.h +++ b/posix/spawn.h @@ -198,7 +198,7 @@ extern int posix_spawn_file_actions_adddup2 (posix_spawn_file_actions_t * int __fd, int __newfd) __THROW __nonnull ((1)); -#ifdef __USE_GNU +#ifdef __USE_MISC /* Add an action changing the directory to PATH during spawn. This affects the subsequent file actions. */ extern int posix_spawn_file_actions_addchdir_np (posix_spawn_file_actions_t * @@ -227,7 +227,7 @@ posix_spawn_file_actions_addtcsetpgrp_np (posix_spawn_file_actions_t *, int __tcfd) __THROW __nonnull ((1)); -#endif +#endif /* __USE_MISC */ __END_DECLS
reply other threads:[~2022-11-04 12:30 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20221104123037.42B57385841B@sourceware.org \ --to=fw@sourceware.org \ --cc=glibc-cvs@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: linkBe 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).