From: "Mikko Rapeli" <mikko.rapeli@bmw.de>
To: <Harpritkaur.Bhandari@kpit.com>
Cc: <openembedded-devel@lists.openembedded.org>, <raj.khem@gmail.com>,
<nisha.parrakat@kpit.com>, <Aditya.Tayade@kpit.com>
Subject: Re: [oe] [meta-oe][dunfell][PATCH] rapidjson: Upgrade SRCREV to latest
Date: Thu, 21 Jan 2021 11:57:17 +0000 [thread overview]
Message-ID: <YAlsHMz2Unf8YfVb@korppu> (raw)
In-Reply-To: <1611122392-13465-1-git-send-email-Harpritkaur.Bhandari@kpit.com>
Hi,
On Wed, Jan 20, 2021 at 11:29:52AM +0530, Harpritkaur Bhandari wrote:
> Upgrade SRCREV to latest as it fixes the below issue:
> Running UndefinedBehaviorSanitizer on projects that use
> rapidjson triggers 'applying non-zero offset <NN> to null
> pointer' findings in 'internal/stack.h' which are hard
> to suppress by library users.
> Removed "0001-CMake-remove-hardcoded-CMAKECONFIG_INSTALL_DIR-path.patch"
> as the changes are already incorporated in the latest
> codebase.
> As per abi-compliance-checker report the source compatibility
> and binary compatibility between previous SRCREV
> 6a905f9311f82d306da77bd963ec5aa5da07da9c and current
> SRCREV 0ccdbf364c577803e2a751f5aededce935314313
> is 100% and this patch is already tested on 64bit
> ARM (aarch64) in a product with on target CI tests.
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> (cherry picked from commit 04d9ea0ba7ece968244bf049893dd5636675b76f)
> Signed-off-by: Harpritkaur Bhandari <Harpritkaur.Bhandari@kpit.com>
> ---
> meta-oe/recipes-devtools/rapidjson/rapidjson_git.bb | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/meta-oe/recipes-devtools/rapidjson/rapidjson_git.bb b/meta-oe/recipes-devtools/rapidjson/rapidjson_git.bb
> index e3ed9c6..5b5c8b2 100644
> --- a/meta-oe/recipes-devtools/rapidjson/rapidjson_git.bb
> +++ b/meta-oe/recipes-devtools/rapidjson/rapidjson_git.bb
> @@ -4,10 +4,9 @@ SECTION = "libs"
> LICENSE = "MIT"
> LIC_FILES_CHKSUM = "file://license.txt;md5=ba04aa8f65de1396a7e59d1d746c2125"
>
> -SRC_URI = "git://github.com/miloyip/rapidjson.git;nobranch=1 \
> - file://0001-CMake-remove-hardcoded-CMAKECONFIG_INSTALL_DIR-path.patch"
Please also remove the patch file. Also from master branch if it's still there
but no longer applied.
Cheers,
-Mikko
> +SRC_URI = "git://github.com/miloyip/rapidjson.git;nobranch=1"
>
> -SRCREV = "6a905f9311f82d306da77bd963ec5aa5da07da9c"
> +SRCREV = "0ccdbf364c577803e2a751f5aededce935314313"
>
> PV = "1.1.0+git${SRCPV}"
>
> --
> 2.7.4
>
> This message contains information that may be privileged or confidential and is the property of the KPIT Technologies Ltd. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. KPIT Technologies Ltd. does not accept any liability for virus infected mails.
>
>
>
prev parent reply other threads:[~2021-01-21 11:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 5:59 [meta-oe][dunfell][PATCH] rapidjson: Upgrade SRCREV to latest Harpritkaur Bhandari
2021-01-21 11:57 ` Mikko Rapeli [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=YAlsHMz2Unf8YfVb@korppu \
--to=mikko.rapeli@bmw.de \
--cc=Aditya.Tayade@kpit.com \
--cc=Harpritkaur.Bhandari@kpit.com \
--cc=nisha.parrakat@kpit.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.