public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: Florian Weimer <fweimer@redhat.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH] posix: Make posix_spawn extensions available by default
Date: Fri, 4 Nov 2022 09:04:04 -0300	[thread overview]
Message-ID: <65c25ce3-167b-bb91-bffb-a511d741b12e@linaro.org> (raw)
In-Reply-To: <875yfv2nsa.fsf@oldenburg.str.redhat.com>



On 04/11/22 04:15, Florian Weimer via Libc-alpha wrote:
> Some sources merely include <spawn.h> without -D_GNU_SOURCE and expect
> declarations for posix_spawn_file_actions_addchdir_np to be available.
> 
> Tested on x86_64-linux-gnu.
> 

LGTM, although you reference posix_spawn_file_actions_addchdir_np on commit
message, but you export posix_spawn_file_actions_addtcsetpgrp_np.

> ---
>  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
>  
> 
> base-commit: faaf733f49211439475e50f06716b303ee2644bf
> 

  reply	other threads:[~2022-11-04 12:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-04  7:15 Florian Weimer
2022-11-04 12:04 ` Adhemerval Zanella Netto [this message]
2022-11-04 12:10   ` Florian Weimer
2022-11-04 12:26     ` Adhemerval Zanella Netto
2022-11-06 21:26       ` Sam James
2022-11-07 16:10         ` Florian Weimer
2022-11-08  0:05           ` Sam James

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=65c25ce3-167b-bb91-bffb-a511d741b12e@linaro.org \
    --to=adhemerval.zanella@linaro.org \
    --cc=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).