* Don't use GROFF_CSH_HACK. It would change the "#! /bin/sh" to just
":", and this causes trouble for some shells. For example, if
CONFIG_SHELL=/bin/ksh, when the groff build uses ${CONFIG_SHELL} to
run a script that has been modified in this way, ksh sees the ":" and
decided to run the script under /bin/sh instead.
* Use SH_SCRIPT_SED_CMD="1s,/bin/sh,${CONFIG_SHELL},"
to edit the "#! /bin/sh" line, to ensure that scripts
are always run under the correct shell.
9a724f1a2d