This is because, for example, on the host system, sh might be /bin/sh,
but on the target system, it's /system/bin/sh.
The new variable is "targetsh" and defaults to "sh" unless changed by the hints file/Configure params.
hostperl=''
hostgenerate=''
hostosname=''
+targetsh=''
extern_C=''
mistrustnm=''
usedevel=''
;;
esac
+: When cross-compiling we need to separate the sh-to-run-Configure-with from the sh-to-use-in-Perl
+: default both to the same thing, cross-compilers can then set targetsh differently if they like
+targetsh=$sh
+
: see if sh knows # comments
if `$sh -c '#' >/dev/null 2>&1`; then
shsharp=true
targethost='$targethost'
targetmkdir='$targetmkdir'
targetport='$targetport'
+targetsh='$targetsh'
tbl='$tbl'
tee='$tee'
test='$test'
* /bin/pdksh, /bin/ash, /bin/bash, or even something such as
* D:/bin/sh.exe.
*/
-#define SH_PATH "$sh" /**/
+#define SH_PATH "$targetsh" /**/
/* SIG_NAME:
* This symbol contains a list of signal names in order of