Actually, /bin/sh does exist; for the sake of argument I changed it to
/sbin/sh. No dice. I tried the GNU "make install" command, and that came
back with:

/da01/qpopper4.0.1> /usr/local/bin/make install
./install-sh -c -m 0644 -o root ./man/popper.8  /usr/local/man/man8/
make: execvp: ./install-sh: Permission denied
make: *** [install] Error 127
/da01/qpopper4.0.1>

Don't know what's giving me the "permission denied" errors; all the file
ownerships and perms in the qpopper directory look fine. Unfortunately, I'm
not a C or C++ programmer, or this would be less mystifying. 

My boss told me a couple minutes ago that the "make" environment on HP/UX is
different than on most x-IXes; he's had problems like this with similar
utilities he's tried to compile. Looking around on the web, I'm noticing
that the last version of qpopper people using HP/UX seem to be successfully
using is somewhere right around 2.14 or 2.53. 

If I can't get this to work, I will, of course, solicit suggestions for an
alternative...

-----Original Message-----
From: Bryce Newall [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 02, 2001 2:24 PM
To: Martin, Rich
Subject: Re: make-install doesn't work for 4.0.1


On Wed, 2 May 2001, Martin, Rich wrote:

> /da01/qpopper4.0.1> make install
>         ./install-sh -c -m 0644 -o root ./man/popper.8
/usr/local/man/man8/
> Make: Cannot load ./install-sh.  Stop.
> *** Error exit code 1

This may be elementary, but did you check the first line of the install-sh
script to see what shell it's pointing to?  If, for example, it's looking
for /bin/sh and /bin/sh doesn't exist on your system, you'll get that
exact error message.  If that's the problem, you can either edit the
script, or make a symlink to the shell so that the script will be able to
find it where it's looking.

*********************************************************
*    Bryce Newall    *    Email: [EMAIL PROTECTED]    *
*               www.dreamhaven.org/~data                *
*  "Computers make very fast, very accurate mistakes."  *
*********************************************************

Reply via email to