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? I suppose we can key off of the target triplets mentioned in install/specific.html as having bad sh implementations. > If we follow "Freeman's Rule" then even the example script can be > misunderstood and having autoconf find ksh for you and run it behind > the scenes would be safer IMHO. Alternatively, find bash, as that works too.
