From: Hongxu Jia <hongxu.jia@windriver.com>
To: Saul Wold <saul.wold@intel.com>,
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/3] apr: upgrade to 1.5.1
Date: Wed, 4 Jun 2014 09:28:31 +0800 [thread overview]
Message-ID: <538E763F.60600@windriver.com> (raw)
In-Reply-To: <538D6C23.9060405@intel.com>
Got it, I am working on it.
//Hongxu
On 06/03/2014 02:33 PM, Saul Wold wrote:
> On 05/29/2014 08:27 PM, Hongxu Jia wrote:
>> The LICENSE has no change, except a newline added.
>>
>> Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
>> ---
>> meta/recipes-support/apr/{apr_1.4.8.bb => apr_1.5.1.bb} | 6 +++---
>> 1 file changed, 3 insertions(+), 3 deletions(-)
>> rename meta/recipes-support/apr/{apr_1.4.8.bb => apr_1.5.1.bb} (91%)
>>
>> diff --git a/meta/recipes-support/apr/apr_1.4.8.bb
>> b/meta/recipes-support/apr/apr_1.5.1.bb
>> similarity index 91%
>> rename from meta/recipes-support/apr/apr_1.4.8.bb
>> rename to meta/recipes-support/apr/apr_1.5.1.bb
>> index 0a77ad7..7f2d2ca 100644
>> --- a/meta/recipes-support/apr/apr_1.4.8.bb
>> +++ b/meta/recipes-support/apr/apr_1.5.1.bb
>> @@ -4,7 +4,7 @@ SECTION = "libs"
>> DEPENDS = "util-linux"
>>
>> LICENSE = "Apache-2.0"
>> -LIC_FILES_CHKSUM =
>> "file://LICENSE;md5=0c35ff3c4c83b89d2f076e315caac28b \
>> +LIC_FILES_CHKSUM =
>> "file://LICENSE;md5=4dfd4cd216828c8cae5de5a12f3844c8 \
>> file://include/apr_lib.h;endline=17;md5=ee42fa7575dc40580a9e01c1b75fae96"
>>
>> BBCLASSEXTEND = "native"
>> @@ -16,8 +16,8 @@ SRC_URI = "${APACHE_MIRROR}/apr/${BPN}-${PV}.tar.bz2 \
>> file://run-ptest \
>> "
>>
>> -SRC_URI[md5sum] = "ce2ab01a0c3cdb71cf0a6326b8654f41"
>> -SRC_URI[sha256sum] =
>> "61b8d2f8d321c6365ee3d71d0bb41f3a89c44da6124cc5b407a3b8319d660421"
>> +SRC_URI[md5sum] = "5486180ec5a23efb5cae6d4292b300ab"
>> +SRC_URI[sha256sum] =
>> "e94abe431d4da48425fcccdb27b469bd0f8151488f82e5630a56f26590e198ac"
>>
>> inherit autotools-brokensep lib_package binconfig multilib_header
>> ptest
>>
>>
> There may be an issue with your apr udpate:
>
> https://autobuilder.yoctoproject.org/main/builders/build-appliance/builds/122/steps/BuildImages/logs/stdio
>
>
>
> Sau!
>
next prev parent reply other threads:[~2014-06-04 1:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-30 3:27 [PATCH V2 0/3] upgrade: apr to 1.5.1 and apr-utils to 1.5.3 Hongxu Jia
2014-05-30 3:27 ` [PATCH 1/3] apr: upgrade to 1.5.1 Hongxu Jia
2014-06-03 6:33 ` Saul Wold
2014-06-04 1:28 ` Hongxu Jia [this message]
2014-05-30 3:27 ` [PATCH 2/3] apr: fix cross compiling failed Hongxu Jia
2014-05-30 11:22 ` Burton, Ross
2014-05-30 3:27 ` [PATCH 3/3] apr-util: upgrade to 1.5.3 Hongxu Jia
-- strict thread matches above, loose matches on Subject: below --
2014-05-28 9:05 [PATCH 0/3] upgrade: apr to 1.5.1 and apr-utils " Hongxu Jia
2014-05-28 9:05 ` [PATCH 1/3] apr: upgrade to 1.5.1 Hongxu Jia
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=538E763F.60600@windriver.com \
--to=hongxu.jia@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=saul.wold@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox