from p3. Some shells leave PWD in the environment (old tcsh, ksh at least)

screws nested configures. "unset PWD" is the right answer, except that
Decstation sh doesn't *have* unset.
	Note also that the send-pr build will fail if you have PWD in your
environment, because emacs also (foolishly) trusts it.

	* configure: just set PWD=`pwd` at the top, since Ultrix sh
	doesn't have unset and all success paths (and most error paths)
	out set it anyway. (Note: should change all uses of ${PWD=`pwd`}
	to just ${PWD} to avoid confusion.)

diff --git a/ChangeLog b/ChangeLog
index 0c301b455264efa9697f460fad6c1a2b1aaa8e28..fed73f71498bd2e1a400688d96ea533f2cc40871 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,10 @@
+Thu Sep 17 23:05:53 1992  Mark Eichin  (eichin@cygnus.com)
+
+       * configure: just set PWD=`pwd` at the top, since Ultrix sh
+       doesn't have unset and all success paths (and most error paths)
+       out set it anyway. (Note: should change all uses of ${PWD=`pwd`}
+       to just ${PWD} to avoid confusion.)
+
 Tue Sep 15 16:00:54 1992  Ian Lance Taylor  (ian@cygnus.com)
 
        * configure: always set $(tooldir) to $(libdir)/$(target_alias),

diff --git a/configure b/configure
index 5f689924de2bae9aa204b6050d23bd67b6b6185a..1c27867a713018233acf0b285c0a7ccfca574c6e 100755 (executable)
--- a/configure
+++ b/configure
@@ -97,6 +97,7 @@ NO_EDIT="This file was generated automatically by configure.  Do not edit."
 ##
 
 progname=$0
+PWD=`pwd`
 
 case "${progname}" in
 /*) ;;