All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Färber" <andreas.faerber@web.de>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Lee Essen <lee.essen@nowonline.co.uk>,
	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:28:41 +0100	[thread overview]
Message-ID: <4F634009.70608@web.de> (raw)
In-Reply-To: <4F633DF1.8010903@redhat.com>

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

  reply	other threads:[~2012-03-16 13:29 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
2012-03-16 13:28       ` Andreas Färber [this message]
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=4F634009.70608@web.de \
    --to=andreas.faerber@web.de \
    --cc=lee.essen@nowonline.co.uk \
    --cc=pbonzini@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.