Re: posix_spawn_file_actions_addchdir

2018-09-07 Thread Bruno Haible
Eric Blake wrote: > http://austingroupbugs.net/view.php?id=1208 > > There, I argue that we also need posix_spawn_file_actions_addfchdir(), > in part because it lets us get the same power as openat() in determining > how relative file names are resolved in relation to an fd. The use-case is, AFA

Re: posix_spawn_file_actions_addchdir

2018-09-07 Thread Eric Blake
On 09/07/2018 04:53 PM, Bruno Haible wrote: Implemented as follows. The prototype is as in [3], except that I dropped the suffix '_np', because - Functions with suffix '_np' are in the system's namespace, that is, there is no requirement that different systems implement them with the

Re: posix_spawn_file_actions_addchdir

2018-09-07 Thread Bruno Haible
Eric Blake wrote: > > Actually, this particular problem can be easily solved on Threos, > > because the posix_spawn() API offers a function for this: > > int posix_spawn_file_actions_addchdir_np(posix_spawn_file_actions_t* > > __restrict file_actions, const char* __restrict path); > > > > Note t