From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Robert Yang <liezhi.yang@windriver.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 3/4] autogen: update libopts.m4's patch
Date: Fri, 14 Apr 2017 10:46:32 +0100 [thread overview]
Message-ID: <1492163192.19076.16.camel@linuxfoundation.org> (raw)
In-Reply-To: <8dda2297e14acc1d586c4e5f1195846f14eb4a52.1492077359.git.liezhi.yang@windriver.com>
On Thu, 2017-04-13 at 02:57 -0700, Robert Yang wrote:
> Use 'test -n "$POSIX_SHELL"' rather than 'test -x "$POSIX_SHELL"' so
> that 'POSIX_SHELL = "/usr/bin/env sh"' can work.
> Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
> ---
> .../0001-config-libopts.m4-regenerate-it-from-config-
> libopts..patch | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-devtools/autogen/autogen/0001-config-
> libopts.m4-regenerate-it-from-config-libopts..patch b/meta/recipes-
> devtools/autogen/autogen/0001-config-libopts.m4-regenerate-it-from-
> config-libopts..patch
> index a14018e..e247594 100644
> --- a/meta/recipes-devtools/autogen/autogen/0001-config-libopts.m4-
> regenerate-it-from-config-libopts..patch
> +++ b/meta/recipes-devtools/autogen/autogen/0001-config-libopts.m4-
> regenerate-it-from-config-libopts..patch
> @@ -30,7 +30,7 @@ index c7ba4f3..51e6a39 100644
> AC_PROG_SED
> [while :
> do
> -+ test -x "$POSIX_SHELL" && break
> ++ test -n "$POSIX_SHELL" && break
> POSIX_SHELL=`which bash`
> test -x "$POSIX_SHELL" && break
> POSIX_SHELL=`which dash`
The patch title makes this sound it it was some kind of regenerated
file. You're then patching this for a rather subtle bug. I worry that
this change is going to get lost in the future when someone regenerates
this.
I'm wondering if we can find a better, more future proof solution?
Cheers,
Richard
next prev parent reply other threads:[~2017-04-14 9:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-13 9:57 [PATCH 0/4] meta: 4 fixes Robert Yang
2017-04-13 9:57 ` [PATCH 1/4] binconfig.bbclass: fix typo in get_binconfig_mangle() Robert Yang
2017-04-13 9:57 ` [PATCH 2/4] apt: fix libdir path for apt.systemd.daily Robert Yang
2017-04-13 9:57 ` [PATCH 3/4] autogen: update libopts.m4's patch Robert Yang
2017-04-14 9:36 ` Robert Yang
2017-04-14 9:46 ` Richard Purdie [this message]
2017-04-14 9:49 ` Robert Yang
2017-04-13 9:57 ` [PATCH 4/4] grep: do_configure: fix "Argument list too long" Robert Yang
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=1492163192.19076.16.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=liezhi.yang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
/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.