[meta-intel] Retaining of rpm database issue

2018-01-04 Thread Raj srinivas
Hi all,

I am using yocto 1.7.3 , i want to get the rpm database in sdk, for that i
have added package-management in IMAGE FEATURES, after extracting the sdk,
iam not able to rebuild the database , i have tried deleting the db files,
still iam facing below issue, any body can please help on below eroor,

bash-3.2# rpm --rebuilddb
rpmdb: BDB1538 Program version 5.3 doesn't match environment version 6.0
rpmdb: BDB2531 Unacceptable log file /var/lib/rpm/./log/log.07:
unsupported log version 21
rpmdb: BDB2527 Invalid log file: log.07: Invalid argument
rpmdb: BDB0061 PANIC: Invalid argument
==> rpmdbe_event_notify(0x2d618, PANIC(0), 0xf6ffd2bc) app_private (nil)
rpmdb: BDB1546 unable to join the environment

error: cannot open Packages(0) index: (-30973)
DB: Berkeley DB 5.3.28: (September  9, 2013)
error: cannot open Packages database in /var/lib/rpm


bash-3.2# rpm -qa
rpmdb: BDB2531 Unacceptable log file /var/lib/rpm/./log/log.07:
unsupported log version 21
rpmdb: BDB2527 Invalid log file: log.07: Invalid argument
rpmdb: BDB0061 PANIC: Invalid argument
==> rpmdbe_event_notify(0x2d780, PANIC(0), 0xf6ffe184) app_private (nil)
rpmdb: BDB1546 unable to join the environment


Regards,
raj
-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel


Re: [meta-intel] [PATCH 1/3] dpdk-dev-libibverbs: fix do_fetch failure in case of multilib

2018-01-04 Thread Mark Asselstine
On Wednesday, January 3, 2018 2:02:31 PM EST Cal Sullivan wrote:
> In actually testing this patch, I noticed that I was getting a fetcher
> warning. After a little investigation I found that
> https://github.com/Mellanox/dpdk-dev-libibverbs no longer exists and
> we're only getting this thanks to the YP mirroring. Do you know of any
> other location we could point to?

Maybe we should actually take this as a signal to revisit things. I am having 
to piece things together as some of the history is lost with the removal of 
the dpdk-dev-libibverbs repo and newer revisions of Mellanox DPDK pages but I 
think we have enough to go on to move forward.

Looking at the history it appears as though dpdk-dev-libibverbs was and 
"optimized" version of libibverbs for the ConnectX-3 (reference: https://
community.mellanox.com/docs/DOC-2197). The fact that Mellanox has dropped the 
repository and now simply references libibverbs (and not dpdk-dev-libibverbs) 
in its latest revision of the Mellanox DPDK documentation (reference: https://
community.mellanox.com/docs/DOC-1502). Leads me to believe that we should move 
on to simply use the latest release of libibverbs.

So I really think the best solution is to drop dpdk-dev-libibverbs and simply 
use libibverbs. This would drop the need to do any of the 'virtual/' do 
jiggery. We can host the libibverbs recipe here still or move to oe-core, 
Bruce can use PREFERRED_VERSION to continue to use the required version in 
meta-cloud-services...

Sorry about taking my time in coming to this conclusion. I was short on time 
and flush with work before the holiday so didn't dig in enough to make the 
right call.

MarkA

> 
> Thanks,
> Cal
> 
> On 01/02/2018 05:27 PM, Chen Qi wrote:
> > Fix to correctly set SRC_URI and S to avoid do_fetch failure in case of
> > multilib.
> > 
> > Signed-off-by: Chen Qi 
> > ---
> > 
> >   .../dpdk-dev-libibverbs/dpdk-dev-libibverbs_1.2.1-3.4-2.0.0.0.bb  | 8
> >    1 file changed, 4 insertions(+), 4 deletions(-)
> > 
> > diff --git
> > a/recipes-extended/dpdk-dev-libibverbs/dpdk-dev-libibverbs_1.2.1-3.4-2.0.
> > 0.0.bb
> > b/recipes-extended/dpdk-dev-libibverbs/dpdk-dev-libibverbs_1.2.1-3.4-2.0.
> > 0.0.bb index e40c63b..9118494 100644
> > ---
> > a/recipes-extended/dpdk-dev-libibverbs/dpdk-dev-libibverbs_1.2.1-3.4-2.0.
> > 0.0.bb +++
> > b/recipes-extended/dpdk-dev-libibverbs/dpdk-dev-libibverbs_1.2.1-3.4-2.0.
> > 0.0.bb @@ -3,7 +3,7 @@ HOMEPAGE =
> > "https://github.com/Mellanox/dpdk-dev-libibverbs";> 
> >   LICENSE = "GPLv2"
> >   LIC_FILES_CHKSUM = 
> >   "file://COPYING;md5=7c557f27dd795ba77cc419dddc656b51"
> > 
> > -SRC_URI =
> > "https://github.com/Mellanox/dpdk-dev-libibverbs/archive/libibverbs-${PV}
> > .tar.gz;name=${PN} \ +SRC_URI =
> > "https://github.com/Mellanox/dpdk-dev-libibverbs/archive/libibverbs-${PV}
> > .tar.gz \> 
> >  file://init_c.patch \
> >  file://0001-Fix-build-with-clang.patch \
> >  file://0002-typecast-enum-to-int-before-comparison.patch \
> > 
> > @@ -11,8 +11,8 @@ SRC_URI =
> > "https://github.com/Mellanox/dpdk-dev-libibverbs/archive/libibverbs-${> 
> >  file://0004-Fix-clang-warnings.patch \
> >  "
> > 
> > -SRC_URI[dpdk-dev-libibverbs.md5sum] = "65234ee278eb437a7069326f37cd4d86"
> > -SRC_URI[dpdk-dev-libibverbs.sha256sum] =
> > "a6471515556cb8d10ad471bb7efb8cf760b248a28aceb57d4534d50d572f56cd"
> > +SRC_URI[md5sum] = "65234ee278eb437a7069326f37cd4d86"
> > +SRC_URI[sha256sum] =
> > "a6471515556cb8d10ad471bb7efb8cf760b248a28aceb57d4534d50d572f56cd"> 
> >   # A machine needs to enable this using:
> >   # COMPATIBLE_MACHINE_pn-dpdk-dev-libibverbs = ""
> > 
> > @@ -20,7 +20,7 @@ SRC_URI[dpdk-dev-libibverbs.sha256sum] =
> > "a6471515556cb8d10ad471bb7efb8cf760b248> 
> >   COMPATIBLE_MACHINE = "null"
> >   COMPATIBLE_HOST_libc-musl_class-target = "null"
> > 
> > -S = "${WORKDIR}/${PN}-libibverbs-${PV}"
> > +S = "${WORKDIR}/dpdk-dev-libibverbs-libibverbs-${PV}"
> > 
> >   COMPATIBLE_HOST = '(i.86|x86_64).*-linux'
> >   DEPENDS = "libnl"


-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel


Re: [meta-intel] [PATCH 1/3] dpdk-dev-libibverbs: fix do_fetch failure in case of multilib

2018-01-04 Thread Bruce Ashfield
On Wed, Jan 3, 2018 at 8:56 PM, ChenQi  wrote:
> On 01/04/2018 03:02 AM, Cal Sullivan wrote:
>>
>> In actually testing this patch, I noticed that I was getting a fetcher
>> warning. After a little investigation I found that
>> https://github.com/Mellanox/dpdk-dev-libibverbs no longer exists and we're
>> only getting this thanks to the YP mirroring. Do you know of any other
>> location we could point to?
>>
>> Thanks,
>> Cal
>>
>
> Hi Cal,
>
> I don't know any other location. It seems that this project no longer
> exists.
> Could you directly point the SRC_URI to yocto download location?
>
> There's a libibverbs recipe in meta-cloud-services. When I started to solve
> this conflict problem, there were two choices in front of me.
> 1) Use 'virtual/libibverbs' approach.
> 2) Drop one recipe, put the other in a common local (e.g. meta-oe layer),
> and make meta-dpdk and meta-cloud-services depend on that layer.
>
> I finally chose the first one, because
> 1) it would definitely bring in no regression problem. Users could choose
> libibverbs or dpdk-dev-libibverbs as they like.
> 2) I was not sure why dpdk-dev-libibverbs recipe was created in the first
> place.
>
> Anyway, for this SRC_URI problem, if we couldn't be sure that
> dpdk-dev-libibverbs is not necessary, let's just point the SRC_URI to yocto
> download location; otherwise, maybe the second approach above could be used.

I'm going to have to carry a different recipe in meta-cloud-services
regardless, due
to version and feature requirements that we have in the system level use cases.

So any solution that involves dropping the recipe there and moving things to a
single location, won't fly.

Cheers,

Bruce

>
> Best Regards,
> Chen Qi
>
>
>
>> On 01/02/2018 05:27 PM, Chen Qi wrote:
>>>
>>> Fix to correctly set SRC_URI and S to avoid do_fetch failure in case of
>>> multilib.
>>>
>>> Signed-off-by: Chen Qi 
>>> ---
>>> .../dpdk-dev-libibverbs/dpdk-dev-libibverbs_1.2.1-3.4-2.0.0.0.bb | 8
>>> 
>>>   1 file changed, 4 insertions(+), 4 deletions(-)
>>>
>>> diff --git
>>> a/recipes-extended/dpdk-dev-libibverbs/dpdk-dev-libibverbs_1.2.1-3.4-2.0.0.0.bb
>>> b/recipes-extended/dpdk-dev-libibverbs/dpdk-dev-libibverbs_1.2.1-3.4-2.0.0.0.bb
>>> index e40c63b..9118494 100644
>>> ---
>>> a/recipes-extended/dpdk-dev-libibverbs/dpdk-dev-libibverbs_1.2.1-3.4-2.0.0.0.bb
>>> +++
>>> b/recipes-extended/dpdk-dev-libibverbs/dpdk-dev-libibverbs_1.2.1-3.4-2.0.0.0.bb
>>> @@ -3,7 +3,7 @@ HOMEPAGE =
>>> "https://github.com/Mellanox/dpdk-dev-libibverbs";
>>>   LICENSE = "GPLv2"
>>>   LIC_FILES_CHKSUM =
>>> "file://COPYING;md5=7c557f27dd795ba77cc419dddc656b51"
>>>   -SRC_URI =
>>> "https://github.com/Mellanox/dpdk-dev-libibverbs/archive/libibverbs-${PV}.tar.gz;name=${PN}
>>> \
>>> +SRC_URI =
>>> "https://github.com/Mellanox/dpdk-dev-libibverbs/archive/libibverbs-${PV}.tar.gz
>>> \
>>>  file://init_c.patch \
>>>  file://0001-Fix-build-with-clang.patch \
>>> file://0002-typecast-enum-to-int-before-comparison.patch \
>>> @@ -11,8 +11,8 @@ SRC_URI =
>>> "https://github.com/Mellanox/dpdk-dev-libibverbs/archive/libibverbs-${
>>>  file://0004-Fix-clang-warnings.patch \
>>>  "
>>>   -SRC_URI[dpdk-dev-libibverbs.md5sum] =
>>> "65234ee278eb437a7069326f37cd4d86"
>>> -SRC_URI[dpdk-dev-libibverbs.sha256sum] =
>>> "a6471515556cb8d10ad471bb7efb8cf760b248a28aceb57d4534d50d572f56cd"
>>> +SRC_URI[md5sum] = "65234ee278eb437a7069326f37cd4d86"
>>> +SRC_URI[sha256sum] =
>>> "a6471515556cb8d10ad471bb7efb8cf760b248a28aceb57d4534d50d572f56cd"
>>> # A machine needs to enable this using:
>>>   # COMPATIBLE_MACHINE_pn-dpdk-dev-libibverbs = ""
>>> @@ -20,7 +20,7 @@ SRC_URI[dpdk-dev-libibverbs.sha256sum] =
>>> "a6471515556cb8d10ad471bb7efb8cf760b248
>>>   COMPATIBLE_MACHINE = "null"
>>>   COMPATIBLE_HOST_libc-musl_class-target = "null"
>>>   -S = "${WORKDIR}/${PN}-libibverbs-${PV}"
>>> +S = "${WORKDIR}/dpdk-dev-libibverbs-libibverbs-${PV}"
>>>   COMPATIBLE_HOST = '(i.86|x86_64).*-linux'
>>>   DEPENDS = "libnl"
>>
>>
>>
>
> --
> ___
> meta-intel mailing list
> meta-intel@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-intel



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel