[OE-core] [PATCH 0/4] Fix some issues of kernel/image recipes

2017-03-19 Thread liu . ming50
From: Ming Liu The changes include: kernel.bbclass: introduce INITRAMFS_IMAGE_NAME kernel.bbclass: handle kernel-vmlinux in KERNEL_IMAGETYPES image.bbclass: remove initramfs bundle related code kernel-initramfs: add recipe Ming Liu (4): kernel.bbclass: introduce INITRAMFS_IMAGE_NAME kernel.b

[OE-core] [PATCH 1/4] kernel.bbclass: introduce INITRAMFS_IMAGE_NAME

2017-03-19 Thread liu . ming50
From: Ming Liu It defaults to ${INITRAMFS_IMAGE}-${MACHINE} if INITRAMFS_IMAGE is not empty. This allows the end users to be able to override the initramfs image name with a customized value. Signed-off-by: Ming Liu --- meta/classes/kernel-fitimage.bbclass | 10 +- meta/classes/kernel

[OE-core] [PATCH 3/4] image.bbclass: remove initramfs bundle related code

2017-03-19 Thread liu . ming50
From: Ming Liu The original purpose of these code was to repackage initramfs bundled kernel before image do_build, but it does not really work because the initramfs bundled kernel images are not packaged at all after commit a49569e3a7534779bbe3f01a0647fd076c95798d: [ kernel.bbclass: do not copy b

[OE-core] [PATCH 2/4] kernel.bbclass: handle kernel-vmlinux in KERNEL_IMAGETYPES

2017-03-19 Thread liu . ming50
From: Ming Liu There is a mess after KERNEL_IMAGETYPES was introduced in commit 849b67b2: [ kernel: Add KERNEL_IMAGETYPES to build multi types kernel at one time ] There are two packages both providing vmlinux image if 'vmlinux' is set in KERNEL_IMAGETYPES, they are kernel-vmlinux and kernel-ima

[OE-core] [PATCH 4/4] kernel-initramfs: add recipe

2017-03-19 Thread liu . ming50
From: Ming Liu To implement initramfs bundled kernel packaging. The kernel images are copied from DEPLOY_DIR_IMAGE, and a list of packages will be generated according to KERNEL_IMAGETYPES setting. For instance: For KERNEL_IMAGETYPES = "bzImage vmlinux" the generated packages would be: - kernel

[OE-core] What is the purpose of /usr/lib/.build-id?

2017-03-19 Thread Peter Kjellerstedt
I have recently noticed the directory /usr/lib/.build-id in the RPM packages generated by master of OE-core. It contains hashed links to the binaries in the package. What is it used for? Can it be removed? //Peter -- ___ Openembedded-core mailing li

[OE-core] [PATCH V3 0/1] gen-lockedsig-cache: catch os.link error

2017-03-19 Thread brian avery
We do a hard link to speed up sdk creation but if your sstate-cache is across a file system boundary, this tries and fails. This patch catches that error and does a copy instead. -brian The following changes since commit 7e0985bab68547f946163828a16beab7542fca2e: nativesdk-packagegroup-sdk-host

[OE-core] [PATCH V3 1/1] gen-lockedsig-cache: catch os.link error

2017-03-19 Thread brian avery
We do a hard link to speed up sdk creation but if your sstate-cache is across a file system boundary, this tries and fails. This patch catches that error and does a copy instead. Signed-off-by: brian avery --- scripts/gen-lockedsig-cache | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-)

Re: [OE-core] [PATCH 0/1] gen-lockedsig-cache: catch os.link error V2

2017-03-19 Thread Brian Avery
Thanks! resubmitted as [PATCH V3 x/y] . -b an intel employee On Fri, Mar 17, 2017 at 2:32 PM, Peter Kjellerstedt < peter.kjellerst...@axis.com> wrote: > > -Original Message- > > From: openembedded-core-boun...@lists.openembedded.org > > [mailto:openembedded-core-boun...@lists.openembedded

Re: [OE-core] What is the purpose of /usr/lib/.build-id?

2017-03-19 Thread Khem Raj
On Sun, Mar 19, 2017 at 8:47 AM, Peter Kjellerstedt wrote: > I have recently noticed the directory /usr/lib/.build-id in the RPM > packages generated by master of OE-core. It contains hashed links to > the binaries in the package. > > What is it used for? I believe it could be due to switching th

[OE-core] [PATCH 2/2] devtool: tidy up handling of parse failures

2017-03-19 Thread Paul Eggleton
Since the tinfoil2 refactoring, if an error occurred during parsing, we were showing a traceback and not correctly exiting (since we weren't calling shutdown()). Fix both of these issues. Signed-off-by: Paul Eggleton --- scripts/lib/devtool/__init__.py | 11 +-- 1 file changed, 9 inserti

[OE-core] [PATCH 1/2] oe-selftest: tinfoil: add tests for recently enabled datastore operations

2017-03-19 Thread Paul Eggleton
A recent patch to bitbake fixes these datastore operations so that they actually affect the server end, so we should test that they work. (For full disclosure, some of these tests would probably pass without those fixes, since the operation would be done on the client side instead - but we are at

[OE-core] [PATCH 0/2] OE-Core fixes relating to tinfoil2 refactoring

2017-03-19 Thread Paul Eggleton
Add some tests and fix parse failure handling in devtool after the tinfoil2 refactoring. NOTE: the bitbake patches I just sent should be applied first in order to ensure the oe-selftest tests that the first patch introduces to pass. The following changes since commit f43290f6e302dbacf5581d1fe1c6