[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Tru64/OSF: BIN_SH revisited
From: |
Ralf Wildenhues |
Subject: |
Re: Tru64/OSF: BIN_SH revisited |
Date: |
Thu, 6 Apr 2006 14:08:27 +0200 |
User-agent: |
Mutt/1.5.11 |
We have to go back once more.
* Stepan Kasal wrote on Fri, Mar 17, 2006 at 08:35:12PM CET:
> On Fri, Mar 17, 2006 at 11:20:49AM -0800, Paul Eggert wrote:
> > Yes, except you need to modify the Autoconf documentation accordingly.
>
> I checked in the version attached to this mail.
The BIN_SH removal (and documentation) should be reverted. I spent far too
much time last night trying to confirm that some of the tests under
tests/mktest.sh:Dunno why these are ignored.
were actually ignored wrongly, until it occurred to me that the hang and
load explosion I was experiencing on Tru64 wasn't due to those tests at
all, but due to the instance of bare `sh' in tests/local.at:
| m4_define([AT_CHECK_SHELL_SYNTAX],
| [AS_IF([test x"$ac_cv_sh_n_works" != xno],
| [AT_CHECK([/bin/sh -n $1], 0)], [$2])])
So while there may be a cleaner fix, namely tracking down all instances
of unadorned `sh', at this point I'm not very inclined to go about that.
I also think BIN_SH should be set in AS_BOURNE_COMPATIBLE, not in
AS_SHELL_SANITIZE, but am less certain about that.
OK to revert the BIN_SH part of the quoted patch? Including
documentation?
Cheers,
Ralf
> 2006-03-17 Stepan Kasal <address@hidden>
>
> * lib/m4sugar/m4sh.m4 (AS_BOURNE_COMPATIBLE): Removed BIN_SH=xpg4,
> moved DUALCASE=1 ...
> (AS_SHELL_SANITIZE): ... here.
> * doc/autoconf.texi (Special Shell Variables) <BIN_SH>: Do not say
> that it is set.
>
> Index: lib/m4sugar/m4sh.m4
> ===================================================================
> RCS file: /cvsroot/autoconf/autoconf/lib/m4sugar/m4sh.m4,v
> retrieving revision 1.162
> diff -u -r1.162 m4sh.m4
> --- lib/m4sugar/m4sh.m4 16 Mar 2006 13:33:18 -0000 1.162
> +++ lib/m4sugar/m4sh.m4 17 Mar 2006 15:20:12 -0000
> @@ -172,8 +172,6 @@
> else
> case `(set -o) 2>/dev/null` in *posix*) set -o posix;; esac
> fi
> -BIN_SH=xpg4; export BIN_SH # for Tru64
> -DUALCASE=1; export DUALCASE # for MKS sh
> ])
>
>
> @@ -320,6 +318,7 @@
> ## --------------------- ##
>
> AS_BOURNE_COMPATIBLE
> +DUALCASE=1; export DUALCASE # for MKS sh
>
> # PATH needs CR
> _AS_CR_PREPARE
> Index: doc//autoconf.texi
> ===================================================================
> RCS file: /cvsroot/autoconf/autoconf/doc/autoconf.texi,v
> retrieving revision 1.967
> diff -u -r1.967 autoconf.texi
> --- doc/autoconf.texi 17 Mar 2006 03:59:05 -0000 1.967
> +++ doc/autoconf.texi 17 Mar 2006 17:19:17 -0000
> @@ -11091,7 +11091,6 @@
> @evindex BIN_SH
> In Tru64, if @env{BIN_SH} is set to @code{xpg4}, subsidiary invocations of
> the standard shell conform to Posix.
> -Autoconf-generated scripts export this variable when they start up.
>
> @item CDPATH
> @evindex CDPATH
- Re: Tru64/OSF: BIN_SH revisited,
Ralf Wildenhues <=