Re: Tru64/OSF: BIN_SH revisited

2006-03-20 Thread Paul Eggert
Stepan Kasal [EMAIL PROTECTED] writes: These two changes would make the following patch; OK to commit? Yes, except you need to modify the Autoconf documentation accordingly.

Re: Tru64/OSF: BIN_SH revisited

2006-03-17 Thread Stepan Kasal
Hello, 0a) Revert the change to set BIN_SH in Autoconf, [...] IMHO this is a very good idea. First, BIN_SH is set in macro AS_BOURNE_COMPATIBLE, but it doesn't belong there: this macro contains things like set -o posix, which i) have an immediate effect inside the current instance ii) are

Re: Tru64/OSF: BIN_SH revisited

2006-03-17 Thread Ralf Wildenhues
Hi Paul, Stepan, * Paul Eggert wrote on Fri, Mar 17, 2006 at 08:55:14AM CET: Ralf Wildenhues [EMAIL PROTECTED] writes: 0a) Revert the change to set BIN_SH in Autoconf, in order to be consistent. 0b) Additionally, prepend /usr/bin/posix/ to the path walk of _AS_DETECT_BETTER_SHELL, to

Re: Tru64/OSF: BIN_SH revisited

2006-03-17 Thread Stepan Kasal
Hello, 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. Stepan 2006-03-17 Stepan Kasal [EMAIL PROTECTED] * lib/m4sugar/m4sh.m4 (AS_BOURNE_COMPATIBLE):

Tru64/OSF: BIN_SH revisited

2006-03-16 Thread Ralf Wildenhues
This started out here and here: http://lists.gnu.org/archive/html/libtool/2004-07/msg00070.html http://lists.gnu.org/archive/html/autoconf-patches/2004-07/msg3.html and led to (CVS) Autoconf exporting BIN_SH=xpg4 (don't be fooled by the patches posted; they do not fully reflect what was

Re: Tru64/OSF: BIN_SH revisited

2006-03-16 Thread Paul Eggert
Ralf Wildenhues [EMAIL PROTECTED] writes: 0a) Revert the change to set BIN_SH in Autoconf, in order to be consistent. 0b) Additionally, prepend /usr/bin/posix/ to the path walk of _AS_DETECT_BETTER_SHELL, to choose the right shell right away, inside Autoconf. This sounds good to me. The