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.)
This commit is contained in:
parent
ca25cb3b4b
commit
fc11b71ac4
2 changed files with 8 additions and 0 deletions
|
@ -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),
|
||||
|
|
1
configure
vendored
1
configure
vendored
|
@ -97,6 +97,7 @@ NO_EDIT="This file was generated automatically by configure. Do not edit."
|
|||
##
|
||||
|
||||
progname=$0
|
||||
PWD=`pwd`
|
||||
|
||||
case "${progname}" in
|
||||
/*) ;;
|
||||
|
|
Loading…
Reference in a new issue