Re: Install problem.

Hugh Sasse Staff Elec Eng <hgs@dmu.ac.uk> writes:

> I have run into this install problem again:
> 
> libwww is installed
> gmake[2]: Leaving directory
> `/home/hgs/Amaya/Amaya/Sun-Sparc-Solaris-2.5.1'
> gmake[2]: Entering directory
> `/home/hgs/Amaya/Amaya/Sun-Sparc-Solaris-2.5.1/thotlib'
> gmake[2]: Leaving directory
> `/home/hgs/Amaya/Amaya/Sun-Sparc-Solaris-2.5.1/thotlib'
> gmake[2]: Entering directory
> `/home/hgs/Amaya/Amaya/Sun-Sparc-Solaris-2.5.1/tablelib'
> gmake[2]: Nothing to be done for `libThotTable'.
> gmake[2]: Leaving directory
> `/home/hgs/Amaya/Amaya/Sun-Sparc-Solaris-2.5.1/tablelib'
> gmake[2]: Entering directory
> `/home/hgs/Amaya/Amaya/Sun-Sparc-Solaris-2.5.1/libpng'
> gmake[2]: Nothing to be done for `all'.
> gmake[2]: Leaving directory
> `/home/hgs/Amaya/Amaya/Sun-Sparc-Solaris-2.5.1/libpng'
> ../install-sh -c -m 755 ../bin/amaya /usr/local/Amaya/applis/bin
> gmake[1]: ../install-sh: Command not found
> gmake[1]: *** [install] Error 127
> gmake[1]: Leaving directory
> `/home/hgs/Amaya/Amaya/Sun-Sparc-Solaris-2.5.1/amaya'
> 
> I don't know if there is a good fix for this or not, but I do know there
> is now: shtool, which is intended to replace install.sh

The problem here is not with install-sh itself, but rather, it's due
to the fact that `../install-sh' is an incorrect path to this script
at the time it's being invoked.

Therefore, if `install-sh' was replaced with `shtool' and if nothing
else was changed in the build process, an identical error would occur
if the build were trying to invoke `../shtool install'.

In the above case, was the configure script run as `../configure' from
within the `Sun-Sparc-Solaris-2.5.1' directory?  And then, was `gmake'
run from within that same directory?  I used to get similar errors
until I did this.

-- 
 Lloyd Zusman
 ljz@asfast.com

Received on Monday, 8 May 2000 09:38:19 UTC