SHC fails if bash script starts with : "#!/usr/bin/env bash" it has to be "#!/usr/bin/bash"

[Jim-JMCD]

SHC fails if bash script starts with : #!/usr/bin/env bash it has to be #!/usr/bin/bash

Error message: shc Unknown shell (env): specify [-i][-x][-l]

Problem could be easily fixed by adding to documentation.

---

No where in the documentation or man pages does mention which shell it is compatible with.
#!/usr/bin/bash or #!/usr/bin/sh. There is the assumption that a SHC binary created in bash environment is for a bash shell environment, similarly the sh shell. What about other shells?

[metacollin]

From the description in the man pages:

The compiled binary will still be dependent on the shell specified in the first line of the shell code (i.e. #!/bin/sh), thus shc does not create completely independent binaries.

/usr/bin/env is not a shell binary. Of course shc isn't going to work if the first line of your bash script is not a path to a shell binary. This is thoroughly implicit from the documentation as well as the entire point of shc.

Not only is it not the responsibility of shc's documentation to educate users in basic operating system competency, I assert that it shouldn't. If a user doesn't understand what is and isn't a shell binary and how to find the path to one, then shc's documentation is not where they should be learning it from.

[Jim-JMCD]

Its is trivial to update the documentation that it will not accept #!/bin/env sh
Otherwise its a timewaster it problem solving, then again not everybody can be bothered with RTFM.

There's debate whether hard coding a shell location in a script is better than the using that set by an environment variable. Both are commonly used.