Ben Reser <b...@reser.org> writes: > On 3/6/14, 10:29 AM, Philip Martin wrote: >> It's also used in SVN_REMOVE_STANDARD_LIB_DIRS and so it is what is >> causing the Solaris fails with some shells. > > Being in POSIX just isn't good enough. POSIX has a lot of features that very > basic shells just don't have. Solaris sadly is a major platform that has a > /bin/sh that is missing a lot of stuff that POSIX says you should have. I > think it also has a POSIX compliant shell but it's a hassle to users to tell > people to specify a different shell. A hassle we can usually avoid by just > using a slightly different syntax. > > Philip is working on a buildbot on Solaris so hopefully these sorts of things > will be exposed more quickly and we won't end up having end users telling us.
configure itself attempts to choose a working shell. The Solaris box gives me SHELL=/bin/bash on login. Both configure and config.nice start with #!/bin/sh and configure would fail if it simply used that. However it doesn't fail because configure has code to test and exec so that it runs with SHELL=/bin/bash. I have to go out of my way to force /bin/sh to get configure to fail. -- Philip Martin | Subversion Committer WANdisco // *Non-Stop Data*
