[OE-core] [PATCH] linux-yocto-custom: Update for newer kernel

Update the NAME version tweak example patch for the newer kernel. This moves the example to the 4.2 stable kernel and appends -custom to the VERSION string. Signed-off-by: Saul Wold --- .../recipes-kernel/linux/linux-yocto-custom.bb | 15 +++

Re: [OE-core] [yocto][PATCH 1/1] ptest: user-specified run-ptest script location

On 28.09.2015 18:41, Ray, Ian (GE Healthcare) wrote: Hi Ross On 28 September 2015, Ross Burton wrote: On 28 September 2015 at 15:46, Ray, Ian (GE Healthcare) wrote: The main benefit is for packages that are run-ptest /aware/, in which case the recipe can be simplified.

[OE-core] [PATCH 0/1] cross-canadian.bbclass: armeb is also gnueabi

This only shows up if you're trying to build for an armeb target, symptom of failure is gcc failing because it can't find a supported target with the -gnu suffix instead of -gnueabi. Signed-off-by: Peter Seebach The following changes since commit

[OE-core] [PATCH 1/1] cross-canadian.bbclass: big-endian ARM is also gnueabi.

If building for a BE8 ARM target, arch is "armeb" rather than "arm", but ABI should still be "gnueabi". Otherwise gcc won't build. Signed-off-by: Peter Seebach --- meta/classes/cross-canadian.bbclass | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[OE-core] [PATCH 1/1 v2] qemurunner: Sanitize output from qemu and qemu pid

From: Mariano Lopez Currently the output from qemu could contain control or Unicode characters; having such characters in the log will cause an internal server error when sending the report to error reporting web. Control characters can be found in the command line

Re: [OE-core] [PATCH v3 03/10] oe-selftest: devtool: add method for checking workspace dir

On 09/24/2015 06:53 AM, Markus Lehtonen wrote: In order to remove some code duplication. Signed-off-by: Markus Lehtonen --- meta/lib/oeqa/selftest/devtool.py | 63 +++ 1 file changed, 24 insertions(+), 39 deletions(-)

Re: [OE-core] [PATCH] oeqa/testimage: Add ability to run single test from suite.

The thing is by the time tc.testlist is iterated, “oeqa.runtime.” is appended before every parameter in TEST_SUITES so I try to find out if it’s a filename.class.test format and truncate it as you said. Thanks for the input. Will do the changes. From: Burton, Ross

Re: [OE-core] [yocto][PATCH 1/1] ptest: user-specified run-ptest script location

Hi Tudor On 28 September 2015, Tudor Florea wrote: > On 9/21/2015 10:11, Ian Ray wrote: >> Provides a new variable, PTEST_RUN_SCRIPT_PATH, which points to a >> directory where the run-ptest script is located. This location >> defaults to the work directory but may be overridden within a recipe

Re: [OE-core] [yocto][PATCH 1/1] ptest: user-specified run-ptest script location

Hi Ross > On 28 September 2015, Ross Burton wrote: >> On 28 September 2015 at 15:46, Ray, Ian (GE Healthcare) >> wrote: >>The main benefit is for packages that are run-ptest /aware/, in which case >> the recipe can be simplified. > Surely if an upstream is under your control

[OE-core] [PATCH] oeqa/runexported: Fix a problem with ssh_target_log existing in folder.

When copying the exported tests to a remote machine ssh_target_log can be transformed from softlink to file which will throw an error when trying to run again. Signed-off-by: Lucian Musat --- meta/lib/oeqa/runexported.py | 4 ++-- 1 file changed, 2 insertions(+), 2

Re: [OE-core] [PATCH] oeqa/testimage: Add ability to run single test from suite.

On 28 September 2015 at 12:47, Lucian Musat wrote: > @@ -172,6 +176,7 @@ def exportTests(d,tc): > +from re import search as re_search > Just import re and then do re.search - it's the same number of characters when calling and it's obvious what you're calling then.

Re: [OE-core] [PATCH 1/1] qemurunner: Sanitize output from qemu and qemu pid

On 25 September 2015 at 07:33, wrote: > def log(self, msg): > if self.logfile: > +# It is needed to sanitize the data received from qemu > +# because is possible to have control characters or Unicode > +msg =

[OE-core] [PATCHv2] oeqa/testimage: Add ability to run single test from suite.

Just like we have in oe-selftest, you can add .. in TEST_SUITES in order to run just that test Signed-off-by: Lucian Musat --- meta/classes/testimage.bbclass | 7 +++ 1 file changed, 7 insertions(+) diff --git a/meta/classes/testimage.bbclass

Re: [OE-core] [yocto][PATCH 1/1] ptest: user-specified run-ptest script location

On 28 September 2015 at 15:46, Ray, Ian (GE Healthcare) wrote: > The main benefit is for packages that are run-ptest /aware/, in which case > the recipe can be simplified. > Surely if an upstream is under your control and is ptest-aware, it can also install run-ptest into the

[OE-core] [PATCH] recipes-extended: remove duplicate recipe and .wks

Removed wic-image-minimal.bb and wic-image-minimal.wks as they're also present in meta-selftest/recipes-test/images/ Signed-off-by: Ed Bartosh --- meta/recipes-extended/images/wic-image-minimal.bb | 14 --

Re: [OE-core] [PATCH v2] opkg: create opkg.lock in /run instead of /var/run

* Jonathan Liu [150926 01:34]: > This avoids a "Could not unlink" warning when extracting a /var/run > symbolic link pointing to /run from the base-files package as it is > unable to unlink the /var/run directory when it contains opkg.lock. > This also fixes an issue where

Re: [OE-core] [PATCH 2/7] gstreamer1.0-plugins-base: upgrade to version 1.6.0

Am 2015-09-28 um 08:47 schrieb Khem Raj: On Sun, Sep 27, 2015 at 11:44 PM, Carlos Rafael Giani wrote: The other patches in the list above, however, need to be reworked to apply against 1.6. 0001-basetextoverlay-make-memory-copy-when-video-buffer-s.patch has been

[OE-core] [PATCH 1/1] toolchain-shar-relocate.sh: make it faster

Make the extrating faster by: * Merge the two heavy t"for .. find" loops into one * Move the commands out of for loop rather than inside, this can reduce the forking amount. As a result, when install: * buildtools-nativesdk-standalone: 14s -> 7s (50% saved) *

[OE-core] [yocto 2.1] [PATCH 0/1] toolchain-shar-relocate.sh: make it faster

The following changes since commit d5cf21179d9f8d3c053316b0864d72fc609f5423: gdk-pixbuf: Avoid rebuild failures (2015-09-24 17:53:25 +0100) are available in the git repository at: git://git.openembedded.org/openembedded-core-contrib rbt/sdk_time

Re: [OE-core] [PATCH] opkg: create opkg.lock in /run instead of /var/run

* Jonathan Liu [150925 17:07]: > On 21/09/2015 10:16 PM, Anders Darander wrote: > >* Jonathan Liu [150921 13:08]: > >>This avoids a "Could not unlink" warning when extracting a /var/run > >>symbolic link pointing to /run from the base-files package as it is

Re: [OE-core] [PATCH 2/7] gstreamer1.0-plugins-base: upgrade to version 1.6.0

Am 2015-09-28 um 03:07 schrieb Khem Raj: On Sun, Sep 27, 2015 at 2:48 PM, Carlos Rafael Giani wrote: A number of patches had to be deleted in order for the recipe to work. Patches which cannot be applied cleanly to 1.6.0 and are nontrivial to fix: *

Re: [OE-core] [PATCH 2/7] gstreamer1.0-plugins-base: upgrade to version 1.6.0

On Sun, Sep 27, 2015 at 11:44 PM, Carlos Rafael Giani wrote: > The other patches in the list above, however, need to be reworked to apply > against 1.6. > 0001-basetextoverlay-make-memory-copy-when-video-buffer-s.patch has been > rejected by upstream, >

Re: [OE-core] [PATCH 2/7] gstreamer1.0-plugins-base: upgrade to version 1.6.0

On Sun, Sep 27, 2015 at 11:53 PM, Carlos Rafael Giani wrote: > Am 2015-09-28 um 08:47 schrieb Khem Raj: >> >> On Sun, Sep 27, 2015 at 11:44 PM, Carlos Rafael Giani >> wrote: >>> >>> The other patches in the list above, however, need to be

Re: [OE-core] [PATCH 1/1] toolchain-shar-relocate.sh: make it faster

On 09/28/2015 03:09 PM, Robert Yang wrote: Make the extrating faster by: * Merge the two heavy t"for .. find" loops into one Sorry, a typo, should be no "t", updated in the repo. // Robert * Move the commands out of for loop rather than inside, this can reduce the forking amount. As a

[OE-core] [oe][meta-oe][PATCH] vim: Compile and provide xxd in package vim-xxd

Signed-off-by: Ioan-Adrian Ratiu --- meta-oe/recipes-support/vim/vim_7.4.481.bb | 10 +- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/meta-oe/recipes-support/vim/vim_7.4.481.bb b/meta-oe/recipes-support/vim/vim_7.4.481.bb index 2ece53b..fcd036b

[OE-core] [PATCH] oeqa/testimage: Add ability to run single test from suite.

Just like we have in oe-selftest, you can add .. in TEST_SUITES in order to run just that test. Signed-off-by: Lucian Musat --- meta/classes/testimage.bbclass | 7 +++ 1 file changed, 7 insertions(+) diff --git a/meta/classes/testimage.bbclass

Re: [OE-core] [PATCH 1/1] python-async: inherit setuptools

On 28 September 2015 at 10:20, Robert Yang wrote: > -inherit distutils > +inherit distutils setuptools > setuptools inherits distutils, so you can replace instead of adding. Ross -- ___ Openembedded-core mailing list

Re: [OE-core] [PATCH 1/7] gstreamer1.0: upgrade to version 1.6.0

On 27 September 2015 at 22:48, Carlos Rafael Giani wrote: > Removed patches which either were backports or accepted and integrated > > Signed-off-by: Carlos Rafael Giani > We're feature frozen so I'll add these to my "for after the freeze"

[OE-core] [PATCH] classes/meta: Add DISTRO_FEATURES check for gtk+/gtk3+

If you currently do a DISTRO_FEATURES_remove = "x11" with OE-Core, you see failures due to dependency problems. The work in resolving this was partially completed a while back. This adds in the markup mainly for gtk/gtk3+ recipes and means "bitbake world" will work successfully. Rather than code

Re: [OE-core] [PATCHv2 1/2] Empty image: core-image-empty recipe

Hi Alex, On Thursday 24 September 2015 10:23:15 Alex Franco wrote: > Added core-image-empty recipe in meta-selftest/recipes-test/images > > [YOCTO #7664] > > Signed-off-by: Alex Franco > --- > meta-selftest/recipes-test/images/core-image-empty.bb | 7 +++

[OE-core] [PATCH 0/1] python-async: inherit setuptools

The following changes since commit d5cf21179d9f8d3c053316b0864d72fc609f5423: gdk-pixbuf: Avoid rebuild failures (2015-09-24 17:53:25 +0100) are available in the git repository at: git://git.openembedded.org/openembedded-core-contrib rbt/python-async

[OE-core] [PATCH 1/1] python-async: inherit setuptools

Fixed when bitbake nativesdk-python-async: DEBUG: Executing shell function do_compile Traceback (most recent call last): File "setup.py", line 2, in from setuptools import setup ImportError: No module named setuptools Signed-off-by: Robert Yang ---

[OE-core] [PATCH] populate_sdk_base: Simplify postprocess commands

When looking at and trying to build a slightly customised SDK, I realised the code could be simplified and written in a way which was more customisable. This patch moves various function calls into the SDK_POSTPROCESS_COMMAND which was intended for this kind of use. Signed-off-by: Richard Purdie

[OE-core] [PATCH] runqemu-internal: Make sure two serial ports always exist

Since inittab for qemu images now always tries to start getty on a second serial device, make sure that device exists. Otherwise the following message will be spammed: INIT: Id "S1" respawning too fast: disabled for 5 minutes [YOCTO #8374] Signed-off-by: Randy Witt

Re: [OE-core] [PATCH 1/1] qemurunner: Sanitize output from qemu and qemu pid

On 09/28/2015 09:42 AM, Burton, Ross wrote: On 25 September 2015 at 07:33, > wrote: def log(self, msg): if self.logfile: +# It is needed to sanitize the data received from qemu +

[OE-core] [PATCH 1/1] oetest: Change logic of a failed test

From: Mariano Lopez Currently the logic to check if a test failed was to check for an exception in the thread, but some decorators used in the syslog runtime test would generate and handle exceptions; this will mess with the current check logic and will dump the

Re: [OE-core] [PATCH v3 10/10] devtool: modify: make bitbake use local files from srctree

Hi Markus, On Thursday 24 September 2015 14:53:07 Markus Lehtonen wrote: > This change makes it possible to have local files (non-remote SRC_URI > files, i.e. files that are located in the "recipe space") under the > srctree even if S!=WORKDIR. The files must be placed under the > 'local-files'

Re: [OE-core] [yocto][PATCH 1/1] ptest: user-specified run-ptest script location

Hi Ian On 9/21/2015 10:11, Ian Ray wrote: > Provides a new variable, PTEST_RUN_SCRIPT_PATH, which points to a > directory where the run-ptest script is located. This location > defaults to the work directory but may be overridden within a recipe > if a package ships its own run-ptest script. >