Bruno Haible wrote:
Since Paul asked about more details on this one in
https://lists.gnu.org/archive/html/bug-gzip/2017-11/msg5.html
here are more details (on OpenBSD/i386):
$ make check TESTS=timestamp VERBOSE=yes > timestamp.x 2>&1
Thanks. I am puzzled by the failures. For example:
+
On Sat, Nov 11, 2017 at 3:39 PM, Bruno Haible wrote:
> Test results of gzip git of today + gnulib git of today (only 32-bit
> platforms):
>
> On
> FreeBSD/i386:
> Haiku/i386:
> HP-UX/hppa:
> HP-UX/ia64:
>
> FAIL: help-version
Thanks, Bruno.
The FreeBSD failure looks like it is due to "more" not
Paul Eggert wrote:
> Thanks. I am puzzled by the failures. For example:
>
> > + touch -t 19010101 in
> > + returns_ 2 gzip in
> > + fail=1
>
> Here, 'touch' succeeded, but gzip did not diagnose the negative timestamp. Do
> other programs report that the timestamp is 1901? For example, what i
Hi Jim,
> On hppa, the test that runs `gunzip --help > /dev/full` fails
> unexpectedly. It should run only on a system with writable "char"
> device /dev/full, and it should fail like this:
>
> $ gunzip --help > /dev/full
> echo: write error: No space left on device
> [Exit 1]
>
> But on your sy
Hi Jim,
> The Haiku failure is due to gzexe failing due to that system's lack of
> hard link support:
>
> + eval 'env $i in-6369 < $tmp_in > $tmp_out'
> ++ env gzexe in-6369
> in-6369:-15.4%
> ln: failed to create hard link 'in-6369~' => 'in-6369': Operation not
> supported
> /boot/home
On Sun, Nov 12, 2017 at 9:40 AM, Bruno Haible wrote:
> Hi Jim,
>
>> On hppa, the test that runs `gunzip --help > /dev/full` fails
>> unexpectedly. It should run only on a system with writable "char"
>> device /dev/full, and it should fail like this:
>>
>> $ gunzip --help > /dev/full
>> echo: write
Hi Jim,
> >> But on your system, it exits with status 2.
> >
> > Yes:
> >
> > $ ./gunzip --help > /dev/full
> > echo: No space left on device
> > $ echo $?
> > 2
>
> Ohh...
> So it's the HP-UX shell's "echo" that is detecting the write failure
> but setting errno to 2 rather than the 1
'bash' on
Bruno Haible wrote:
! # Produce output and exit with code 1 if there is a write error.
! # Use 'exec echo', not plain 'echo', because the 'echo' built-in in
! # HP-UX /bin/sh does not check for write errors.
! # Use '|| exit 1', because the 'echo' program on HP-UX exits with
! # code 2 in case of
