On Thu, 7 Apr 2005, Joe Buck wrote:
On Thu, Apr 07, 2005 at 03:11:25PM -0400, Kaveh R. Ghazi wrote:I don't know about the utility of example scripts in general, but for this specific case, I strongly feel autoconf should automatically detect this and reexec the configure script under /bin/ksh.
Is there a specific test we can write that identifies a flawed /bin/sh?
Twisting the meaning of this slightly: are there tests that show what is wrong with a [for example, Solaris] /bin/sh? A hailstorm of bug reports might have enough momentum to move things along.
Hugh
