[OE-core] [PATCH V2] libcomps: Fix/optimize building with clang

Signed-off-by: Khem Raj --- ...-Make-__comps_objmrtree_all-static-inline.patch | 35 ++ meta/recipes-devtools/libcomps/libcomps_git.bb | 1 + 2 files changed, 36 insertions(+) create mode 100644

[OE-core] [PATCH] libcomps: Fix/optimize building with clang

Signed-off-by: Khem Raj --- ...-Make-__comps_objmrtree_all-static-inline.patch | 35 ++ meta/recipes-devtools/libcomps/libcomps_git.bb | 1 + 2 files changed, 36 insertions(+) create mode 100644

Re: [OE-core] [PATCH 0/5] Fix some issues of kernel/image recipes

On Tue, Mar 21, 2017 at 01:54:58AM +0100, liu.min...@gmail.com wrote: > From: Peter Liu What version of the patchset is this? > The changes include: > kernel.bbclass: fix some incorrect inter-task dependencies > kernel.bbclass: introduce

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

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

[OE-core] [PATCH 1/5] kernel.bbclass: fix some incorrect inter-task dependencies

From: Ming Liu - Move the addtask statment that kernel_link_images needs run after do_compile from linux-yocto.inc to kernel.bbclass. Or else the recipes that inheriting kernel.bbclass might run into implicit dependency issues. - Fix a typo, "addtask

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

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

[OE-core] [PATCH 3/5] kernel.bbclass: handle kernel-vmlinux in KERNEL_IMAGETYPES

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,

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

From: Peter Liu The changes include: kernel.bbclass: fix some incorrect inter-task dependencies kernel.bbclass: introduce INITRAMFS_IMAGE_NAME kernel.bbclass: handle kernel-vmlinux in KERNEL_IMAGETYPES image.bbclass: remove initramfs bundle related code

[OE-core] [PATCH 2/5] kernel.bbclass: introduce INITRAMFS_IMAGE_NAME

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 ---

[OE-core] [PATCH] libxslt: Add PACKAGECONFIG support

Some options like python bindings, debug support, crypto are hardcoded inside the recipe. Change that to make those option configurable using PACKAGECONFIG. Signed-off-by: Vedang Patel --- meta/recipes-support/libxslt/libxslt_1.1.29.bb | 9 +++-- 1 file changed, 7

[OE-core] [PATCH 6/7] scripts/yocto-compat-layer.py: Add option to disable layer autodiscovery

Sometimes there is a need to only analyze the layer specified by the command line, the new option -n will disable autodiscovery of layers and only will try to test specified layers. Signed-off-by: Aníbal Limón --- scripts/lib/compatlayer/__init__.py | 17

[OE-core] [PATCH 7/7] scripts/yocto-compat-layer.py: Handle layer dependencies when test

If some layer depends on other tries to find layer dependency, if the layer dependency isn't found avoid to test the layer and notice the user. Signed-off-by: Aníbal Limón --- scripts/lib/compatlayer/__init__.py | 29 -

[OE-core] [PATCH 5/7] scripts/lib/compatlayer: Remove require of meta- in layer dir name

The layers isn't required to have a dirctory name start with meta- so remove the validation. Signed-off-by: Aníbal Limón --- scripts/lib/compatlayer/__init__.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scripts/lib/compatlayer/__init__.py

[OE-core] [PATCH 3/7] scripts/yocto-compat-layer.py: Make output log argument optional

Only create a log file when --output-log option is specified, since logger is dumping to stdout by default is better to let the user decide if a log needs to be created. [YOCTO #11160] Signed-off-by: Aníbal Limón --- scripts/yocto-compat-layer.py | 17

[OE-core] [PATCH 2/7] scripts/yocto-compat-layer.py: Dump log to stdout instead of stderr

The common unix tools uses stdout as standard for log output, by default python logging uses stderr if not stream is specified. [YOCTO #11160] Signed-off-by: Aníbal Limón --- scripts/yocto-compat-layer.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

[OE-core] [PATCH 4/7] scripts/compatlayer: Add exclude of meta-world-pkgdata on get_signatures

The meta-world-pkgdata recipe can be modified when a layer is added may be can add recipes to world target, so exclude by default. [YOCTO #11162] Signed-off-by: Aníbal Limón --- scripts/lib/compatlayer/__init__.py | 14 ++ 1 file changed, 14

[OE-core] [PATCH 1/7] scriptutils: Add support for specify stream on logger_create

It is a good idea to let the script to choose what stream wants to dump the logging output. [YOCTO #11160] Signed-off-by: Aníbal Limón --- scripts/lib/scriptutils.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/scripts/lib/scriptutils.py

[OE-core] [PATCH 2/3] scripts/yocto-compat-layer.py: Add option to disable layer autodiscovery

Sometimes there is a need to only analyze the layer specified by the command line, the new option -n will disable autodiscovery of layers and only will try to test specified layers. Signed-off-by: Aníbal Limón --- scripts/lib/compatlayer/__init__.py | 17

[OE-core] [PATCH 3/3] scripts/yocto-compat-layer.py: Handle layer dependencies when test

If some layer depends on other tries to find layer dependency, if the layer dependency isn't found avoid to test the layer and notice the user. Signed-off-by: Aníbal Limón --- scripts/lib/compatlayer/__init__.py | 29 -

[OE-core] [PATCH 1/3] scripts/lib/compatlayer: Remove require of meta- in layer dir name

The layers isn't required to have a dirctory name start with meta- so remove the validation. Signed-off-by: Aníbal Limón --- scripts/lib/compatlayer/__init__.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scripts/lib/compatlayer/__init__.py

[OE-core] [PATCH] scripts/compatlayer: Add exclude of meta-world-pkgdata on get_signatures

The meta-world-pkgdata recipe can be modified when a layer is added may be can add recipes to world target, so exclude by default. [YOCTO #11162] Signed-off-by: Aníbal Limón --- scripts/lib/compatlayer/__init__.py | 14 ++ 1 file changed, 14

[OE-core] ovmf fails to build with musl (was: Re: [PATCH 5/6] musl: Update to latest)

On Mon, 2017-03-20 at 07:43 -0700, Khem Raj wrote: > On Mon, Mar 20, 2017 at 1:32 AM, Jussi Kukkonen > wrote: > > > > On 15 March 2017 at 01:35, Khem Raj wrote: > >> > >> Rich Felker (11): > >> fix ld-behavior-dependent crash in ppc64 ldso

[OE-core] [PATCH 2/3] scripts/yocto-compat-layer.py: Dump log to stdout instead of stderr

The common unix tools uses stdout as standard for log output, by default python logging uses stderr if not stream is specified. [YOCTO #11160] Signed-off-by: Aníbal Limón --- scripts/yocto-compat-layer.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

[OE-core] [PATCH 3/3] scripts/yocto-compat-layer.py: Make output log argument optional

Only create a log file when --output-log option is specified, since logger is dumping to stdout by default is better to let the user decide if a log needs to be created. [YOCTO #11160] Signed-off-by: Aníbal Limón --- scripts/yocto-compat-layer.py | 17

[OE-core] [PATCH 1/3] scriptutils: Add support for specify stream on logger_create

It is a good idea to let the script to choose what stream wants to dump the logging output. [YOCTO #11160] Signed-off-by: Aníbal Limón --- scripts/lib/scriptutils.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/scripts/lib/scriptutils.py

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

On Mon, Mar 20, 2017 at 4:45 PM, Peter Liu wrote: > Hi, Andrea: > > > Thanks for your testing. > > > I think you are absolutely right, actually I think you had found a fix for a > potential defect, do_kernel_link_images needs to run after do_compile, and >

[OE-core] [morty][PATCH] sstate.bbclass: update .siginfo atime

From: Ed Bartosh .siginfo files are not being accessed from local or NFS-mounted sstate mirrors when sstate package is installed, so their atime is not updated. If sstate mirror is cleaned based on access time, they get deleted, even though they are still being used.

[OE-core] [PATCH 2/2] oeqa/selftest: remove test_sanity_unsafe_binary_references

This test was attempting to exercise a broken test, for some reason this broke with patches under review but investigation revealed that the test itself is broken. The test has been removed, so there's no need to test it. Signed-off-by: Ross Burton ---

[OE-core] [PATCH 2/4] openssl: Fix build with clang

Signed-off-by: Khem Raj --- ...build-with-clang-using-external-assembler.patch | 49 ++ .../recipes-connectivity/openssl/openssl_1.0.2k.bb | 5 ++- 2 files changed, 52 insertions(+), 2 deletions(-) create mode 100644

[OE-core] [PATCH 4/4] go-native: Install bootstrap binaries with 1.4 suffix

Currently, bin/go and bin/gofmt collide between go-native and go-bootstrap-native packages, these are scripts anyway which call the go compiler proper from right install, in this case create go1.4 and gofmt1.4 names for these scripts to avoid namespace collision Signed-off-by: Khem Raj

[OE-core] [PATCH 3/4] acpitests: Point Makefile CC to use OE synthesized CC

Default CC is same as used here, there is no need to duplicate it, as a plus it helps in compiling acpitests with non-gcc cross compilers Signed-off-by: Khem Raj --- meta/recipes-extended/acpica/acpitests_20140828.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[OE-core] [PATCH 1/2] insane: remove broken unsafe-references-in-binaries test

This test aims to detect binaries in /bin which link to libraries in /usr/lib, for the case where the user has /usr on a separate filesystem to /. However it doesn't scan both image/ and the sysroot, so if a binary in /bin links to a library in /usr/lib that was built by the same recipe then it

Re: [OE-core] go-bootstrap / go-native conflict during do_rootfs

On Mon, Mar 20, 2017 at 8:29 AM, Khem Raj wrote: > On Mon, Mar 20, 2017 at 8:17 AM, Richard Purdie > wrote: >> On Mon, 2017-03-20 at 07:49 -0700, Khem Raj wrote: >>> On Mon, Mar 20, 2017 at 6:47 AM, Kristian Amlie >>>

[OE-core] [PATCH 1/4] ltp: Fix __sighandler_t for mips

mips definition of kernel_sigaction was added later and the patch did not apply to mips part which ended in ltp failing to compile on mips parts In file included from rt_sigaction01.c:42:0: ../../../../include/lapi/rt_sigaction.h:39:2: error: unknown type name '__sighandler_t' __sighandler_t

[OE-core] [PATCH 0/4] misc fixes

Fix install collisions between go-native and go-bootstrap-native Fix ltp for musl Other fixes are found by clang but are generic The following changes since commit b5a595a4be09756b88e91f3353e3b221b165ab44: binutils: disable gold on mingw (2017-03-20 15:17:48 +) are available in the git

Re: [OE-core] [PATCH 5/5] file: 5.29 -> 5.30

> -Original Message- > From: Stefano Babic [mailto:sba...@denx.de] > Sent: Monday, March 20, 2017 5:06 PM > To: Manjukumar Harthikote Matha; Robert Yang; Stefano Babic; openembedded- > c...@lists.openembedded.org > Subject: Re: [OE-core] [PATCH 5/5] file: 5.29 -> 5.30 > > On 20/03/2017

Re: [OE-core] go-bootstrap / go-native conflict during do_rootfs

On Mon, Mar 20, 2017 at 8:17 AM, Richard Purdie wrote: > On Mon, 2017-03-20 at 07:49 -0700, Khem Raj wrote: >> On Mon, Mar 20, 2017 at 6:47 AM, Kristian Amlie >> wrote: >> > >> > -- >> >

[OE-core] [PATCH] gpgme: Avoid requiring a host C++ compiler with C++11 support

Building the C++ bindings for native requires a host C++ compiler with C++11 support. Since these bindings are currently not needed, we can disable them and thus avoid increasing the requirement for the host C++ compiler. Signed-off-by: Peter Kjellerstedt ---

Re: [OE-core] go-bootstrap / go-native conflict during do_rootfs

On Mon, 2017-03-20 at 07:49 -0700, Khem Raj wrote: > On Mon, Mar 20, 2017 at 6:47 AM, Kristian Amlie > wrote: > >  > > -- > > > > Additionally, in the logs I found these two snippets: > > > >

[OE-core] [PATCH] package.bbclass: Add PRIVATE_LIBS to list of package specific variables

Changes to PRIVATE_LIBS should change the sstate checksum. To make that happen, it needs to be listed in the list of package specific variables, therefore add it. Signed-off-by: Peter Kjellerstedt --- meta/classes/package.bbclass | 2 +- 1 file changed, 1

Re: [OE-core] [morty][PATCH] file: update SRCREV for 5.28 to fix fetch fail on missing commit

On Mon, Mar 20, 2017 at 02:55:41PM +, Richard Purdie wrote: > On Mon, 2017-03-20 at 10:06 -0400, Denys Dmytriyenko wrote: > > Ping. > > > > This is getting quickly escalated by my teams and customers. Can we > > merge this  > > to morty right away? Thanks! > > > > There's another patch for

Re: [OE-core] [morty][PATCH] file: update SRCREV for 5.28 to fix fetch fail on missing commit

On Mon, 2017-03-20 at 10:06 -0400, Denys Dmytriyenko wrote: > Ping. > > This is getting quickly escalated by my teams and customers. Can we > merge this  > to morty right away? Thanks! > > There's another patch for krogoth, that's not as urgent yet, but > probably will  > be soon too... > >

Re: [OE-core] [PATCH] binutils: disable gold on mingw

On Mon, Mar 20, 2017 at 5:20 AM, Ross Burton wrote: > oe-core 759eed (binutils: Enable threading when gold is enabled and is not > default linker) causes linking in mingw SDKs to fail: > >

Re: [OE-core] go-bootstrap / go-native conflict during do_rootfs

On Mon, Mar 20, 2017 at 6:47 AM, Kristian Amlie wrote: > First of all, kudos to Khem Raj for the hard work on the go compiler > support, this will help a lot! > > However, I have one problem when my project reaches do_rootfs: > >

[OE-core] Yocto Project Status WW12’17

Current Dev Position: YP 2.3 M4 Next Deadline: YP 2.3 M4 Cutoff is April 10, 2017 *** FEATURE FREEZE for 2.3 is now in effect. *** SWAT team rotation: Alejandro -> Jussi on Mar. 17, 2017. SWAT team rotation: Jussi-> Stephano on Mar. 24, 2017.

Re: [OE-core] [PATCH 5/6] musl: Update to latest

On Mon, Mar 20, 2017 at 1:32 AM, Jussi Kukkonen wrote: > > On 15 March 2017 at 01:35, Khem Raj wrote: >> >> Rich Felker (11): >> fix ld-behavior-dependent crash in ppc64 ldso startup >> rework ldso handling of global symbol table for

Re: [OE-core] [morty][PATCH] file: update SRCREV for 5.28 to fix fetch fail on missing commit

On Mon, Mar 20, 2017 at 02:08:58PM +, Burton, Ross wrote: > On 20 March 2017 at 14:06, Denys Dmytriyenko wrote: > > > This is getting quickly escalated by my teams and customers. Can we merge > > this > > to morty right away? Thanks! > > > > Morty and Krogoth have been

Re: [OE-core] [morty][PATCH] file: update SRCREV for 5.28 to fix fetch fail on missing commit

Ping. This is getting quickly escalated by my teams and customers. Can we merge this to morty right away? Thanks! There's another patch for krogoth, that's not as urgent yet, but probably will be soon too... BTW, I believe Armin was traveling last week, not sure if he's back yet. -- Denys

Re: [OE-core] [morty][PATCH] file: update SRCREV for 5.28 to fix fetch fail on missing commit

On 20 March 2017 at 14:06, Denys Dmytriyenko wrote: > This is getting quickly escalated by my teams and customers. Can we merge > this > to morty right away? Thanks! > Morty and Krogoth have been patched now. Ross -- ___

Re: [OE-core] Status of usrmerge merger

On 18 March 2017 at 22:25, Anton Gerasimov wrote: > what is the current status of the usrmerge patch [1]? It was submitted > quite a long time ago and I can't find any discussion about it. If there > is something I can do to help with testing/tweaking to get it

[OE-core] go-bootstrap / go-native conflict during do_rootfs

First of all, kudos to Khem Raj for the hard work on the go compiler support, this will help a lot! However, I have one problem when my project reaches do_rootfs: -- ERROR: core-image-full-cmdline-1.0-r0 do_rootfs: Error executing a python function in

Re: [OE-core] Error after updating Poky

On 2017-03-20 13:58, Burton, Ross wrote: On 20 March 2017 at 12:50, Gary Thomas > wrote: Thanks, that did fix it. I see that those recipe-sysroot* trees are kept around (I don't run rm_work) For one of my builds which has ~475 packages

Re: [OE-core] [PATCH 3/3] meta: images: Add fsck to avoid corrupt EXT file systems

On 20 March 2017 at 13:01, Daniel Schultz wrote: > Doesn't mkfs returns an exit code if it wasn't successful? >> >> Yes, but it seems like mkfs can't handle everything. > > "The htree (hash tree) indexes directory entries by hash to speed up > random directory accesses.

Re: [OE-core] [PATCH 3/3] meta: images: Add fsck to avoid corrupt EXT file systems

Am 20.03.2017 um 13:26 schrieb Burton, Ross: On 20 March 2017 at 12:18, Daniel Schultz > wrote: Since there are no checks if a EXT file system was successfully created, this should add to prevent possible system failures. Doesn't mkfs

Re: [OE-core] Error after updating Poky

On 20 March 2017 at 12:50, Gary Thomas wrote: > Thanks, that did fix it. > > I see that those recipe-sysroot* trees are kept around (I don't run > rm_work) > For one of my builds which has ~475 packages in tmp/work, they amount to > 7GB > Is there any way to prune them? >

Re: [OE-core] Error after updating Poky

On 2017-03-20 13:21, Patrick Ohly wrote: On Mon, 2017-03-20 at 13:12 +0100, Gary Thomas wrote: I just updated to the latest Poky master (7e0985bab68547) which replaced rpm-5.4 with rpm-4.13.90 (git). My builds in an existing tree now fail: |

Re: [OE-core] [PATCH 3/3] meta: images: Add fsck to avoid corrupt EXT file systems

On 20 March 2017 at 12:18, Daniel Schultz wrote: > Since there are no checks if a EXT file system was successfully created, > this should add to prevent possible system failures. > Doesn't mkfs returns an exit code if it wasn't successful? Ross --

[OE-core] [PATCH] image-buildinfo.bbclass: configurable location for build file

In a stateless image, /etc is not a good place for the "build" file. By definining the location with a variable it becomes possible to have the file created elsewhere on a per-image basis. The default is the same as before. Signed-off-by: Patrick Ohly ---

Re: [OE-core] [PATCH 4/6] binutils: Enable threading when gold is enabled and is not default linker

On 14 March 2017 at 23:35, Khem Raj wrote: > Currently we enable threaded linking feature of gold linker only > when its used as default ld. There is no need to restrict it when > its not default linker either. As long as gold is enabled, which > is the case here, we should

Re: [OE-core] Error after updating Poky

On Mon, 2017-03-20 at 13:12 +0100, Gary Thomas wrote: > I just updated to the latest Poky master (7e0985bab68547) which > replaced rpm-5.4 with rpm-4.13.90 (git). My builds in an existing > tree now fail: > > | >

[OE-core] [PATCH] binutils: disable gold on mingw

oe-core 759eed (binutils: Enable threading when gold is enabled and is not default linker) causes linking in mingw SDKs to fail: .../work/i686-nativesdk-mingw32-pokysdk-mingw32/binutils-cross-canadian-x86-64/2.28-r0

[OE-core] [PATCH 3/3] meta: images: Add fsck to avoid corrupt EXT file systems

This patch avoids the creation of a corrupt EXT file system. Since there are no checks if a EXT file system was successfully created, this should add to prevent possible system failures. Signed-off-by: Daniel Schultz --- meta/classes/image_types.bbclass | 1 + 1 file

[OE-core] [PATCH 1/3] e2fsprogs: Fix wrong error code after optimization

fsck.ext will return an error code of 1 if a file systems was checked and successfully repaired. Even when an optimization was performed it will return this error code. This patch will change the error code to 0 if only optimizations had changed the file systems. The reason for this patch is a

[OE-core] [PATCH 2/3] wic: partition.py: Add fsck to avoid corrupt EXT file systems

This patch avoids the creation of a corrupt EXT file system. Since there are no checks if a EXT file system was successfully created, this should add to prevent possible system failures. Signed-off-by: Daniel Schultz --- scripts/lib/wic/partition.py | 3 +++ 1 file

[OE-core] Error after updating Poky

I just updated to the latest Poky master (7e0985bab68547) which replaced rpm-5.4 with rpm-4.13.90 (git). My builds in an existing tree now fail: | /build/p7619_2016-02-23/tmp/work/cortexa7hf-neon-amltd-linux-gnueabi/libsolv/0.6.26-r0/recipe-sysroot-native/usr/lib/librpmdb.so: file not

Re: [OE-core] [PATCH 5/5] file: 5.29 -> 5.30

On 20 March 2017 at 13:29, Manjukumar Harthikote Matha < manjukumar.harthikote-ma...@xilinx.com> wrote: > > > > -Original Message- > > From: openembedded-core-boun...@lists.openembedded.org > > [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of > > Robert Yang > >

Re: [OE-core] [PATCH 5/5] file: 5.29 -> 5.30

On 20/03/2017 12:29, Manjukumar Harthikote Matha wrote: > > >> -Original Message- >> From: openembedded-core-boun...@lists.openembedded.org >> [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of >> Robert Yang >> Sent: Monday, March 20, 2017 3:14 PM >> To: Stefano

Re: [OE-core] [PATCH 5/5] file: 5.29 -> 5.30

> -Original Message- > From: openembedded-core-boun...@lists.openembedded.org > [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of > Robert Yang > Sent: Monday, March 20, 2017 3:14 PM > To: Stefano Babic; openembedded-core@lists.openembedded.org > Subject: Re:

[OE-core] what are OE's options for a PPTP server to use instead of poptop?

colleague wants to add a PPTP server to image, and is familiar with poptop which (AFAICT) is not listed in the current "supported" OE recipes. i found a recipe for it: http://cgit.openembedded.org/openembedded/plain/recipes/poptop/poptop_1.3.4.bb but i note that do_install_append() suggests

Re: [OE-core] [PATCH 5/6] musl: Update to latest

On Mon, 2017-03-20 at 10:32 +0200, Jussi Kukkonen wrote: > > On 15 March 2017 at 01:35, Khem Raj wrote: > Rich Felker (11): > fix ld-behavior-dependent crash in ppc64 ldso startup > rework ldso handling of global symbol table for >

Re: [OE-core] [PATCH 4/6] oeqa/targetcontrol.py: modify it to test runqemu

On 03/17/2017 07:54 PM, Richard Purdie wrote: On Thu, 2017-03-16 at 03:13 -0700, Robert Yang wrote: Modify the following files to test runqemu: targetcontrol.py utils/commands.py utils/qemurunner.py We need simulate how "runqemu" works in command line, so when test "runqemu", the

Re: [OE-core] [PATCH 5/5] file: 5.29 -> 5.30

Yes, file's upstream commit ID has changed, Paul has sent a patch for it: http://lists.openembedded.org/pipermail/openembedded-core/2017-March/134261.html // Robert On 03/20/2017 05:14 PM, Stefano Babic wrote: On 22/02/2017 02:44, Robert Yang wrote: Signed-off-by: Robert Yang

Re: [OE-core] [PATCH 5/5] file: 5.29 -> 5.30

On 20 March 2017 at 11:14, Stefano Babic wrote: > > On 22/02/2017 02:44, Robert Yang wrote: > > Signed-off-by: Robert Yang > > --- > > meta/recipes-devtools/file/{file_5.29.bb => file_5.30.bb} | 2 +- > > 1 file changed, 1 insertion(+), 1 deletion(-) >

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

On Sun, Mar 19, 2017 at 2:13 PM, wrote: > 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

Re: [OE-core] [PATCH 5/5] file: 5.29 -> 5.30

On 22/02/2017 02:44, Robert Yang wrote: > Signed-off-by: Robert Yang > --- > meta/recipes-devtools/file/{file_5.29.bb => file_5.30.bb} | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > rename meta/recipes-devtools/file/{file_5.29.bb => file_5.30.bb} (96%) > >

Re: [OE-core] [morty][PATCH] file: update SRCREV for 5.28 to fix fetch fail on missing commit

I hit this issue when doing a build this morning, and filed this bug before seeing your patches: https://bugzilla.yoctoproject.org/show_bug.cgi?id=11190 Cheers, Phil On 18.03.2017 00:24, Denys Dmytriyenko wrote: > From: Paul Gortmaker > > Machines that cloned a

Re: [OE-core] [PATCH 5/6] musl: Update to latest

On 15 March 2017 at 01:35, Khem Raj wrote: > Rich Felker (11): > fix ld-behavior-dependent crash in ppc64 ldso startup > rework ldso handling of global symbol table for consistency > reorder addend handling before symbol lookup in relocation code >