Hello Paul, * Paul Eggert wrote on Wed, Oct 04, 2006 at 11:21:02PM CEST: > "Underwood, Tonya" <[EMAIL PROTECTED]> writes: > > >>>> ./configure[2236]: /var/tmp/sh10423.126: Cannot create the specified > >>>> file. > > OK, thanks, I think I may have figured it out: you're using > /usr/posix/bin/sh and it's buggy. > > I have installed the following patch to GNU Autoconf to try to squash > this one. The area is kind of messy, but I guess it's better to let > the OSF and Unixware folks figure out how to build than to hurt > everyone else.
Yes, I guess that's probably the right decision. But you cannot use AS_EXECUTABLE_P in _AS_DETECT_BETTER_SHELL: the shell detection has to be done before (because the `test' used may change). This currently leads to a configure script that hangs; you can try this with regenerating Autoconf's configure, and running ksh ./configure Cheers, Ralf > 2006-10-04 Paul Eggert <[EMAIL PROTECTED]> > > * doc/autoconf.texi (Special Shell Variables): Autoconf-generated > shell scripts no longer export BIN_SH, due to configuration > hassles with this. See, for example, Tonya Underwood's report > <http://lists.gnu.org/archive/html/bug-autoconf/2006-10/msg00003.html>. > * lib/m4sugar/m4sh.m4 (AS_BOURNE_COMPATIBLE): Don't set BIN_SH > or DUALCASE. > (_AS_DETECT_BETTER_SHELL): Don't look in /usr/bin/posix. > Use AS_EXECUTABLE_P rather than test -f. > (AS_SHELL_SANITIZE): Set DUALCASE. > (AS_EXECUTABLE_P): Just invoke as_executable_p. > (_AS_TEST_PREPARE): Default to test -f, rather than to nothing.
