This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
[toplevel] Use a full path to INSTALL
- From: Daniel Jacobowitz <drow at false dot org>
- To: gcc-patches at gcc dot gnu dot org
- Cc: binutils at sources dot redhat dot com
- Date: Sat, 23 Oct 2004 15:16:58 -0400
- Subject: [toplevel] Use a full path to INSTALL
Bug admin/179 in the binutils bugzilla (on sources.redhat.com) describes a
problem where "make install" fails when configured with a relative path. On
systems where /usr/bin/install isn't usable, autoconf carefully does not
cache the value of INSTALL so that subdirectories will not use it. However,
we explicitly pass it to subdirectories - we have to, because of
MAKEOVERRIDES=, or else make install INSTALL="whatever" will not work.
This patch explicitly uses a relative path to install-sh in this case. It
was the least intrusive solution I could come up with. Tested on
i386-pc-linux-gnu, with /usr/bin/install moved out of the way. OK?
--
Daniel Jacobowitz
2004-10-23 Daniel Jacobowitz <dan@debian.org>
* configure.in: Use an absolute path to install-sh.
* configure: Regenerated.
Index: configure.in
===================================================================
RCS file: /big/fsf/rsync/src-cvs/src/configure.in,v
retrieving revision 1.242
diff -u -p -r1.242 configure.in
--- configure.in 12 Oct 2004 23:40:03 -0000 1.242
+++ configure.in 23 Oct 2004 19:05:48 -0000
@@ -80,10 +80,17 @@ AC_SUBST(TOPLEVEL_CONFIGURE_ARGUMENTS)
moveifchange=${srcdir}/move-if-change
+srcpwd=`cd ${srcdir} ; ${PWDCMD-pwd}`
+
+# We pase INSTALL explicitly to sub-makes. Make sure that it is not
+# a relative path.
+if test "$INSTALL" = "${srcdir}/install-sh -c"; then
+ INSTALL="${srcpwd}/install-sh -c"
+fi
+
# Set srcdir to "." if that's what it is.
# This is important for multilib support.
pwd=`${PWDCMD-pwd}`
-srcpwd=`cd ${srcdir} ; ${PWDCMD-pwd}`
if test "${pwd}" = "${srcpwd}" ; then
srcdir=.
fi