Re: Install problem.

On 8 May 2000, Lloyd Zusman wrote:

> Hugh Sasse Staff Elec Eng <hgs@dmu.ac.uk> writes:
> 
> > I have run into this install problem again:
> > 
	[...]
> > 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.

	Agreed.
> 
> 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'.

	Also agreed.  The information about shtool was for information.
	However, I imagine from the description of shtool that changing
	to shtool would necessitate re-examining this, and it hints
	that there may be improvemnts in portability, too, from my
	reading of the page.
> 
> 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'

	Yes, and yes.

> run from within that same directory?  I used to get similar errors
> until I did this.
> 
> -- 
>  Lloyd Zusman
>  ljz@asfast.com
> 
> 
	Hugh
	hgs@dmu.ac.uk

Received on Monday, 8 May 2000 10:01:02 UTC