From: "Yu, Mingli" <mingli.yu@windriver.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-oe][PATCH 2/2] log4cplus: Upgrade to 2.0.4
Date: Mon, 22 Jul 2019 14:18:46 +0800 [thread overview]
Message-ID: <5D355546.4090007@windriver.com> (raw)
In-Reply-To: <CAMKF1sqTTzTSgXFHeizk7hgdCJ9=sBjJ56_BtNk1mJWf1FN5Ag@mail.gmail.com>
On 2019年07月22日 00:27, Khem Raj wrote:
> seeing gold linker crash on arm
>
> https://errors.yoctoproject.org/Errors/Details/253440/
>
> however, this is a linker problem which is latent until this, I would
> like to see if we can find a solution
> before applying this patch
Hi Khem,
I didn't encounter the linker problem on arm as you mentioned in my
local env.
Thanks,
>
> On Wed, Jul 17, 2019 at 9:21 PM <mingli.yu@windriver.com> wrote:
>>
>> From: Mingli Yu <mingli.yu@windriver.com>
>>
>> Signed-off-by: Mingli Yu <mingli.yu@windriver.com>
>> ---
>> .../log4cplus/{log4cplus_2.0.3.bb => log4cplus_2.0.4.bb} | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>> rename meta-oe/recipes-devtools/log4cplus/{log4cplus_2.0.3.bb => log4cplus_2.0.4.bb} (81%)
>>
>> diff --git a/meta-oe/recipes-devtools/log4cplus/log4cplus_2.0.3.bb b/meta-oe/recipes-devtools/log4cplus/log4cplus_2.0.4.bb
>> similarity index 81%
>> rename from meta-oe/recipes-devtools/log4cplus/log4cplus_2.0.3.bb
>> rename to meta-oe/recipes-devtools/log4cplus/log4cplus_2.0.4.bb
>> index 56c62f1f2..d86521aba 100644
>> --- a/meta-oe/recipes-devtools/log4cplus/log4cplus_2.0.3.bb
>> +++ b/meta-oe/recipes-devtools/log4cplus/log4cplus_2.0.4.bb
>> @@ -7,8 +7,8 @@ LICENSE = "Apache-2.0 & BSD-2-Clause"
>> LIC_FILES_CHKSUM = "file://LICENSE;md5=41e8e060c26822886b592ab4765c756b"
>>
>> SRC_URI = "${SOURCEFORGE_MIRROR}/project/${BPN}/${BPN}-stable/${PV}/${BP}.tar.gz"
>> -SRC_URI[md5sum] = "20a87090cd8ec34ea11b3e59954234cb"
>> -SRC_URI[sha256sum] = "2d8f627aa6417e6c6a100bc09dc407684ca4605c929defc1690ee7d6a575ce6a"
>> +SRC_URI[md5sum] = "2b5b7bc294698bf30a315a259ef9eec2"
>> +SRC_URI[sha256sum] = "196eedbc7f2dd792dae721b1159c7ac132255bb368226353c24d4d5fa7c7797a"
>>
>> UPSTREAM_CHECK_URI = "https://sourceforge.net/projects/log4cplus/files/log4cplus-stable/"
>> UPSTREAM_CHECK_REGEX = "log4cplus-stable/(?P<pver>\d+(\.\d+)+)/"
>> --
>> 2.21.0
>>
>> --
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>
prev parent reply other threads:[~2019-07-22 6:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 4:21 [meta-oe][PATCH 1/2] fio: Upgrade to 3.15 mingli.yu
2019-07-18 4:21 ` [meta-oe][PATCH 2/2] log4cplus: Upgrade to 2.0.4 mingli.yu
2019-07-21 16:27 ` Khem Raj
2019-07-21 17:20 ` Adrian Bunk
2019-07-21 17:37 ` Khem Raj
2019-07-21 19:33 ` Adrian Bunk
2019-07-22 6:18 ` Yu, Mingli [this message]
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=5D355546.4090007@windriver.com \
--to=mingli.yu@windriver.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=raj.khem@gmail.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.