Re: [bug-gzip] gzip-1.5 test failures on FreeBSD 9.0 and NetBSD 5.1

2012-06-20 Thread Nelson H. F. Beebe
Thanks, Paul, for the patch to tests/init.sh. I've just applied that and prepared gzip-1.5.p1.tar.gz that I then configured and built on both FreeBSD and NetBSD. This time, the runs succeeded, without any infinite loops (though that could be because /usr/local/bin/zdiff is now the latest version)

Re: Testsuite summary for gzip 1.5

2012-06-20 Thread sunmana...@t-online.de
Hi Paul, sorry for the delay. I modified the files and repeated only the check (successfully). If I should repeate the hole build process please let me know it. Best regards Daniel -Original Message- Date: Wed, 20 Jun 2012 02:26:24 +0200 Subject: Re: Testsuite summary for gzip 1.5 From

Re: [bug-gzip] gzip-1.5 test failures on FreeBSD 9.0 and NetBSD 5.1

2012-06-20 Thread Paul Eggert
On 06/20/2012 06:38 AM, Nelson H. F. Beebe wrote: > This time, the runs succeeded, without > any infinite loops (though that could be because /usr/local/bin/zdiff > is now the latest version). OK, thanks, I've pushed the following change to gnulib and it should percolate to gzip on the next sync.

Re: [bug-gzip] gzip-1.5 test failures on FreeBSD 9.0 and NetBSD 5.1

2012-06-20 Thread Eric Blake
[adding bug-autoconf] On 06/20/2012 08:10 AM, Paul Eggert wrote: > This addresses symptoms of the problem reported by Nelson H.F. Beebe in > . > Although Nelson's bug was not necessarily fixed by this patch, > it seems wise to make

Re: [bug-gzip] gzip-1.5 test failures on FreeBSD 9.0 and NetBSD 5.1

2012-06-20 Thread Paul Eggert
On 06/20/2012 07:16 AM, Eric Blake wrote: > do we know which shells suffer from this > POSIX non-compliance bug, and whether they are still in active use Sorry, I don't know of a list of such shells. The problem is documented in the Autoconf manual, without listing shells. I have verified that th

Re: [bug-gzip] gzip-1.5 test failures on FreeBSD 9.0 and NetBSD 5.1

2012-06-20 Thread Eric Blake
On 06/20/2012 08:45 AM, Paul Eggert wrote: > More generally, the problem is that often people use scripts > in Perl or Python or whatnot to run a test, or run a test from > a shell spawned by a terminal emulator, and these scripts > or terminal emulators may execute chdir without updating PWD, > s