Sorry, lost me there... So, hopefully to improve both our understanding of what is happening...
1. I am using ksh (using bash did not change anything, unfortunately). 2. Running only init.sh returns the following (first not set, then set VERBOSE=yes) Note: log file attached - no extra debug info... root@x105:[/]cd /data/prj/co*14 root@x105:[/data/prj/coreutils-8.14]./init.sh ksh: ./init.sh: not found. root@x105:[/data/prj/coreutils-8.14]cd tests root@x105:[/data/prj/coreutils-8.14/tests]./init.sh root@x105:[/data/prj/coreutils-8.14/tests]export VERBOSE=yes root@x105:[/data/prj/coreutils-8.14/tests]./init.sh + initial_cwd_=/data/prj/coreutils-8.14/tests + fail=0 ++ testdir_prefix_ ++ printf gt + pfx_=gt ++ mktempd_ /data/prj/coreutils-8.14/tests gt-init.sh.XXXX ++ destdir_=/data/prj/coreutils-8.14/tests ++ template_=gt-init.sh.XXXX ++ MAX_TRIES_=4 +++ unset TMPDIR +++ mktemp -d -t -p /data/prj/coreutils-8.14/tests gt-init.sh.XXXX ++ d=/data/prj/coreutils-8.14/tests/gt-init.sh.bbZX ++ test -d /data/prj/coreutils-8.14/tests/gt-init.sh.bbZX +++ ls -dgo /data/prj/coreutils-8.14/tests/gt-init.sh.bbZX +++ tr S - ++ perms=drwx------ 2 256 Jan 2 2012 /data/prj/coreutils-8.14/tests/gt-init.sh.bbZX ++ test 0 = 0 ++ echo /data/prj/coreutils-8.14/tests/gt-init.sh.bbZX ++ return + test_dir_=/data/prj/coreutils-8.14/tests/gt-init.sh.bbZX + cd /data/prj/coreutils-8.14/tests/gt-init.sh.bbZX + gl_init_sh_nl_= + IFS= ++ expr 1 + 128 + eval 'trap '\''Exit 129'\'' 1' ++ trap 'Exit 129' 1 ++ expr 2 + 128 + eval 'trap '\''Exit 130'\'' 2' ++ trap 'Exit 130' 2 ++ expr 3 + 128 + eval 'trap '\''Exit 131'\'' 3' ++ trap 'Exit 131' 3 ++ expr 13 + 128 + eval 'trap '\''Exit 141'\'' 13' ++ trap 'Exit 141' 13 ++ expr 15 + 128 + eval 'trap '\''Exit 143'\'' 15' ++ trap 'Exit 143' 15 + trap remove_tmp_ 0 + remove_tmp_ + __st=0 + cleanup_ + : + cd /data/prj/coreutils-8.14/tests + chmod -R u+rwx /data/prj/coreutils-8.14/tests/gt-init.sh.bbZX + rm -rf /data/prj/coreutils-8.14/tests/gt-init.sh.bbZX + exit 0 root@x105:[/data/prj/coreutils-8.14/tests] On Mon, Jan 2, 2012 at 9:32 PM, Jim Meyering <[email protected]> wrote: > Paul Eggert wrote: > > On 01/02/12 11:39, Michael Felt wrote: > >> Running with VERBOSE=yes, however, I do not see a big difference with > the output > > > > Weird. > > VERBOSE=yes is disabled via init.sh when the selected shell mishandles > "set -x" so badly that its output would induce test failures. > When that happens, you should see a diagnostic something like this: > > warn_ "using SHELL=/bin/sh with 'set -x' corrupts stderr" > > Here are the relevant parts of init.sh: > > # The "...set -x; P=1 true 2>err..." test is to disqualify any shell that > # emits "P=1" into err, as /bin/sh from SunOS 5.11 and OpenBSD 4.7 do. > # > # Use "9" to indicate success (rather than 0), in case some shell acts > # like Solaris 10's /bin/sh but exits successfully instead of with status > 2. > > # Eval this code in a subshell to determine a shell's suitability. > # 10 - passes all tests; ok to use > # 9 - ok, but enabling "set -x" corrupts app stderr; prefer higher score > # ? - not ok > gl_shell_test_script_=' > test $(echo y) = y || exit 1 > score_=10 > if test "$VERBOSE" = yes; then > test -n "$( (exec 3>&1; set -x; P=1 true 2>&3) 2> /dev/null)" && score_=9 > fi > test -z "$EXEEXT" && exit $score_ > shopt -s expand_aliases > alias a-b="echo zoo" > v=abx > test ${v%x} = ab \ > && test ${v#a} = bx \ > && test $(a-b) = zoo \ > && exit $score_ > ' > ... > > 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 >
log.xz
Description: Binary data
