From: Wenlin Kang <wenlin.kang@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] bash: fixed bash build error
Date: Fri, 23 May 2014 17:45:20 +0800 [thread overview]
Message-ID: <537F18B0.6060009@windriver.com> (raw)
In-Reply-To: <CAJTo0LYb9vqXFTLwEczYzafcAPv8yuo8isK00ViPvOF=YsFPsw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1044 bytes --]
On 2014年05月23日 17:29, Burton, Ross wrote:
> First, bash builds fine for me, so can you elaborate on what the
> situation that causes the failure is.
build bash, then check temp/log.do_install, we can see error , this
trigger when builds in bash/po/
> The patch is missing upstream-status and signed-off-by. For build
> fixes I'd hope that there would be communication with upstream.
>
> On 23 May 2014 09:31, Wenlin Kang <wenlin.kang@windriver.com> wrote:
>> +--- bash-4.3-org/aclocal.m4 2014-05-23 15:28:54.252565146 +0800
>> ++++ bash-4.3/aclocal.m4 2014-05-23 15:33:19.924570133 +0800
> aclocal.m4 is overwritten in do_configure when we run autoreconf so
> anything changed in that file will be lost.
in bash, I have double checking, original a clocal.m4 will be
"cat" to acinclude.m4 at begin of do_configure not changed,
and after regenerated acloacl.m4 will include acinclude.m4, so the
changing in original aclocal.m4 will be not lost.
>
> Ross
>
>
--
Thanks,
Wenlin Kang
[-- Attachment #2: Type: text/html, Size: 2099 bytes --]
next prev parent reply other threads:[~2014-05-23 9:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-23 8:31 [PATCH] bash: fixed bash build error Wenlin Kang
2014-05-23 9:29 ` Burton, Ross
2014-05-23 9:45 ` Wenlin Kang [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-06-03 5:59 Wenlin Kang
2014-06-03 6:58 ` Richard Purdie
2014-06-03 7:35 ` Wenlin Kang
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=537F18B0.6060009@windriver.com \
--to=wenlin.kang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--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.