So, is the issue because some platforms are shipping a non-compatible version of sh, or is the script incorrectly using bash while only claiming to use sh?
On Tue, May 5, 2015 at 3:46 PM, Dagobert Michelsen <[email protected]> wrote: > Hi, > > Am 04.05.2015 um 22:30 schrieb Ángel González <[email protected]>: >> On 04/05/15 12:54, Mariusz Balewski wrote: >>>> it looks like something fishy with your shell. Could you give us the >>>> output of "ls -l /bin/sh" ? >>>> >>>> Could you try to run instead "bash ./bootstrap" ? >>> >>> Problem already resolved. Bad shebang was the issue. As soon as I >>> changed it to #!/bin/bash - everything went well. >> >> Glad you solved it. Which shell was it using? > > This is a common problem and also happens e.g. with the Solaris /bin/sh. > I also had to use the bash-construct for the builds: > https://buildfarm.opencsw.org/buildbot/waterfall?category=wget > > > Best regards > > -- Dago > > -- > "You don't become great by trying to be great, you become great by wanting to > do something, > and then doing it so hard that you become great in the process." - xkcd #896 > -- Thanking You, Darshit Shah
