test failures for 2.05a

[Paul Jarc]

I got the following test failures when building bash 2.05a, all
related to assumptions about programs' locations.

The "command not found" errors seem to happen because the tests
replace $PATH instead of augmenting it.  The stated goal is to ensure
that "notthere" will not be found in $PATH, but that isn't guaranteed
even when replacing $PATH.  Anyway, could the original $PATH be
restored for finding commands that are expected to be found?

The use of /bin/echo and /bin/cat seem to be intended to avoid the
shell builtin commands; "env foo" or "(exec foo)" would work for these
cases and allow searching $PATH.  I also found /bin/date and /bin/true
in some of the tests, which could also use env or (exec), though they
seem to have not caused any test failures.

run-execscript
warning: the text of a system error message may vary between systems and
warning: produce diff output.
warning: if the text of the error messages concerning `notthere' or
warning: `/tmp/bash-notthere' not being found or `/' being a directory
warning: produce diff output, please do not consider this a test failure
15c15
< /: /: is a directory
---
> /: /: cannot execute binary file
39,40d38
< /home/prj/b/bash-2.05a/bash: cat: command not found
< /home/prj/b/bash-2.05a/bash: cat: command not found
49,52d46
< ./exec6.sub: touch: command not found
< ./exec6.sub: chmod: command not found
< 0
< 1
54a49
> 0
56a52
> 1

run-redir
warning: the text of a system error message may vary between systems and
warning: produce diff output.
warning: if the text of an error message concerning `redir1.*' not being
warning: found produces diff output, please do not consider it a test failure
43d42
< ./redir.tests: /bin/cat: No such file or directory

run-varenv
./varenv.sh: /bin/echo: No such file or directory
./varenv.sh: /bin/echo: No such file or directory
5a6
> /usr/chet
6a8
> /usr/chet


paul