From: "Khem Raj" <raj.khem@gmail.com>
To: Martin Jansa <martin.jansa@gmail.com>,
Naveen Saini <naveen.kumar.saini@intel.com>
Cc: openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [oe] [meta-oe][PATCH] tbb: upgrade 2020.3 -> 2021.2.0
Date: Wed, 21 Apr 2021 08:24:39 -0700 [thread overview]
Message-ID: <6b71b535-fd7e-e648-6e62-bdf55958c7d7@gmail.com> (raw)
In-Reply-To: <20210421111839.nkrxhzsh7ldst3a4@jama>
On 4/21/21 4:18 AM, Martin Jansa wrote:
> On Thu, Apr 08, 2021 at 06:51:17AM +0000, Naveen Saini wrote:
>>>> On Tue, Apr 6, 2021 at 11:10 PM Naveen Saini
>>>> <naveen.kumar.saini@intel.com> wrote:
>>>>>
>>>>> Switched to cmake build tool.
>>>>>
>>>>> Rebased some patches due to directory re-structuring.
>>>>> Dropped patches, which are not required anymore.
>>>>>
>>>>> Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
>>>>> rename from meta-oe/recipes-support/tbb/tbb_2020.3.bb
>>>>> rename to meta-oe/recipes-support/tbb/tbb_2021.2.0.bb
>>>>> index 8e0094b31..357fbba34 100644
>>>>> --- a/meta-oe/recipes-support/tbb/tbb_2020.3.bb
>>>>> +++ b/meta-oe/recipes-support/tbb/tbb_2021.2.0.bb
>>>>> @@ -5,37 +5,24 @@ DESCRIPTION = "Parallelism library for C++ - runtime
>>> files \
>>>>> and threading mechanism for performance and scalability."
>>>>> HOMEPAGE = "https://software.intel.com/en-us/tbb"
>>>>> LICENSE = "Apache-2.0"
>>>>> -LIC_FILES_CHKSUM =
>>> "file://LICENSE;md5=86d3f3a95c324c9479bd8986968f4327"
>>>>> -BRANCH = "tbb_2020"
>>>>> -SRCREV = "eca91f16d7490a8abfdee652dadf457ec820cc37"
>>>>> +LIC_FILES_CHKSUM =
>>> "file://LICENSE.txt;md5=86d3f3a95c324c9479bd8986968f4327"
>>>>> +BRANCH = "onetbb_2021"
>>>>> +SRCREV = "2dba2072869a189b9fdab3ffa431d3ea49059a19"
>>>>> SRC_URI = "git://github.com/oneapi-
>>> src/oneTBB.git;protocol=https;branch=${BRANCH} \
>>>>> - file://cross-compile.patch \
>>>>> - file://0001-mallinfo-is-glibc-specific-API-mark-it-so.patch \
>>>>> - file://GLIBC-PREREQ-is-not-defined-on-musl.patch \
>>>>> - file://tbb.pc \
>>>>> - file://improve-reproducibility.patch \
>>>>> + file://0001-mallinfo-is-glibc-specific-API-mark-it-so.patch \
>>>>> + file://GLIBC-PREREQ-is-not-defined-on-musl.patch \
>>>>> "
>>>>>
>>>>> S = "${WORKDIR}/git"
>>>>> -PE = "1"
>
> Why did you drop PE? Please send follow-up patch to restore it to fix:
>
right. Since its a simple change, I have sent the patch to restore it
> ERROR: tbb-2021.2.0-r0 do_packagedata: QA Issue: Package version for package tbb-dbg went backwards which would break package feeds (from 1:2020.3-r0 to 0:2021.2.0-r0) [version-going-backwards]
> ERROR: tbb-2021.2.0-r0 do_packagedata: QA Issue: Package version for package tbb-dev went backwards which would break package feeds (from 1:2020.3-r0 to 0:2021.2.0-r0) [version-going-backwards]
> ERROR: tbb-2021.2.0-r0 do_packagedata: QA Issue: Package version for package tbb-doc went backwards which would break package feeds (from 1:2020.3-r0 to 0:2021.2.0-r0) [version-going-backwards]
> ERROR: tbb-2021.2.0-r0 do_packagedata: QA Issue: Package version for package tbb-locale went backwards which would break package feeds (from 1:2020.3-r0 to 0:2021.2.0-r0) [version-going-backwards]
> ERROR: tbb-2021.2.0-r0 do_packagedata: QA Issue: Package version for package tbb-src went backwards which would break package feeds (from 1:2020.3-r0 to 0:2021.2.0-r0) [version-going-backwards]
> ERROR: tbb-2021.2.0-r0 do_packagedata: QA Issue: Package version for package tbb-staticdev went backwards which would break package feeds (from 1:2020.3-r0 to 0:2021.2.0-r0) [version-going-backwards]
> ERROR: tbb-2021.2.0-r0 do_packagedata: QA Issue: Package version for package tbb went backwards which would break package feeds (from 1:2020.3-r0 to 0:2021.2.0-r0) [version-going-backwards]
>
> Regards,
>
prev parent reply other threads:[~2021-04-21 15:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 6:22 [meta-oe][PATCH] tbb: upgrade 2020.3 -> 2021.2.0 Naveen Saini
2021-04-07 14:25 ` [oe] " Khem Raj
2021-04-07 17:32 ` Khem Raj
2021-04-08 6:51 ` Naveen Saini
2021-04-21 11:18 ` Martin Jansa
2021-04-21 15:24 ` Khem Raj [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=6b71b535-fd7e-e648-6e62-bdf55958c7d7@gmail.com \
--to=raj.khem@gmail.com \
--cc=martin.jansa@gmail.com \
--cc=naveen.kumar.saini@intel.com \
--cc=openembedded-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox