Re: z/OS and symlink()

2017-03-14 Thread Paul Eggert
On 03/14/2017 12:53 PM, Daniel Richard G. wrote: Special-case the test for z/OS? That sounds like the right way to go, yes. I hope the special case is small and unobtrusive code.

Re: z/OS and symlink()

2017-03-14 Thread Daniel Richard G.
Hi Bruno, On Tue, 2017 Feb 28 16:47+0100, Bruno Haible wrote: > > The relevant spec here is POSIX: > http://pubs.opengroup.org/onlinepubs/9699919799/functions/symlink.html > Line 64 of test-symlink.h:64 corresponds to the case > > [ENOENT] or [ENOTDIR] > The path2 argument contains at leas

Re: z/OS and symlink()

2017-02-28 Thread Daniel Richard G.
On Tue, 2017 Feb 28 16:47+0100, Bruno Haible wrote: > > The relevant spec here is POSIX: > http://pubs.opengroup.org/onlinepubs/9699919799/functions/symlink.html > Line 64 of test-symlink.h:64 corresponds to the case > > [ENOENT] or [ENOTDIR] > The path2 argument contains at least one non-

Re: z/OS and symlink()

2017-02-28 Thread Bruno Haible
Daniel Richard G. wrote: > Currently, test-symlink and test-symlinkat are failing on z/OS: > > $ ./test-symlink > .../test-symlink.h:64: assertion 'errno == ENOTDIR || errno == ENOENT' > failed > CEE5207E The signal SIGABRT was received. > ABORT instruction > > $ ./test-symli

z/OS and symlink()

2017-02-27 Thread Daniel Richard G.
Currently, test-symlink and test-symlinkat are failing on z/OS: $ ./test-symlink .../test-symlink.h:64: assertion 'errno == ENOTDIR || errno == ENOENT' failed CEE5207E The signal SIGABRT was received. ABORT instruction $ ./test-symlinkat .../test-symlink.h:64: assertion