summaryrefslogtreecommitdiff
path: root/libtoolize.in
diff options
context:
space:
mode:
authorGary V. Vaughan <gary@gnu.org>2004-07-28 14:57:28 +0000
committerGary V. Vaughan <gary@gnu.org>2004-07-28 14:57:28 +0000
commitcf79a985499a75c4d4bc6f3ab4ba14c239e3e21f (patch)
tree5859fe8505d8d3a84a3afb56102d7643d13e8ed8 /libtoolize.in
parentb0cf8fdd1667cc4fdae11a62f9b0bb12fd1de13e (diff)
downloadlibtool-cf79a985499a75c4d4bc6f3ab4ba14c239e3e21f.tar.gz
To take full advantage of this, libtool must be bootstrapped with
CVS autoconf, otherwise pdksh chokes on some nested escaped quotes from libtool.m4. Using CVS autoconf protects configure from non-bourne compatible shells in the same way this changeset protects libtool and libtoolize: * libtoolize.in: Include latest CVS autoconf AS_SHELL_SANITIZE expansion to make various shells fully bourne compatible. * ltmain.in: Ditto. * m4/libtool.m4 (AC_PATH_TOOL_PREFIX): Remove spurious quotes, the RHS of = assignment is not IFS split. (_LT_LANG_CXX_CONFIG): Ditto. (AC_LIBTOOL_POSTDEP_PREDEP): Ditto.
Diffstat (limited to 'libtoolize.in')
-rw-r--r--libtoolize.in13
1 files changed, 13 insertions, 0 deletions
diff --git a/libtoolize.in b/libtoolize.in
index e036bf7c..d5ec504f 100644
--- a/libtoolize.in
+++ b/libtoolize.in
@@ -47,6 +47,19 @@
#
# Report bugs to <bug-libtool@gnu.org>.
+# Be Bourne compatible
+if test -n "${ZSH_VERSION+set}" && (emulate sh) >/dev/null 2>&1; then
+ emulate sh
+ NULLCMD=:
+ # Zsh 3.x and 4.x performs word splitting on ${1+"$@"}, which
+ # is contrary to our usage. Disable this feature.
+ alias -g '${1+"$@"}'='"$@"'
+ setopt NO_GLOB_SUBST
+elif test -n "${BASH_VERSION+set}${KSH_VERSION+set}" && (set -o posix) >/dev/null 2>&1; then
+ set -o posix
+fi
+DUALCASE=1; export DUALCASE # for MKS sh
+
: ${CP="cp -f"}
: ${LN_S="@LN_S@"}
: ${MKDIR="mkdir"}