public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Florian Weimer <fweimer@redhat.com>,
	GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] posix: Replace posix_spawnattr_tc{get,set}pgrp_np with posix_spawn_file_actions_addtcsetpgrp_np
Date: Sat, 29 Jan 2022 16:59:08 -0300	[thread overview]
Message-ID: <46a6e92a-3313-659b-6d01-5fe1f2d2b97a@linaro.org> (raw)
In-Reply-To: <CAMe9rOpZ_ipBo7bgj_taav+re1S+Hx1B+7uXzDwUqi=kp7jN5g@mail.gmail.com>



On 29/01/2022 01:55, H.J. Lu wrote:
> On Thu, Jan 27, 2022 at 9:05 AM Adhemerval Zanella via Libc-alpha
> <libc-alpha@sourceware.org> wrote:
>>
>>
>>
>> On 27/01/2022 13:11, Florian Weimer wrote:
>>> * Adhemerval Zanella:
>>>
>>>> The posix_spawnattr_tcsetpgrp_np works on a file descriptor (the
>>>> controlling terminal), so it would make more sense to actually fit
>>>> it on the file actions API.
>>>>
>>>> Also, POSIX_SPAWN_TCSETPGROUP is not really required since it is
>>>> implicit by the presence of tcsetpgrp file action.
>>>>
>>>> The posix/tst-spawn6.c is also fixed when TTY can is not present.
> 
> I still got
> 
> [hjl@gnu-tgl-2 build-x86_64-linux]$ cat posix/tst-spawn6.out
> error: xopen.c:28: open64 ("/dev/tty", 0x0, 0600): No such device or address
> error: 1 test failures
> [hjl@gnu-tgl-2 build-x86_64-linux]$
> 
> It happened when I did
> 
> $ nohup make check&
> $ logout

That's because I am using the wrong errno value to check if the tty is
present (ENOENT).  I have changed to ENXIO.

> 
>>>> Checked on x86_64-linux-gnu and i686-linux-gnu.
>>>
>>> This has an ABI check failure on Hurd:
>>>
>>> --- ../sysdeps/mach/hurd/i386/libc.abilist      2022-01-27 10:04:20.120812828 -0500
>>> +++ /home/bmg/build/glibcs/i686-gnu/glibc/libc.symlist  2022-01-27 10:43:39.646804376 -0500
>>> @@ -2292,2 +2291,0 @@ GLIBC_2.35 posix_spawn_file_actions_addt
>>> -GLIBC_2.35 posix_spawnattr_tcgetpgrp_np F
>>> -GLIBC_2.35 posix_spawnattr_tcsetpgrp_np F
>>>
>>> The changes look okay to me.  A second review is probably warranted at
>>> this stage.
>>
>> Thanks.  It is really annoying that hurd make update-abi adds a bunch of files
>> and requires manual edit to get it right.
> 
> 
> 

      reply	other threads:[~2022-01-29 19:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-27 14:14 [PATCH] posix: Replace posix_spawnattr_tc{get, set}pgrp_np " Adhemerval Zanella
2022-01-27 16:11 ` [PATCH] posix: Replace posix_spawnattr_tc{get,set}pgrp_np " Florian Weimer
2022-01-27 17:04   ` Adhemerval Zanella
2022-01-27 17:15     ` Samuel Thibault
2022-01-27 18:09       ` Adhemerval Zanella
2022-01-27 18:10         ` Samuel Thibault
2022-01-27 18:12         ` Florian Weimer
2022-01-28  0:07         ` [hurd] update-abi (was: posix: Replace posix_spawnattr_tc{get,set}pgrp_np with posix_spawn_file_actions_addtcsetpgrp_np) Samuel Thibault
2022-03-01 12:42           ` [hurd] update-abi Florian Weimer
2022-03-06 19:28             ` Samuel Thibault
2022-01-29  4:55     ` [PATCH] posix: Replace posix_spawnattr_tc{get, set}pgrp_np with posix_spawn_file_actions_addtcsetpgrp_np H.J. Lu
2022-01-29 19:59       ` Adhemerval Zanella [this message]

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=46a6e92a-3313-659b-6d01-5fe1f2d2b97a@linaro.org \
    --to=adhemerval.zanella@linaro.org \
    --cc=fweimer@redhat.com \
    --cc=hjl.tools@gmail.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).