qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Lee Essen <lee.essen@nowonline.co.uk>
Cc: "Andreas Färber" <andreas.faerber@web.de>,
	qemu-devel@nongnu.org,
	"Stefan Hajnoczi" <stefanha@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH] fix incorrect bracket in tracetool
Date: Fri, 16 Mar 2012 14:19:45 +0100	[thread overview]
Message-ID: <4F633DF1.8010903@redhat.com> (raw)
In-Reply-To: <1EA6E838-00B8-45F3-A293-BF495BF07F7B@nowonline.co.uk>

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.

Paolo

  reply	other threads:[~2012-03-16 13:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-16 12:29 [Qemu-devel] [PATCH] fix incorrect bracket in tracetool Lee Essen
2012-03-16 12:44 ` Andreas Färber
2012-03-16 13:00   ` Lee Essen
2012-03-16 13:19     ` Paolo Bonzini [this message]
2012-03-16 13:28       ` Andreas Färber
2012-03-16 13:21     ` Andreas Färber
2012-03-16 13:18 ` Paolo Bonzini
2012-03-16 14:56   ` Eric Blake
2012-03-19 11:59 ` Stefan Hajnoczi
2012-03-19 12:05   ` Lee Essen
2012-03-19 12:32     ` Stefan Hajnoczi
2012-03-19 12:32     ` Andreas Färber
2012-03-19 13:35       ` Lee Essen
2012-03-20 16:59         ` Stefan Hajnoczi
2012-03-20 17:11           ` Lee Essen
2012-03-21  9:52             ` Stefan Hajnoczi
2012-03-19 12:40     ` Stefan Weil
2012-03-19 12:49       ` Andreas Färber

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F633DF1.8010903@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=andreas.faerber@web.de \
    --cc=lee.essen@nowonline.co.uk \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@linux.vnet.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).