What Michael_Bray is saying, is something I try to point out in all installs -- not everyone uses the EXACT same names for their files (or there is system-translation going on). You need to list the directory to see what names have been unpacked. Sometimes the "make" will be "Make" or even 'MAKE'
If you are using a windowed environment to access it ... it helps to open a directory listing (FTP by Telnet) to see the list of the file names. It also makes reading the docs and editing files easy.
The other thing is that if you've su'd to root, then your path information may not exist, and you need to give complete paths.
When I work on file installs, I load my default shell manually /path/to/shell/ profile so that my "environment" is normal for the system. Because I'm already logged in as root, and know I'm working, it's safe to do.
Sometimes, programs will install with a command like:
/usr/local/bin/perl make (etc...)
Other times, they want more from the environment, and I find loading the shell with default binary paths solves a lot of problems of editing the scripts (some want the path to gcc, or other programs).
So -- the two things to check are:
1) the file names
2) the paths in your environment
------------------
POSTCARDS.COM -- Everything Postcards on the Internet
www.postcards.com LinkSQL FAQ: www.postcards.com/FAQ/LinkSQL/