Re: [OE-core] [PATCH 3/3] libepoxy: Upgrade 1.4.2 -> 1.4.3

On Wed, Jul 12, 2017 at 7:11 AM, Khem Raj wrote: > On Tue, Jul 11, 2017 at 9:56 PM, Andrea Galbusera > wrote: > > On Wed, Jul 12, 2017 at 12:38 AM, Khem Raj wrote: > >> > >> On Tue, Jul 11, 2017 at 3:02 PM, Andrea Galbusera

Re: [OE-core] [PATCH 3/3] libepoxy: Upgrade 1.4.2 -> 1.4.3

On Tue, Jul 11, 2017 at 9:56 PM, Andrea Galbusera wrote: > On Wed, Jul 12, 2017 at 12:38 AM, Khem Raj wrote: >> >> On Tue, Jul 11, 2017 at 3:02 PM, Andrea Galbusera >> wrote: >> > >> > >> > Il 11 lug 2017 8:00 PM, "Khem Raj"

[OE-core] [poky][master] [PATCH v5 0/1] initramfs-framework:configuration to boot up live image

From: "Ng, Wei Tee" Hi, This patch is to get initramfs-framework able to boot up live image. A new scriplet named setup-live module has been created to handle the removeable media detection and assign the rootfs.img. This is because the current rootfs module has no

[OE-core] [PATCH 1/1] initramfs-framwork: module to support boot live image

From: "Ng, Wei Tee" setup-live module is a new module being introduced to integrate the functionality of init-live.sh into new scriptlet named setup-live in order to support the live boot image. The udev-extraconf rdepends is being added to perform automounting. It gets to

Re: [OE-core] [PATCH 3/3] libepoxy: Upgrade 1.4.2 -> 1.4.3

On Wed, Jul 12, 2017 at 12:38 AM, Khem Raj wrote: > On Tue, Jul 11, 2017 at 3:02 PM, Andrea Galbusera > wrote: > > > > > > Il 11 lug 2017 8:00 PM, "Khem Raj" ha scritto: > > > > On Tue, Jul 11, 2017 at 1:34 AM, Jussi Kukkonen > >

Re: [OE-core] [PATCH] u-boot: Upgrade to 2017.07 release (WIP)

On Tue, Jul 11, 2017 at 09:09:47PM -0400, Denys Dmytriyenko wrote: > On Mon, Jul 10, 2017 at 03:12:19PM -0400, Tom Rini wrote: > > On Mon, Jul 10, 2017 at 12:08:41PM -0700, Khem Raj wrote: > > > On 7/10/17 12:06 PM, Tom Rini wrote: > > > > On Mon, Jul 10, 2017 at 09:02:39PM +0200, Marek Vasut

[OE-core] [PATCH 1/2] dropbear: reduce local pending patches

Signed-off-by: Dengke Du --- meta/recipes-core/dropbear/dropbear/0003-configure.patch| 13 +++-- .../dropbear/fix-libtomcrypt-libtommath-ordering.patch | 12 +++- 2 files changed, 14 insertions(+), 11 deletions(-) diff --git

[OE-core] [PATCH 0/2] dropbear, chrpath: reduce local pending patches

The following changes since commit 81498aac9560fbeaeb58eaada32ce80e0ea51628: yocto-project-qs: Updated Next Steps list (2017-07-12 00:28:16 +0100) are available in the git repository at: https://github.com/DengkeDu/openembedded-core.git dengke/dropbear-chrpath-reduce-local-pending-patch

[OE-core] [PATCH 2/2] chrpath: reduce local pending patches

Signed-off-by: Dengke Du --- .../chrpath/chrpath/standarddoc.patch | 25 -- 1 file changed, 19 insertions(+), 6 deletions(-) diff --git a/meta/recipes-devtools/chrpath/chrpath/standarddoc.patch

Re: [OE-core] [PATCH v3] slang: add ptest

On 07/12/2017 01:31 AM, Stefan Strogin wrote: Hi Robert, Thanks for the report. Could you say how to reproduce the error? What target architecture, config options, oe-core version, etc do you use? I have tried with openembedded-core 643c81af (master), with MACHINE = "qemux86-64",

[OE-core] [PATCH 1/1] bind: 9.10..3-P3 -> 9.10.5-P3

From: Kai Kang Upgrade bind from 9.10.3-P3 to 9.10.5-P3 * Update md5sum of LIC_FILES_CHKSUM that it update year in file COPYRIGHT * Remvoe mips1-not-support-opcode.diff which has been merged * Remove CVE patches that there are backported from upstream * Use python3 for

[OE-core] [PATCH 0/1] bind: 9.10..3-P3 -> 9.10.5-P3

From: Kai Kang The following changes since commit 81498aac9560fbeaeb58eaada32ce80e0ea51628: yocto-project-qs: Updated Next Steps list (2017-07-12 00:28:16 +0100) are available in the git repository at: git://git.pokylinux.org/poky-contrib kangkai/bind

Re: [OE-core] [PATCH] u-boot: Upgrade to 2017.07 release (WIP)

On Mon, Jul 10, 2017 at 03:12:19PM -0400, Tom Rini wrote: > On Mon, Jul 10, 2017 at 12:08:41PM -0700, Khem Raj wrote: > > On 7/10/17 12:06 PM, Tom Rini wrote: > > > On Mon, Jul 10, 2017 at 09:02:39PM +0200, Marek Vasut wrote: > > >> On 07/10/2017 09:01 PM, Tom Rini wrote: > > >>> On Mon, Jul 10,

Re: [OE-core] [PATCH] dhcp: fix genetle shutdown not work while bind9 compile with --enable-threads

On 2017年07月11日 19:19, Burton, Ross wrote: On 11 July 2017 at 09:13, Hongxu Jia > wrote: +Upstream-Status: Inappropriate [OE specific] This is not OE specific. We enable a specific build combination, and it breaks. Have you

[OE-core] [PATCH] gnu-efi: Upgrade package to 3.0.6 and refresh patches

Version 3.0.6 fixes a failure when using the pxe headers and allows us to drop the explicit fall through patch as it was fixed upstream. Other patches were rebased on top of the new version. Signed-off-by: California Sullivan ---

Re: [OE-core] [PATCH 3/3] libepoxy: Upgrade 1.4.2 -> 1.4.3

On Tue, Jul 11, 2017 at 3:02 PM, Andrea Galbusera wrote: > > > Il 11 lug 2017 8:00 PM, "Khem Raj" ha scritto: > > On Tue, Jul 11, 2017 at 1:34 AM, Jussi Kukkonen > wrote: >> On 11 July 2017 at 11:27, Jussi Kukkonen

Re: [OE-core] [PATCH 3/3] libepoxy: Upgrade 1.4.2 -> 1.4.3

Il 11 lug 2017 8:00 PM, "Khem Raj" ha scritto: On Tue, Jul 11, 2017 at 1:34 AM, Jussi Kukkonen wrote: > On 11 July 2017 at 11:27, Jussi Kukkonen wrote: >> >> On 11 July 2017 at 10:42, Jussi Kukkonen

Re: [OE-core] [PATCH v3] valgrind: Update 3.12.0 -> 3.13.0

On 11 July 2017 at 13:45, Burton, Ross wrote: > I just replicated this and yes your failure is gold specific. > Fixed, patch on the list, and sent it upstream. Ross -- ___ Openembedded-core mailing list

[OE-core] [PATCH] valgrind: fix link failure with gold

Signed-off-by: Ross Burton --- .../valgrind/valgrind/link-gz-tests.patch | 25 ++ meta/recipes-devtools/valgrind/valgrind_3.12.0.bb | 1 + 2 files changed, 26 insertions(+) create mode 100644

[OE-core] [PATCH] dpky.py: Adds testcases for dpkg package manager

From: Libertad Cruz Adds dpkg testcases for testing basic operation functionality for the dpkg package manager. [YOCTO #10063] Signed-off-by: Libertad Cruz --- meta/lib/oeqa/runtime/cases/dpkg.py | 52 + 1

Re: [OE-core] [morty][PATCH 1/1] openssl-native: Compile with -fPIC

Hi Armin, Could we backport this patch to morty? On 07/11/2017 12:39 PM, Khem Raj wrote: On Tue, Jul 11, 2017 at 12:07 PM, Martin Kelly wrote: Hi, Is there any issue with backporting this to morty? It would help me fix a build crash I'm seeing on morty, and I'm currently

[OE-core] ✗ patchtest: failure for oeqa core and oe-selftest threaded enablement

== Series Details == Series: oeqa core and oe-selftest threaded enablement Revision: 1 URL : https://patchwork.openembedded.org/series/7694/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been

[OE-core] [PATCH 26/30] selftest/cases/devtool{, end}: Move update/finish_modify tests to its own module

This devtool tests are set to run at end because made changes into the poky repository causing problems (non deteministic meta data) in other execution threads. Signed-off-by: Aníbal Limón --- meta/lib/oeqa/selftest/cases/devtool.py | 545

[OE-core] [PATCH 28/30] argparse_oe: Add int_positive type

Sometimes only expect positive values from cmdline so it's better to filter at parsing cmdline step instead of validate later. Signed-off-by: Aníbal Limón --- scripts/lib/argparse_oe.py | 7 +++ 1 file changed, 7 insertions(+) diff --git

[OE-core] [PATCH 27/30] seltest/cases/devtool: Build dbus on test_devtool_add_git_local

The dbus-wait recipe has the dependency of dbus, due to now we have build folder per test class the dependency needs to be build before run devtool add because without it the DEPENDS field is unset. The devtool/recipetool uses previously build recipes to figure out the dependencies.

[OE-core] [PATCH 24/30] oeqa/selftest/cases: recipetool enable for threaded runs

- Change to use wrappers from OESelfTestCase. - Move templayer dir creation to RecipetoolBase class because now every class has its own build folder. Signed-off-by: Aníbal Limón --- meta/lib/oeqa/selftest/cases/recipetool.py | 105 +++-- 1

[OE-core] [PATCH 25/30] oeqa/selftest/cases: Move devtool deploy test case to own module

The devtool deploy test case uses runqemu that uses tinfoil so tinfoil requires to run on the main thread. Signed-off-by: Aníbal Limón --- meta/lib/oeqa/selftest/cases/devtool.py| 91 ++--- meta/lib/oeqa/selftest/cases/devtool_deploy.py

[OE-core] [PATCH 23/30] oeqa/selftest/cases: devtool enable threaded runs

- Add new class DevtoolCommon to split devtool suite into other modules. - Change to use wrappers from OESelfTest class (runCmd, bitbake). - When remove workspacedir using bitbake-layers use full path because now has it own builddir. - Add a build of xz-native because some tests needs it to

[OE-core] [PATCH 22/30] oeqa/selftest/cases: eSDK enable threaded runs

- Change some staticmethods to classmethods to be able access wrappers from OESelfTestCase. - Remove unused method update_configuration. Signed-off-by: Aníbal Limón --- meta/lib/oeqa/selftest/cases/eSDK.py | 61 +++- 1 file changed,

[OE-core] [PATCH 21/30] oeqa/selftest/cases: runtime enable threaded runs

- Use wrappers from OESelfTestCase for runCmd, bitbake, etc. - Split into tree modules because runtime_test_export and runtime_test_postinsts uses runqemu/tinfoil and needs to be executed into the main thread. Signed-off-by: Aníbal Limón ---

[OE-core] [PATCH 19/30] oeqa/selftest/cases: imagefeatures enable threaded runs

- Change to use wrapper methos from OESelfTestCase. - Move tests that use runqemu to its own module because it needs tinfoil and run in the main thread. Signed-off-by: Aníbal Limón --- meta/lib/oeqa/selftest/cases/imagefeatures.py | 78 +++---

[OE-core] [PATCH 20/30] oeqa/selftest/cases: runqemu enable thraded runs

- Update to use wrappers {bitbake,get_bb_var} from OESelfTestCase class. - Run into the main thread because it needs tinfoil to run. Signed-off-by: Aníbal Limón --- meta/lib/oeqa/selftest/cases/runqemu.py | 7 +++ 1 file changed, 3 insertions(+), 4 deletions(-)

[OE-core] [PATCH 15/30] oeqa/selftest/cases: Use testlayer_path instead of call get_test_layer()

The testlayer_path is set at init of selftest so isn't need to call every time get_test_layer to get it. Signed-off-by: Aníbal Limón --- meta/lib/oeqa/selftest/cases/_sstatetests_noauto.py | 2 +- meta/lib/oeqa/selftest/cases/devtool.py | 4 ++--

[OE-core] [PATCH 29/30] oeqa/selftest/context: Enable support for threaded runs

Add an option to specify how many threads will be used for execution, default to 1. If the thread_num are greater than 1 the OESelftestContextThreaded will be used, this is due to compatibility reasons. Signed-off-by: Aníbal Limón ---

[OE-core] [PATCH 18/30] oeqa/selftest/cases: tinfoil to run in the main thread

The tinfoil tests needs to initialize bitbake internals and wasn't designed to be in a thread environment causing problems when try for example set signal handlers in a thread different than the main one. To workaround this execute tinfoil tests in the main thread and don't use custom builddir

[OE-core] [PATCH 16/30] oeqa/selftest/cases: Use builddir from class instead of get from environment

Now the build directory is setup by Test class, so the builddir attr points to the actual BUILDDIR instead of get from environment. Signed-off-by: Aníbal Limón --- meta/lib/oeqa/selftest/cases/_sstatetests_noauto.py | 7 +++

[OE-core] [PATCH 17/30] oeqa/selftest/cases: Use wrapper methods from OESelfTestCase class

In order to support threaded runs in oe-selftest cases, there is a need to use wrapper methods that takes into account the current builddir by Test class. Signed-off-by: Aníbal Limón --- .../lib/oeqa/selftest/cases/_sstatetests_noauto.py | 16 ++--

[OE-core] [PATCH 13/30] oeqa/selftest/case: tearDown extra commands print what actually fails

Its better to have the output to see what actually fails in a command that is aim to execute at end of a test case. Signed-off-by: Aníbal Limón --- meta/lib/oeqa/selftest/case.py | 13 + 1 file changed, 9 insertions(+), 4 deletions(-) diff --git

[OE-core] [PATCH 14/30] oeqa/selftest/case: Support bitbake memres mode in per build directory

If BBSERVER is set on the environment the bitbake is set to be used as a memres, so starts an bitbake server per TestClass. Signed-off-by: Aníbal Limón --- meta/lib/oeqa/selftest/case.py | 9 + 1 file changed, 9 insertions(+) diff --git

[OE-core] [PATCH 12/30] oeqa/selftest/case: Creates meta-selftest layer per class

The meta-selftest layer is used by test cases to modify meta data but in a threaded environment two test cases can modify the meta data causing errors because the signatures will change. Signed-off-by: Aníbal Limón --- meta/lib/oeqa/selftest/case.py | 34

[OE-core] [PATCH 30/30] oeqa/selftest/cases: systemd_boot enable threaded runs

Signed-off-by: Aníbal Limón --- .../lib/oeqa/selftest/cases/systemd_boot.py| 26 -- 1 file changed, 14 insertions(+), 12 deletions(-) diff --git a/meta-yocto-bsp/lib/oeqa/selftest/cases/systemd_boot.py

[OE-core] [PATCH 10/30] oeqa/selftest/{case, context}: Add builddir by test class and context

The build directory by Test class will enable to use several instances of bitbake in parallel to enable oe-selftest threaded runs. [YOCTO #11429] Signed-off-by: Aníbal Limón --- meta/lib/oeqa/selftest/case.py| 97 ---

[OE-core] [PATCH 09/30] oeqa/core/tests: Update test_loader threaded to cover main thread usage

Signed-off-by: Aníbal Limón --- meta/lib/oeqa/core/tests/test_loader.py | 17 ++--- 1 file changed, 10 insertions(+), 7 deletions(-) diff --git a/meta/lib/oeqa/core/tests/test_loader.py b/meta/lib/oeqa/core/tests/test_loader.py index

[OE-core] [PATCH 08/30] oeqa/core/threaded: logSummary add skipped tests info

Signed-off-by: Aníbal Limón --- meta/lib/oeqa/core/threaded.py | 11 +++ 1 file changed, 11 insertions(+) diff --git a/meta/lib/oeqa/core/threaded.py b/meta/lib/oeqa/core/threaded.py index a7dc0aed401..022c9ac59a2 100644 --- a/meta/lib/oeqa/core/threaded.py

[OE-core] [PATCH 11/30] oeqa/selftest/case: Add wrappers to utils.commands modules

This methods are wrappers to use builddir by Test class. Signed-off-by: Aníbal Limón --- meta/lib/oeqa/selftest/case.py | 96 +- 1 file changed, 94 insertions(+), 2 deletions(-) diff --git a/meta/lib/oeqa/selftest/case.py

[OE-core] [PATCH 06/30] oeqa/core/threaded: Enable support to use the main thread

Some test cases needs to be executed by the main thread for several resons, this implmentation enables usage of the main thread to execute suites. The rules are if some test case request by test class attr _main_thread it will be executed, if no tests are scheduled to be executed into the main

[OE-core] [PATCH 05/30] oe/copy_buildsystem: check_sstate_task_list also pop BBPATH from env

The BBPATH environment could be set and can make a failure when try to build an extensible sdk because it will look the bitbake.lock file in the original build folder. Example: $ export BBPATH=`pwd` $ bitbake core-image-minimal -c populate_sdk_ext ERROR: bitbake failed: ERROR: Only one copy of

[OE-core] [PATCH 07/30] oeqa/core/threaded: Add support to run into a thread at end of execution

Some test cases aren't allowed to run into a multi-thread environment so add the posibility to run those tests at end of execution. Signed-off-by: Aníbal Limón --- meta/lib/oeqa/core/threaded.py | 102 +++-- 1 file changed, 78

[OE-core] [PATCH 04/30] bb/tinfoil: run_command handle busy status in bitbake server

When tinfoil request a command to bitbake is handled in async manner [1], sometimes is this ends on return a Busy status. This is a workaround a needs to be fixed in proper manner inside bitbake code. For example when running clientComplete and buildFile is on progress, ERROR: Function

[OE-core] [PATCH 03/30] selftest/cases/package: Call parent setUpClass method

Since config paths are now passed in Test context the setUpClass method is expected to be call. Signed-off-by: Aníbal Limón --- meta/lib/oeqa/selftest/cases/package.py | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta/lib/oeqa/selftest/cases/package.py

[OE-core] [PATCH 01/30] oeqa/core/loader: Switch method definition for _make_failed_test

This was a mistake of me to define wrong what methods needs to be defined by certain python version. See rev d8380d098a290510b442a7abd2dd5a50cabf5844. Signed-off-by: Aníbal Limón --- meta/lib/oeqa/core/loader.py | 4 ++-- 1 file changed, 2 insertions(+), 2

[OE-core] [PATCH 02/30] oeqa/selftest/{context, case}: Handle KeyboardInterrupt/SIGINT and SIGTERM

In order to avoid corrupt local.conf and bblayers.conf adds signal handler for SIGTERM and use try/finally (KeyboardIntrrupt) block to restore previously backuped configuration. [YOCTO #11650] Signed-off-by: Aníbal Limón --- meta/lib/oeqa/selftest/case.py| 36

[OE-core] [PATCH 00/30] oeqa core and oe-selftest threaded enablement

This series is to enable oe-selftest threaded runs along some fixes, * Implementation of main/end thread usage in oeqa threaded * Adaptation of oe-selftest cases to be able to run in threaded env, ** Usage of own build directory by Test class. ** Mark the test modules that are enabled to run

Re: [OE-core] [poky][master] [PATCH v4 0/1] initramfs-framework: configuration to boot up live image

On Mon, Jul 10, 2017 at 2:09 PM, wrote: > From: "Ng, Wei Tee" > > Hi, > > This patch is to get initramfs-framework able to boot up live image. > A new scriplet named setup-live module has been created to handle > the removeable media detection and

Re: [OE-core] [morty][PATCH 1/1] openssl-native: Compile with -fPIC

On Tue, Jul 11, 2017 at 12:07 PM, Martin Kelly wrote: > Hi, > > Is there any issue with backporting this to morty? It would help me fix a > build crash I'm seeing on morty, and I'm currently using the backport in a > separate repo with no issue. > there should be no issues. Let

Re: [OE-core] [morty][PATCH 1/1] openssl-native: Compile with -fPIC

Hi, Is there any issue with backporting this to morty? It would help me fix a build crash I'm seeing on morty, and I'm currently using the backport in a separate repo with no issue. On 06/28/2017 11:06 AM, Martin Kelly wrote: On 05/26/2017 12:03 AM, Mirza Krak wrote: From: Khem Raj

Re: [OE-core] [PATCH 3/3] libepoxy: Upgrade 1.4.2 -> 1.4.3

On Tue, Jul 11, 2017 at 1:34 AM, Jussi Kukkonen wrote: > On 11 July 2017 at 11:27, Jussi Kukkonen wrote: >> >> On 11 July 2017 at 10:42, Jussi Kukkonen wrote: Exception: FileExistsError: [Errno 17] File

Re: [OE-core] [PATCH v3] slang: add ptest

Hi Robert, Thanks for the report. Could you say how to reproduce the error? What target architecture, config options, oe-core version, etc do you use? I have tried with openembedded-core 643c81af (master), with MACHINE = "qemux86-64", EXTRA_IMAGE_FEATURES ?= "debug-tweaks ptest-pkgs"

Re: [OE-core] [PATCH v3] valgrind: Update 3.12.0 -> 3.13.0

On 07/11/2017 04:43 AM, Burton, Ross wrote: On 9 July 2017 at 08:35, Soren Brinkmann > wrote: Signed-off-by: Soren Brinkmann > --- v3: - rebased

Re: [OE-core] [PATCH] gettext: Enable generation of libasprintf in gettext 0.19

On Tue, 2017-07-11 at 11:57 -0400, Lev Iserovich wrote: > From: Lev Iserovich > next type, in case you need to send a second (or third..) revision, include the 'v2' label after the '[PATCH ' string the subject line. BTW, this time patchtest did not complain :) Leo

Re: [OE-core] [PATCH v2 2/2] mesa: Upgrade to 17.1.4 release

On Tue, Jul 11, 2017 at 6:00 AM, Jussi Kukkonen wrote: > On 3 July 2017 at 23:02, Otavio Salvador wrote: >> >> This includes following upstream bug fixes: >> >> Bug 77240 - khrplatform.h not installed if EGL is disabled > > > Saying this here as

Re: [OE-core] [PATCH 0/3] pkgconf: consider pkgconf as a replacement for pkg-config

On 11 July 2017 at 17:17, Khem Raj wrote: > Is this going to be the case permanently? > I would suggest to make pkgconf default and dump pkgconfig recipes at same > time > Or do we plan to wait for one release > For testing this is good, if it merges I think we should dump

Re: [OE-core] ✗ patchtest: failure for gettext: Enable generation of libasprintf in gettext 0.19

On 07/11/2017 11:35 AM, Denys Dmytriyenko wrote: Your patch is simply corrupted - please use git to send it, not a regular MUA. Thank you, resending with git worked. Lev -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org

Re: [OE-core] [PATCH 0/3] pkgconf: consider pkgconf as a replacement for pkg-config

On Tue, Jul 11, 2017 at 5:58 AM Maxin B. John wrote: > pkgconf is a better replacement for pkg-config. Fedora 26 replaces the > system pkg-config implementation with pkgconf because it "provides better > support for handling .pc files and a stable library ABI/API for

[OE-core] [PATCH] gettext: Enable generation of libasprintf in gettext 0.19

From: Lev Iserovich Libasprintf was included in gettext 0.16 recipe, but omitted for some reason in 0.19. This turns it back on. Signed-off-by: Lev Iserovich --- meta/recipes-core/gettext/gettext_0.19.8.1.bb | 3 +-- 1 file

Re: [OE-core] ✗ patchtest: failure for gettext: Enable generation of libasprintf in gettext 0.19

On Tue, 2017-07-11 at 11:35 -0400, Denys Dmytriyenko wrote: > Your patch is simply corrupted - please use git to send it, not a regular MUA. Lev, I just tried locally and patch can not be merged on top of master's HEAD. One easy way to try is using patchwork's git plugin and from the command

[OE-core] [PATCH] gcc-7.1: Update the libsanitize stack_t patch to upstreamed version

Signed-off-by: Khem Raj --- ...r-Use-stack_t-instead-of-struct-sigaltsta.patch | 135 + 1 file changed, 28 insertions(+), 107 deletions(-) diff --git a/meta/recipes-devtools/gcc/gcc-7.1/0049-libsanitizer-Use-stack_t-instead-of-struct-sigaltsta.patch

Re: [OE-core] ✗ patchtest: failure for gettext: Enable generation of libasprintf in gettext 0.19

Your patch is simply corrupted - please use git to send it, not a regular MUA. On Tue, Jul 11, 2017 at 11:10:11AM -0400, Lev Iserovich wrote: > Can anyone help me with undestanding this - I'm confused by this > patchwork failure. > The patch applies just fine on top of master - my patch was

[OE-core] [PATCH] wayland-protocols: upgrade to 1.9

From: Denys Dmytriyenko Signed-off-by: Denys Dmytriyenko --- .../wayland/{wayland-protocols_1.8.bb => wayland-protocols_1.9.bb}| 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-graphics/wayland/{wayland-protocols_1.8.bb =>

[OE-core] [PATCH][pyro] mkefidsk: fix bash/dash shell quoting problem

mkefidsk currently writes a startup.nsh with embedded control characters. This happens because \b etc are control sequences to the shell echo command when using dash. The resulting startup.nsh causes the bootup to fail, and the user is dropped into the EFI shell to manually run startup.nsh. Patch

Re: [OE-core] ✗ patchtest: failure for gettext: Enable generation of libasprintf in gettext 0.19

Can anyone help me with undestanding this - I'm confused by this patchwork failure. The patch applies just fine on top of master - my patch was based on top of the commit with the hash referenced by patchwork below. Thanks, Lev Iserovich On 07/10/2017 05:31 PM, Patchwork wrote: == Series

[OE-core] [PATCH] libarchive: Upgrade to 3.3.2 release

Signed-off-by: Otavio Salvador --- .../libarchive/{libarchive_3.3.1.bb => libarchive_3.3.2.bb} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-extended/libarchive/{libarchive_3.3.1.bb => libarchive_3.3.2.bb} (93%) diff --git

[OE-core] [PATCH 6/6] linux-yocto-dev: bump to 4.12+

Signed-off-by: Bruce Ashfield --- meta/recipes-kernel/linux/linux-yocto-dev.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-kernel/linux/linux-yocto-dev.bb b/meta/recipes-kernel/linux/linux-yocto-dev.bb index

[OE-core] [PATCH 4/6] linux-yocto/4.4: update to v4.4.76

Integrating the -stable commit with the following changes: 4282d39575bf Linux 4.4.76 be8c39b47061 KVM: nVMX: Fix exception injection 77d977dd78b3 KVM: x86: zero base3 of unusable segments 3b1609f6c436 KVM: x86/vPMU: fix undefined shift in intel_pmu_refresh() b9b3eb5c774e KVM: x86:

[OE-core] [PATCH 1/6] kernel-yocto: propagate configuration errors to bbclass

As pointed out by klapperichp...@johndeere.com, missing configuration fragments were being picked up twice, once by the tools and once by the bbclass. Unfortunately, the tools error message was being detected as configs, and hence no error was reported at all. Rather than catching the output of

[OE-core] [PATCH 5/6] linux-yocto/4.9: update to v4.9.36

Integrating the -stable release with the following commits: 9f86f302ec0e Linux 4.9.36 a29fd27ca268 KVM: nVMX: Fix exception injection d1d3756f07da KVM: x86: zero base3 of unusable segments f3c3ec96e5fb KVM: x86/vPMU: fix undefined shift in intel_pmu_refresh() 1eeb79426332 KVM: x86:

[OE-core] [PATCH 3/6] linux-yocto/4.1: update to v4.1.41

Integrating the korg -stable update that comprises the following commits: 4bd4cfc5210e Linux 4.1.41 c1dd3f51ad77 mm/huge_memory.c: respect FOLL_FORCE/FOLL_COW for thp afeb39160249 xc2028: Fix use-after-free bug properly 5eef36af5974 iio: proximity: as3935: fix as3935_write

[OE-core] [PATCH 2/6] kernel-yocto/meta: smp configuration changes

Integrating the following kernel configuration changes to clean up the SMP configuration fragments and fix a configuration audit warning. d0e5ea0e199b smp: Separate smp into 32 and 64 bit versions to avoid kernel warnings f1369c1d817e bsp/mohonpeak: smp gets added by default, remove

[OE-core] [PATCH 0/6] kernel-yocto: consolidated pull request

Hi all, There are a couple of repeated patches in this series, but I'm sending them along just to make sure that all my pending patches are grouped together. In this series, we have a configuratiion tweak (that fixes a build warning), -stable updates for all the active kernels, a bug fix for

[OE-core] [PATCH 2/2] runqemu: check exit code of 'ls -t'

Used check_output instead of Popen as it raises CalledProcessError exception when command exits with non-zero exit code. Catched the exception to produce user-friendly output. [YOCTO #11719] Signed-off-by: Ed Bartosh --- scripts/runqemu | 5 - 1 file changed, 4

[OE-core] [PATCH 1/2] runqemu: reworked exception handling

Introduced custom RunQemuException that script raises on known errors. This exception is handled in one place and prints error output without printing Python traceback. This shoud make error output less scary for the end user. Handling of unknown errors has not been changed - both error and

[OE-core] [PATCH 0/2] runqemu: rework of exception handling

Hi, Reorganized exception handling code in a way that script raises RunQemuError for all known errors. runqemu will not produce tracebacks for known errors. It will only print error messages, which is hopefully more user friendly than current approach. Fixed 11719 - Unneeded stack trace is

Re: [OE-core] [PATCH] gcc-cross: Fix linker and fortran symlinks

On Tue, Jul 11, 2017 at 7:16 AM, Martin Jansa wrote: > Shouldn't the symlink be created in ${D}${STAGING_DIR_NATIVE} as suggested > in: > http://lists.openembedded.org/pipermail/openembedded-core/2014-April/091480.html unrelated to this change but I agree, probably we can

Re: [OE-core] [PATCH] gcc-cross: Fix linker and fortran symlinks

Shouldn't the symlink be created in ${D}${STAGING_DIR_NATIVE} as suggested in: http://lists.openembedded.org/pipermail/openembedded-core/2014-April/091480.html On Tue, Jul 11, 2017 at 3:05 PM, Khem Raj wrote: > If we used -fuse-ld gcc option, then it does not work > ending

[OE-core] [PATCH] gcc-cross: Fix linker and fortran symlinks

If we used -fuse-ld gcc option, then it does not work ending in collect2: fatal error: cannot find 'ld'

Re: [OE-core] [PATCH v3 2/2] initramfs-framwork: module to support boot live image

On Tue, Jul 11, 2017 at 2:36 AM, Ng, Wei Tee wrote: > Yes, I had squash the changes into a single commit and corrected the typo > also. The changes is being submitted to the mailing list. > Thanks a lot! There are bad indents yet; please double check it all. -- Otavio

[OE-core] [PATCH 2/3] libx11: fix build error

libx11 build fails with this error: fatal error: bits/long-double-64.h: No such file or directory | compilation terminated. This is due to the fact that "makekeys" should be compiled for the host since it is executed at build time to generate ks_tables.h. Since we have the X11 include files in

[OE-core] [PATCH 1/3] pkgconf: add recipe

Move pkgconf recipe to oe-core from meta-pkgconf: https://github.com/kergoth/meta-kergoth-wip/tree/master/meta-pkgconf Signed-off-by: Christopher Larson Signed-off-by: Maxin B. John --- meta/files/common-licenses/pkgconf | 10

[OE-core] [PATCH 3/3] libxt: fix build failure

libxt build fails with this error: /home/maxin/poky/build/tmp/work/i586-poky-linux/libxt/1_1.1.5-r0/recipe-sysroot/usr/include/bits/long-double.h:57:33: fatal error: bits/long-double-64.h: No such file or directory | compilation terminated. | Makefile:408: recipe for target 'makestrs.o' failed

[OE-core] [PATCH 0/3] pkgconf: consider pkgconf as a replacement for pkg-config

pkgconf is a better replacement for pkg-config. Fedora 26 replaces the system pkg-config implementation with pkgconf because it "provides better support for handling .pc files and a stable library ABI/API for integrating into applications." and is actively maintained, unlike pkg-config. pkgconf

Re: [OE-core] [PATCH v3] valgrind: Update 3.12.0 -> 3.13.0

On 11 July 2017 at 12:42, Martin Jansa wrote: > I guess it's gold again, https://gcc.gnu.org/ml/ > gcc-patches/2014-05/msg01860.html > I just replicated this and yes your failure is gold specific. The upgrade failure is unrelated. Ross --

[OE-core] [PATCHv3] vulkan-demos: Add recipe

Sascha Willems collection of Vulkan demos is useful as a smoke testing tool. * Add patch to install binaries and data. * Add patch to fix build on X86 * Use a combination of patch and do_install_append to avoid some 3D models with unclear licensing. Signed-off-by: Jussi Kukkonen

[OE-core] [PATCH 1/1] acpitests: Remove as unmaintained

This recipe was last upgraded about ~30 releases or three years ago, it seems to only be touched when something breaks. It also has an 'interesting' license that maybe is open source... Signed-off-by: Jussi Kukkonen --- .../acpica/acpitests/aapits-linux.patch

[OE-core] [PATCH 0/1] acpitests: Remove as unmaintained

Without meta-oe in bblayers this recipe warns: do_populate_lic: acpitests: No generic license file exists for: Intel in any provider The license may actually be open source, hard to tell -- but the "Intel" license that's in meta-oe is definitely not the correct one. The recipe also seems

Re: [OE-core] [PATCH v3] valgrind: Update 3.12.0 -> 3.13.0

I guess it's gold again, https://gcc.gnu.org/ml/gcc-patches/2014-05/msg01860.html On Tue, Jul 11, 2017 at 12:11 PM, Burton, Ross wrote: > > On 11 July 2017 at 11:12, Martin Jansa wrote: > >> ptest was broken for all architectures even before

Re: [OE-core] [PATCH] dhcp: fix genetle shutdown not work while bind9 compile with --enable-threads

On 11 July 2017 at 09:13, Hongxu Jia wrote: > +Upstream-Status: Inappropriate [OE specific] > This is not OE specific. We enable a specific build combination, and it breaks. Have you reported this upstream? Should we disable gentle shutdown as it's clearly not being

Re: [OE-core] [PATCH v3] valgrind: Update 3.12.0 -> 3.13.0

On 11 July 2017 at 11:12, Martin Jansa wrote: > ptest was broken for all architectures even before 3.13.0 upgrade, wasn't > it? > Works for me, and the autobuilder, before the upgrade. Curious what the difference is. Ross --

Re: [OE-core] [PATCH v3] valgrind: Update 3.12.0 -> 3.13.0

On Tue, Jul 11, 2017 at 09:43:24AM +0100, Burton, Ross wrote: > On 9 July 2017 at 08:35, Soren Brinkmann wrote: > > > Signed-off-by: Soren Brinkmann > > --- > > v3: > > - rebased onto latest master branch > > v2: > > - no change > > > >

Re: [OE-core] [PATCH] update distro_alias to include unmap packages on other distro

Hi Shen Joon, The commit message doesn't match the expected format of "primary item changed: short summary Long description" as documented at: https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines If in doubt about how to describe the primary item changed git log is invaluable, in

Re: [OE-core] [PATCH v2 2/2] mesa: Upgrade to 17.1.4 release

On 3 July 2017 at 23:02, Otavio Salvador wrote: > This includes following upstream bug fixes: > > Bug 77240 - khrplatform.h not installed if EGL is disabled > Saying this here as well for visibility: This conflicts with userland from meta-raspberrypi because both

  1   2   >