Am 16.03.2012 14:19, schrieb Paolo Bonzini: > Il 16/03/2012 14:00, Lee Essen ha scritto: >> /tmp/patch/qemu/scripts/tracetool[520]: local: not found [No such file or >> directory] >> /tmp/patch/qemu/scripts/tracetool[66]: local: not found [No such file or >> directory] >> /tmp/patch/qemu/scripts/tracetool[136]: local: not found [No such file or >> directory] >> /tmp/patch/qemu/scripts/tracetool[55]: local: not found [No such file or >> directory] >> /tmp/patch/qemu/scripts/tracetool[80]: local: not found [No such file or >> directory] >> /tmp/patch/qemu/scripts/tracetool[55]: local: not found [No such file or >> directory] >> >> From what I can see "local" isn't supported in posix ... >> "The POSIX standard supports functions, as shown above, but the semantics >> are weaker: functions do not have local traps or options, it is not possible >> to define local variables, and functions can't be exported." >> >> So I could do with some advice now on how to proceed … is the goal to keep >> posix shell compliance? Wait for a tracetool.py version? Or should I go back >> to messing with SHELL? > > I think #!/bin/bash is a better solution in the short-term.
Breaks if it's in /usr/gnu/bin or /opt/SUNWfoo/bin. :) Just like Python scripts can't rely on #!/usr/bin/env python on BeOS/Haiku in lack of /usr. The world is complicated. Andreas