Ralf Wildenhues <[EMAIL PROTECTED]> writes: > Well, this seems to me that the mechanism did not work with the file > #! /bin/cat > exit 69 > > (was that due to some "hardened system" such as SELinux by the way, with > the `No such file or directory' the result of a missing clearing of > errno, or is this indeed a system that does not have /bin/cat?)
My money would be on a missing "/bin/cat". > Consequently, I guess the test should have failed, no? If "/bin/cat" is missing and the kernel causes the script to fail because of this, then the "#!" mechanism is indeed working, so the test should pass. Most likely a "hardened system" would also be working too (unless it disabled "#!/bin/sh", which would be hard to believe -- but in that case we'll need to see the system before we can port Autoconf to it).
