Am 09.08.2008 um 20:09 schrieb Axel Dörfler:
Andreas Färber <andreas.faerber@xxxxxx> wrote:This change was not supposed to be applied. Whether or not Bourne Shell is POSIX-compliant, replacing it is not an option. There are a lot of bashisms around that are not necessarily POSIX. Anyway, a better solution is to do /bin/bash configure ... but this way it's more convenient for me in my copy. In case we need it in more scripts, we should make sure that Jam uses the current shell for, e.g., build/ scripts/*.If you encounter any particular "bashisms", I would then just file a bug report for them - preferrably with a patch that fixes them, of course ;-))
As inquired before, the problem is finding out whether that is the case. If one can trust Wikipedia then Solaris is fully POSIX- and SUSv2-compliant. As background, it uses the Bourne Shell as /bin/sh, which, being traditionally a server operating system, has special security measures so that up to Solaris 9 root was not allowed to have another default shell. This was relaxed with S10 but still is the default user shell there, in OSol it's the Bourne Again Shell /bin/ bash instead.
One of the isses seemed to be the use of "local" in configure. But since we should add a notice to the ReadMe anyway concerning gawk, we could just as well instruct the user to invoke `/bin/bash configure ...` there, less work for us. :-) The build_haiku_image script for instance works nicely in Bourne Shell.
Andreas
