Make on bash 3.1 fails with "autoconf: not found" (AlphaServer DS10L running Tru64 UNIX 5.1B Patch Kit #5, latest)

[John Lanier]

Hello,
 
Not sure if this is a bug, but I figured I'd start here.
 
Also, I have compiled 3.1 on other Alpha platforms using the same OS/PK without 
incident.  The only difference is that the system I am having a problem with is 
a member of a TruCluster V5.1B configuration and the others are not (I don't 
think that should make a difference, but I figured I should mention it 
nonetheless).
 
Problem:
=======
 
 
1. Configure completes without incident using these options:
----------------------------------------------------------
root@jimwest in /var/bash3.1/binaries/bash-3.1 -->./configure
(OK)
 
root@jimwest in /var/bash3.1/binaries/bash-3.1 --> CC=cc ./configure \
--srcdir=/var/bash3.1/binaries/bash-3.1
(OK..)
 
 
2. "make" fails as follows after both configure's complete:
---------------------------------------------------------
root@jimwest in /var/bash3.1/binaries/bash-3.1 --> make
cd /var/bash3.1/binaries/bash-3.1 && autoconf
sh: autoconf: not found <--
*** Exit 1  <--
Stop.   <--
 
 
3. From my config.log:
--------------------
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by bash configure 3.1-release, which was
generated by GNU Autoconf 2.53.  Invocation command line was
  $ ./configure --srcdir=/var/bash3.1/binaries/bash-3.1
## --------- ##
## Platform. ##
## --------- ##
hostname = jimwest.parsec.com
uname -m = alpha
uname -r = V5.1
uname -s = OSF1
uname -v = 2650
/usr/bin/uname -p = alpha
/bin/uname -X     = unknown

 
Compiler Information:
-----------------------
......
configure:2317: cc -V </dev/null >&5
Compaq C V6.5-011 on Compaq Tru64 UNIX V5.1B (Rev. 2650)
Compiler Driver V6.5-003 (sys) cc Driver
......
 
 
4.  I did a "find / -name" on "autoconf" and "Autoconf" on both the problem 
system and a working system, and it didn't find it in either environment (??).
 
 
5.  No luck on any fixes from Google, but maybe I didn't search hard enough :-)
 
 
Regards,
 
--John Lanier