Re: Starting /bin/sh in output configure file

[Mohammad Akhlaghi]

Thank you very much everyone for the great comments.

I can confirm that on this Android phone there is no `/usr' directory 
either (it also doesn't have any `/bin' directory)! So a `#!/usr/bin/env 
sh' first line would have a similar fate.

I do all my serious work with my GNU/Linux systems on my desktop and 
laptop computers. But I have always been bothered by the fact that we 
have such physically-portable and powerful devices (smartphones) with us 
every where, but I can't use it as a simple command-line tool (with my 
own programs as I do on my GNU/Linux system). It is a real shame!

In short, this is more like a hobby for me to have my most commonly used 
command-line programs running natively on my phone to use in occasions 
when I don't have my (physically) larger GNU/Linux systems nearby.

So I searched for a terminal emulator app for my smartphone and found 
Termux (https://termux.com/). It uses the apt (Debian) package manager 
to download and install pre-compiled most necessary low-level 
command-line programs like a compiler and Make and etc (installed in 
`/data/datacom.termux/files/usr'). However, I couldn't get the configure 
script for my programs running until yesterday that I randomly started 
playing with it again and found the cause and reported it to you.

I understand why Shebangs ( 
https://en.wikipedia.org/wiki/Shebang_%28Unix%29 ) would be necessary 
for non-shell interpretters (like a Python script having a `#! 
/bin/python' as its first line). But we are already running the 
configure script within the shell and don't pass any other options with 
the `#! /bin/sh' shebang.

So just out of curiosity, what is the necessity of  `#! /bin/sh' in a 
configure script? I am sure there must be things I am not aware of, but 
I am curious to know.

Maybe I can use a simple script to remove such shebangs from all the 
files in the tar-ball of a program before configuring and building it on 
my phone.

Thank you very much,
Mohammad