public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Sam James <sam@gentoo.org>
To: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>,
	Florian Weimer <fweimer@redhat.com>
Cc: Carlos O'Donell via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH] posix: Make posix_spawn extensions available by default
Date: Sun, 6 Nov 2022 21:26:41 +0000	[thread overview]
Message-ID: <F9A97449-234A-4B8B-9529-627493CA65DA@gentoo.org> (raw)
In-Reply-To: <78b07982-0bee-074a-e491-ab3d844c68f8@linaro.org>

[-- Attachment #1: Type: text/plain, Size: 1610 bytes --]



> On 4 Nov 2022, at 12:26, Adhemerval Zanella Netto via Libc-alpha <libc-alpha@sourceware.org> wrote:
> 
> 
> 
> On 04/11/22 09:10, Florian Weimer wrote:
>> * Adhemerval Zanella Netto:
>> 
>>> 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.
>> 
>> Sorry, there are multiple functions that are now available by default.
>> I encountered the problem just with posix_spawn_file_actions_addchdir_np,
>> so I still think the commit message is correct.
> 
> I would advise cite all the function affected then, because with only
> posix_spawn_file_actions_addchdir_np on commit message it might seems that
> the patch is exporting more than intended.
> 

Agreed. I'm a little bit uneasy given this ends up masking some problems
and then we're back to having to only fix them on musl systems, but if
this is the only function not exposed and the logic already applies to the others,
I guess it's fine.

(In particular, there's various functions from glibc where I have to go around
and spot missing _GNU_SOURCE right now for Clang 16/modern C porting,
but if we pursue more changes like this, we end up having to do more work
to find issues on other platforms like musl instead of getting it for free.)

thanks,
sam

[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 358 bytes --]

  reply	other threads:[~2022-11-06 21:27 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
2022-11-04 12:10   ` Florian Weimer
2022-11-04 12:26     ` Adhemerval Zanella Netto
2022-11-06 21:26       ` Sam James [this message]
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=F9A97449-234A-4B8B-9529-627493CA65DA@gentoo.org \
    --to=sam@gentoo.org \
    --cc=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).