On Thu, Jul 13, 2017 at 9:46 PM, Paul Eggert <egg...@cs.ucla.edu> wrote: > Mohammad Akhlaghi wrote: >> >> It would be great if this first line of the configure script would also >> check for `CONFIG_SHELL' > > > Unfortunately this does not work, as the operating system handles the first > line before the configure script starts. >
A hardcoded binary path isn't portable, the correct solution is to use `env sh`. Typically this is seen as: #!/usr/bin/env sh Which technically causes the same problem Mr. Akhlagi was experiencing, but on most desktop Unixes the location of `env` is more predictable than the location of various interpreters. R0b0t1.
