Re: z/OS sigpipe test failures due to quirky error handling

2017-02-28 Thread Bruno Haible
Daniel Richard G. wrote: > The second test is test-sigpipe.sh: > > $ /path/to/testdir/gltests/test-sigpipe.sh > CEE5213S The signal SIGPIPE was received. > $ echo $? > 1 > > The default SIGPIPE signal handler appears to write to stderr, and this > is separate from the "Broken pipe

Re: z/OS perror test failures due to quirky error handling

2017-02-28 Thread Bruno Haible
Daniel Richard G. wrote: > Two tests in the Gnulib test suite are currently failing due to z/OS > idiosyncrasies relating to error messages. > > The first one is test-perror.sh: > > $ srcdir=/path/to/testdir/gltests /path/to/testdir/gltests/test-perror.sh > test-perror.sh: failed test: r

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