Pádraig Brady wrote:
> On 09/01/2011 09:15 AM, Bruno Haible wrote:
>> Jim Meyering wrote:
>>> coreutils snapshot: (.gz files are here, too)
>>> http://meyering.net/cu/coreutils-ss.tar.xz 4.8 MB
>>> http://meyering.net/cu/coreutils-ss.tar.xz.sig
>>> http://meyering.net/cu/coreutils-8.12.178-df9cd.tar.xz
>>
>> On Linux with glibc 2.11.3:
>> All tests pass, and all gnulib-tests pass.
>
> Thanks for all this testing Bruno.
> Note the reports are easier to diagnose if you use:
>
> make check VERBOSE=yes
Hi Pádraig,
That is enabled by default, but if you are running the tests with
a deficient bourne shell it turns off the VERBOSE=yes.
Here's the code from init.sh that does that:
setup_ ()
{
if test "$VERBOSE" = yes; then
# Test whether set -x may cause the selected shell to corrupt an
# application's stderr. Many do, including zsh-4.3.10 and the /bin/sh
# from SunOS 5.11, OpenBSD 4.7 and Irix 5.x and 6.5.
# If enabling verbose output this way would cause trouble, simply
# issue a warning and refrain.
if $gl_set_x_corrupts_stderr_; then
warn_ "using SHELL=$SHELL with 'set -x' corrupts stderr"
else
set -x
fi
fi
So, the best for us would be if the tests could be run using say, bash.
