From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Phil Blundell <philb@brightsign.biz>,
Martin Jansa <martin.jansa@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] flex: updated to 2.5.37
Date: Sun, 12 May 2013 08:32:18 +0100 [thread overview]
Message-ID: <1368343938.21569.1.camel@ted> (raw)
In-Reply-To: <CAJTo0LYgAzXW4PEt_KucpDG7Uk5rpXJEDzWPGTgA7X3jZkU-yQ@mail.gmail.com>
On Fri, 2013-05-10 at 12:00 +0100, Burton, Ross wrote:
> On 10 May 2013 11:50, Phil Blundell <philb@brightsign.biz> wrote:
> > Or you could replace the shell wrapper that create_wrapper() currently
> > generates with either a compiled binary or a Python script. That would
> > allow you to execl("/path/foo.real", "foo", ...), which I don't think
> > you can do in shell but which would avoid this whole class of problem.
>
> Bash can do that, but it's not POSIX. :/
I'm quite happy to have the wrapper as bash shell script. We only need
dash compatibility in things that get run under /bin/sh (i.e. bitbake
shell tasks).
Cheers,
Richard
next prev parent reply other threads:[~2013-05-12 7:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-10 10:15 [PATCH] flex: updated to 2.5.37 Bogdan Marinescu
2013-05-10 10:13 ` Marinescu, Bogdan A
2013-05-10 10:20 ` Martin Jansa
2013-05-10 10:32 ` Richard Purdie
2013-05-10 10:37 ` Martin Jansa
2013-05-10 10:46 ` Phil Blundell
2013-05-10 10:50 ` Phil Blundell
2013-05-10 11:00 ` Burton, Ross
2013-05-12 7:32 ` Richard Purdie [this message]
2013-05-27 7:48 ` Marinescu, Bogdan A
-- strict thread matches above, loose matches on Subject: below --
2013-01-31 11:53 Bogdan Marinescu
2013-01-31 16:30 ` Richard Purdie
2013-02-01 10:29 ` Marinescu, Bogdan A
2013-02-01 14:56 ` Richard Purdie
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=1368343938.21569.1.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=philb@brightsign.biz \
--cc=ross.burton@intel.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.