Re: [musl] Re: posix_spawn_file_actions_add* functions on musl libc

2019-03-24 Thread Rich Felker
On Sun, Mar 24, 2019 at 07:23:16PM +0100, Bruno Haible wrote: > Hi Rich, > > > -- it would preclude advance creation of a file actions object which > > will open or dup onto high fd numbers at a later time after the rlimit > > has been increased. > > This is a highly theoretical use-case, isn't i

Re: posix_spawn_file_actions_add* functions on musl libc

2019-03-24 Thread Bruno Haible
Hi Rich, > -- it would preclude advance creation of a file actions object which > will open or dup onto high fd numbers at a later time after the rlimit > has been increased. This is a highly theoretical use-case, isn't it? If you think POSIX should not specify things the way it does, please rep

Re: posix_spawn_file_actions_add* functions on musl libc

2019-03-24 Thread Rich Felker
On Sat, Mar 23, 2019 at 09:46:28PM +0100, Bruno Haible wrote: > The gnulib configure test in m4/posix_spawn.m4, when run on Alpine Linux 3.7, > determines that the posix_spawn_file_actions_add* functions do not fail as > expected for an out-of-range file descriptor. The POSIX "shall fail" requirem

posix_spawn_file_actions_add* functions on musl libc

2019-03-23 Thread Bruno Haible
The gnulib configure test in m4/posix_spawn.m4, when run on Alpine Linux 3.7, determines that the posix_spawn_file_actions_add* functions do not fail as expected for an out-of-range file descriptor. Let me document this in gnulib and update the cross-compilation guess accordingly. Rich, FYI: Thes