On Thu, 4 Jun 2015, Dirk Hohndel wrote: > > On Jun 4, 2015, at 12:14 AM, Willem Ferguson > > <[email protected]> wrote: > > > > I get this: > > > > src$ sh subsurface/scripts/build.sh > > exec 1> >(tee build.log) 2>&1 > > subsurface/scripts/build.sh: 21: subsurface/scripts/build.sh: Syntax error: > > redirection unexpected > > > > Am I only half awake again? (Arrived from Tanzania at 3 am this > > morning, so only 2 brain cells firing) > > Let me guess. You're running this on one of those silly distributions > where sh is not bash?
Now, really... Why do you state that? _That's_ silly. `man 1 bash': ,---- | BUGS | It's too big and too slow. | | There are some subtle differences between bash and traditional | versions of sh, mostly because of the POSIX specification. | | Aliases are confusing in some uses. | | Shell builtin commands and functions are not stoppable/restartable. | | Compound commands and command sequences of the form `a ; b ; c' are | not handled gracefully when process suspension is attempted. When a | process is stopped, the shell immediately executes the next command | in the sequence. It suffices to place the sequence of commands between | parentheses to force it into a subshell, which may be stopped as a | unit. | | Array variables may not (yet) be exported. | | There may be only one active coprocess at a time. `---- You stuck bash on the shebang line. Such error can only happen if /bin/bash is a symlink to some other shell, I guess. Is that the case? Cheers, -- Cristian _______________________________________________ subsurface mailing list [email protected] http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
