- From: H. Nanosecond <aldomel@ix.netcom.com>
- Date: Tue, 9 May 2000 01:36:42 -0400 (EDT)
- To: Hugh Sasse Staff Elec Eng <hgs@dmu.ac.uk>
- CC: www-amaya@w3.org
A solution for you is to give an absolute path for install-sh
by this way:
rm Options config.cache # get rid of old stuff
INSTALL=~hgs/Amaya/Amaya/install-sh ../configure options...
A solution for amaya developers may be to set an absolute path in
configure.in:
AC_PROG_INSTALL
prog="${INSTALL##*/}" # prog=$(basename $INSTALL)
dir="${INSTALL%/*}" # dir=$(dirname $INSTALL)
cd "$dir"
INSTALL="$( pwd )""/$prog"
cd -
AC_MSG_RESULT([install is now $INSTALL])
maybe this should be mentioned to autoconf people.
>`/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
>See
Received on Tuesday, 9 May 2000 02:45:02 UTC