Gabriel Scherer 41c6f50ec8 shebangs: use `/usr/bin/env bash` instead of `/bin/bash` for BSD compat ... Currently our CI machine on FreeBSD fails to build with the following error message: ``` bytecomp/generate_runtimedef.sh runtime/caml/fail.h runtime/primitives > bytecomp/runtimedef.ml /bin/sh: bytecomp/generate_runtimedef.sh: not found ``` This PR converts all the files with a `/bin/bash` shebang to `/usr/bin/env bash`. Some files use `/bin/sh` instead, and they are unchanged. It may be the case that some 'bash' files could in fact run using 'sh', but checking this requires more work and I decided to follow the original author's intent. (Personally I like using bash explicitly as it gives a consistent programming environment that I can easily test on my machine; but this should not be at the expense of portability.)		2018-10-16 09:06:16 +02:00
..
appveyor_build.cmd	Split the AppVeyor build into two jobs	2018-09-07 08:41:54 +02:00
appveyor_build.sh	shebangs: use `/usr/bin/env bash` instead of `/bin/bash` for BSD compat	2018-10-16 09:06:16 +02:00