Re: [toplevel] Use a full path to INSTALL

[Eric Botcazou <ebotcazou at libertysurf dot fr>]

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

One of the most reported bugs on Solaris for GCC.  Thanks for tackling it.

> 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?

...an absolute path... I presume (as written in the ChangeLog entry).


+srcpwd=`cd ${srcdir} ; ${PWDCMD-pwd}`
+
+# We pase INSTALL explicitly to sub-makes. ?Make sure that it is not
           ^
           typo

+# a relative path.
+if test "$INSTALL" = "${srcdir}/install-sh -c"; then
+ ?INSTALL="${srcpwd}/install-sh -c"
+fi

-- 
Eric Botcazou