* ltmain.in ($PATH): Expand any tildes in the users path to the

contents of $HOME to avoid problems with *_cmds splitting and
evaluation.

diff --git a/ChangeLog b/ChangeLog
index 8f67e9b9ce633f261c90fdfd5e901539527a74a4..0ef976674ba58657d9a9a7428f8d6264a4965297 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,9 @@
+1999-03-25  Gary V. Vaughan  <gvaughan@oranda.demon.co.uk>
+
+       * ltmain.in ($PATH):  Expand any tildes in the users path to the
+       contents of $HOME to avoid problems with *_cmds splitting and
+       evaluation.
+       
 1999-03-24 Thomas Tanner  <tanner@gmx.de>
 
        * doc/PLATFORMS: Erez Zadok reported that libtool works on bsdi 4.0.1

diff --git a/ltmain.in b/ltmain.in
index fed22505fd45dc7195366efcab0c9de07a123eaf..fe9655c67d875f7db2d21cbeba4027bc83a6a889 100644 (file)
--- a/ltmain.in
+++ b/ltmain.in
@@ -90,6 +90,13 @@ if test "$build_libtool_libs" != yes && test "$build_old_libs" != yes; then
   exit 1
 fi
 
+# A little paranoid perhaps...
+[ "${HOME+set}" ] || HOME=`cd && pwd`
+
+# Apparently some people optimistically hardcode `~' in their path, and
+# hope that their tools will interpret it correctly.  We mustn't disappoint!
+eval PATH=`echo "$PATH" | sed 's,^~/,$HOME/,;s,:~/,:$HOME/,g'`
+
 # Global variables.
 mode=$default_mode
 nonopt=