Re: [OE-core] [PATCH 3/4] linux-yocto: Mark qemuriscv64 as compatible

2019-06-17 Thread Bruce Ashfield
On Mon, Jun 17, 2019 at 6:04 PM Alistair Francis wrote: > > Signed-off-by: Alistair Francis > --- > meta/recipes-kernel/linux/linux-yocto_5.0.bb | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/meta/recipes-kernel/linux/linux-yocto_5.0.bb >

[OE-core] [PATCH] lighttpd:upgrade 1.4.53 -> 1.4.54

2019-06-17 Thread Zang Ruochen
-Upgrade from lighttpd_1.4.53.bb to lighttpd_1.4.54.bb. Signed-off-by: Zang Ruochen --- .../lighttpd/{lighttpd_1.4.53.bb => lighttpd_1.4.54.bb} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-extended/lighttpd/{lighttpd_1.4.53.bb => lighttpd_1.4.54.bb}

[OE-core] [PATCH] less: upgrade 550 -> 551

2019-06-17 Thread Yi Zhao
Signed-off-by: Yi Zhao --- meta/recipes-extended/less/{less_550.bb => less_551.bb} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-extended/less/{less_550.bb => less_551.bb} (89%) diff --git a/meta/recipes-extended/less/less_550.bb

Re: [OE-core] [PATCH 1/1] pkgdata: fix test_find_path to consider multilib

2019-06-17 Thread ChenQi
On 06/17/2019 11:51 PM, Richard Purdie wrote: On Mon, 2019-06-17 at 16:32 +0800, Chen Qi wrote: Fix test_find_path test case to take into consideration of multilib being enabled. After this change, no matter multilib is enabled or not, the test case should pass. Signed-off-by: Chen Qi ---

Re: [OE-core] [PATCH 1/1] manifest.py: fix test_SDK_manifest_entries

2019-06-17 Thread ChenQi
On 06/17/2019 11:54 PM, Richard Purdie wrote: On Mon, 2019-06-17 at 17:24 +0800, Chen Qi wrote: TOOLCHAIN_OUTPUTNAME could be overridden. So use this variable directly instead of its default value ${SDK_NAME}-toolchain-${SDK_VERSION}. Signed-off-by: Chen Qi ---

Re: [OE-core] [PATCH] mtd-utils: upgrade 2.0.2 -> 2.1.0

2019-06-17 Thread Denys Dmytriyenko
On Wed, Jun 12, 2019 at 11:26:06PM +0100, Richard Purdie wrote: > On Wed, 2019-06-12 at 18:23 -0400, Denys Dmytriyenko wrote: > > On Wed, Jun 12, 2019 at 08:33:26AM +0300, Adrian Bunk wrote: > > > On Tue, Jun 11, 2019 at 05:41:52PM -0400, Denys Dmytriyenko wrote: > > > > ... > > > > * Now requires

[OE-core] [PATCH v2 1/2] mtd-utils: upgrade 2.0.2 -> 2.1.0+

2019-06-17 Thread Denys Dmytriyenko
From: Denys Dmytriyenko * 0001-Revert-Return-correct-error-number-in-ubi_get_vol_in.patch is upstreamed * Add "crypto" PACKAGECONFIG for UBIFS crypto features * One extra commit after 2.1.0 release tag is pulled in to fix openssl error when "crypto" PACKAGECONFIG is not enabled: | In file

[OE-core] [PATCH 2/2] mtd-utils: add "jffs" and "ubifs" PACKAGECONFIG options

2019-06-17 Thread Denys Dmytriyenko
From: Denys Dmytriyenko Enabled by default, but allow to optionally disable them. Signed-off-by: Denys Dmytriyenko --- meta/recipes-devtools/mtd/mtd-utils_git.bb | 8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/meta/recipes-devtools/mtd/mtd-utils_git.bb

[OE-core] [PATCH] shadow: fix configure error with dash

2019-06-17 Thread Yi Zhao
A configure error occurs when /bin/sh -> dash: checking for is_selinux_enabled in -lselinux... yes checking for semanage_connect in -lsemanage... yes configure: 16322: test: yesyes: unexpected operator Use "=" instead of "==" since dash doesn't support the latter. Signed-off-by: Yi Zhao

[OE-core] Yocto Project Newcomer & Unassigned Bugs - Help Needed

2019-06-17 Thread sjolley.yp.pm
All, The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on the triage page under the appropriate heading:

[OE-core] ✗ patchtest: failure for "libffi: Add RISC-V support..." and 3 more

2019-06-17 Thread Patchwork
== Series Details == Series: "libffi: Add RISC-V support..." and 3 more Revision: 1 URL : https://patchwork.openembedded.org/series/18186/ 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 3/4] libmodule-build-perl: move from meta-perl

2019-06-17 Thread Tim Orling
* cpan_build.bbclass DEPENDS on libmodule-build-perl * add self as maintainer Fixes [YOCTO #12873] Signed-off-by: Tim Orling --- meta/conf/distro/include/maintainers.inc | 1 + .../perl/libmodule-build-perl_0.4224.bb | 34 +++ 2 files changed, 35 insertions(+)

[OE-core] [PATCH 2/4] libxml-sax-perl: upgrade 1.00 -> 1.02

2019-06-17 Thread Tim Orling
* Sort ptest dependencies alphabetically Upstream release notes: 1.02 14 Jun 2019 Grant McLean - Spelling fixes (patch from Ville Skyttä) - Add repo location to metadata (patches from Ville Skyttä & Martin McGrath) - Reorganise module files under lib/XML - Regenerate MANIFEST

[OE-core] [PATCH 4/4] libmodule-build-perl: upgrade 0.4224 -> 0.4229; enable ptest

2019-06-17 Thread Tim Orling
* Add runtime and ptest dependencies * Add own run-ptest, since we need to run blib License-Update: License lines moved up in README Upstream release notes: 0.4229 - Tue Apr 16 00:49:45 CEST 2019 - Released 0.42_28 without changes 0.42_28 - Thu Apr 19 16:34:32 CEST 2018 - Replace

[OE-core] [PATCH 0/4] perl updates, fixes and libmodule-buil-perl

2019-06-17 Thread Tim Orling
* Many perl dependency fixes uncovered in libmodule-build-perl ptest and meta-perl maintenance. * Update libxml-sax-perl from 1.00 -> 1.02 * Import libmodule-build-perl from meta-perl for cpan_build.bbclass support [YOCTO #12873] * Upgrade libmodule-build-perl from 0.4224 -> 0.4229 and enable

[OE-core] [PATCH 1/4] perl-rdepends.txt: more ptest dependencies fixes

2019-06-17 Thread Tim Orling
* File::Spec::Unix runtime depends on Cwd and constant * Module::Metadata runtime depends on version * CPAN::Meta runtime depends on Parse::CPAN::Meta and JSON::PP * ExtUtils::MakeMaker runtime depends on ExtUtils::MM_Unix * TAP::Base runtime depends on TAP::Object *

[OE-core] [PATCH 1/4] libffi: Add RISC-V support

2019-06-17 Thread Alistair Francis
Backport a libffi patch to add RISC-V support. Signed-off-by: Alistair Francis --- .../libffi/0001-New-RISC-V-port-281.patch | 827 ++ meta/recipes-support/libffi/libffi_3.2.1.bb | 5 +- 2 files changed, 830 insertions(+), 2 deletions(-) create mode 100644

[OE-core] [PATCH 4/4] qemuriscv64: Add the QEMU RISC-V 64-bit machine

2019-06-17 Thread Alistair Francis
The include is split ready to add the 32-bit RISC-V machine as soon as glibc supports 32-bit RISC-V. This is based on the work in the meta-riscv layer, thanks to Khem for starting this. Signed-off-by: Alistair Francis --- .../conf/machine/include/riscv/arch-riscv.inc | 10 +

[OE-core] [PATCH 2/4] opensbi: Initial commit of OpenSBI

2019-06-17 Thread Alistair Francis
This is used as a bootloader for RISC-V QEMU machines. Signed-off-by: Alistair Francis --- ...Makefile-Don-t-specify-mabi-or-march.patch | 38 ++ ...-address-of-packed-member-warning-wi.patch | 52 +++ meta/recipes-bsp/opensbi/opensbi-payloads.inc | 37 +

[OE-core] [PATCH 3/4] linux-yocto: Mark qemuriscv64 as compatible

2019-06-17 Thread Alistair Francis
Signed-off-by: Alistair Francis --- meta/recipes-kernel/linux/linux-yocto_5.0.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-kernel/linux/linux-yocto_5.0.bb b/meta/recipes-kernel/linux/linux-yocto_5.0.bb index 8aec315084..a79d0b962d 100644 ---

Re: [OE-core] [PATCH] wic/bootimg-efi: allow multiple initrd

2019-06-17 Thread Richard Purdie
On Thu, 2019-06-13 at 14:21 +0800, chee.yang@intel.com wrote: > From: Chee Yang Lee > > Allow plugin bootimg-efi to configure with multiple initrd > through source parameter. > > Uses ; to separate each initrd. > > e.g: > --sourceparams="loader=${EFI_PROVIDER},initrd=initrd1;initrd2" > >

[OE-core] [PATCH] volatile-binds: Change cp to use -a instead of -p.

2019-06-17 Thread luca . boccassi
From: Chris PeBenito This is needed on SELinux systems, so the labels (xattrs) are preserved. Signed-off-by: Chris PeBenito --- meta/recipes-core/volatile-binds/files/mount-copybind | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

Re: [OE-core] [PATCH] serf: cleanup recipe

2019-06-17 Thread Martin Jansa
Hello, now serf is failing to build here: DEBUG: Executing python function extend_recipe_sysroot NOTE: Direct dependencies are ['TOPDIR/oe-core/meta/recipes-devtools/gcc/gcc-runtime_9.1.bb:do_populate_sysroot',

Re: [OE-core] [PATCH 1/1] manifest.py: fix test_SDK_manifest_entries

2019-06-17 Thread Richard Purdie
On Mon, 2019-06-17 at 17:24 +0800, Chen Qi wrote: > TOOLCHAIN_OUTPUTNAME could be overridden. So use this variable directly > instead of its default value ${SDK_NAME}-toolchain-${SDK_VERSION}. > > Signed-off-by: Chen Qi > --- > meta/lib/oeqa/selftest/cases/manifest.py | 7 ++- > 1 file

Re: [OE-core] [PATCH v2] inetutils: Fix the rcp couldn't copy subdirectory issue

2019-06-17 Thread Richard Purdie
On Mon, 2019-06-17 at 01:39 -0700, Zhixiong Chi wrote: > Since snprintf doesn't support the same src and dst address, it will get > the wrong result. > In the sink second recursive call env, the argv and the namebuf will point > the same address, after free operation for namebuf. > So the last

Re: [OE-core] [PATCH 1/1] pkgdata: fix test_find_path to consider multilib

2019-06-17 Thread Richard Purdie
On Mon, 2019-06-17 at 16:32 +0800, Chen Qi wrote: > Fix test_find_path test case to take into consideration of multilib > being enabled. After this change, no matter multilib is enabled or > not, the test case should pass. > > Signed-off-by: Chen Qi > --- >

Re: [OE-core] [AUH] lttng-ust: upgrading to 2.10.4 FAILED

2019-06-17 Thread Richard Purdie
On Mon, 2019-06-17 at 16:51 +0200, Alexander Kanavin wrote: > On Mon, 17 Jun 2019 at 16:22, Richard Purdie > wrote: > > >Yes, it's another one of those recipes which includes a > > >different recipe with its version number (which breaks when > > >devtool upgrades one but not the other). > > > >

Re: [OE-core] [AUH] lttng-ust: upgrading to 2.10.4 FAILED

2019-06-17 Thread Alexander Kanavin
On Mon, 17 Jun 2019 at 16:22, Richard Purdie wrote: > >Yes, it's another one of those recipes which includes a > >different recipe with its version number (which breaks when > >devtool upgrades one but not the other). > > > >I have a fix queued: > > >

Re: [OE-core] [AUH] lttng-ust: upgrading to 2.10.4 FAILED

2019-06-17 Thread Richard Purdie
From: Alexander Kanavin :>Yes, it's another one of those recipes which includes a >different recipe with its version number (which breaks when >devtool upgrades one but not the other).>>I have a fix

Re: [OE-core] [AUH] lttng-ust: upgrading to 2.10.4 FAILED

2019-06-17 Thread Alexander Kanavin
Yes, it's another one of those recipes which includes a different recipe with its version number (which breaks when devtool upgrades one but not the other). I have a fix queued:

Re: [OE-core] [AUH] lttng-ust: upgrading to 2.10.4 FAILED

2019-06-17 Thread richard . purdie
On Sun, 2019-06-16 at 14:57 -0700, a...@auh.yoctoproject.org wrote: > Hello, > > You are receiving this email because you are the maintainer > of *lttng-ust* recipe and this is to let you know that the automatic > attempt > to upgrade the recipe to *2.10.4* has Failed(get_env). > > Detailed

Re: [OE-core] [PATCH] Add release field to version in rpm package dictionary

2019-06-17 Thread richard . purdie
On Sun, 2019-06-16 at 19:11 -0700, akuster wrote: > Hello Micheal, > > > On 5/25/19 6:29 AM, Corey Minyard wrote: > > On Mon, Apr 29, 2019 at 02:43:42PM -0500, miny...@acm.org wrote: > > > From: Corey Minyard > > I haven't heard anything on this. Is this a proper change? > > > > -corey > I

Re: [OE-core] [PATCH 1/2] mesa: make gallium swrast target optional

2019-06-17 Thread Alexander Kanavin
Yes please, I think that is the best way out for qemu. Alex On Mon, 17 Jun 2019 at 11:35, Marco Felsch wrote: > On 19-06-14 15:37, Alexander Kanavin wrote: > > On Fri, 14 Jun 2019 at 15:36, Burton, Ross > wrote: > > > > > > Dropping the swrast dependency will not help though, as it is >

Re: [OE-core] [PATCH 1/2] mesa: make gallium swrast target optional

2019-06-17 Thread Marco Felsch
On 19-06-14 15:37, Alexander Kanavin wrote: > On Fri, 14 Jun 2019 at 15:36, Burton, Ross wrote: > > > > Dropping the swrast dependency will not help though, as it is provided > > by the mesa-megadriver package, which will continue to include swrast as > > long as it is enabled in the mesa

[OE-core] [PATCH 1/1] manifest.py: fix test_SDK_manifest_entries

2019-06-17 Thread Chen Qi
TOOLCHAIN_OUTPUTNAME could be overridden. So use this variable directly instead of its default value ${SDK_NAME}-toolchain-${SDK_VERSION}. Signed-off-by: Chen Qi --- meta/lib/oeqa/selftest/cases/manifest.py | 7 ++- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git

[OE-core] [PATCH 0/1] manifest.py: fix test_SDK_manifest_entries

2019-06-17 Thread Chen Qi
*** BLURB HERE *** The following changes since commit 27d60c5a812774f0e5c43161e5b514c4aebdf301: gstreamer1.0-libav: disable API documentation (2019-06-15 13:46:38 +0100) are available in the git repository at: git://git.pokylinux.org/poky-contrib ChenQi/oeqa-manifest

[OE-core] [PATCH v2] inetutils: Fix the rcp couldn't copy subdirectory issue

2019-06-17 Thread Zhixiong Chi
Since snprintf doesn't support the same src and dst address, it will get the wrong result. In the sink second recursive call env, the argv and the namebuf will point the same address, after free operation for namebuf. So the last change for this is wrong, now we just drop the free function in the

[OE-core] ✗ patchtest: failure for inetutils: Fix the rcp couldn't copy subdirectory issue

2019-06-17 Thread Patchwork
== Series Details == Series: inetutils: Fix the rcp couldn't copy subdirectory issue Revision: 1 URL : https://patchwork.openembedded.org/series/18178/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests

[OE-core] [PATCH] inetutils: Fix the rcp couldn't copy subdirectory issue

2019-06-17 Thread Zhixiong Chi
Since snprintf doesn't support the same src and dst address, it will get the wrong result. In the sink second recursive call env, the argv and the namebuf will point the same address, after free operation for namebuf. So the last change for this is wrong, now we just drop the free function in the

[OE-core] [PATCH 1/1] pkgdata: fix test_find_path to consider multilib

2019-06-17 Thread Chen Qi
Fix test_find_path test case to take into consideration of multilib being enabled. After this change, no matter multilib is enabled or not, the test case should pass. Signed-off-by: Chen Qi --- meta/lib/oeqa/selftest/cases/pkgdata.py | 7 --- 1 file changed, 4 insertions(+), 3 deletions(-)

[OE-core] [PATCH 0/1] pkgdata: fix test_find_path to consider multilib

2019-06-17 Thread Chen Qi
*** BLURB HERE *** The following changes since commit 27d60c5a812774f0e5c43161e5b514c4aebdf301: gstreamer1.0-libav: disable API documentation (2019-06-15 13:46:38 +0100) are available in the git repository at: git://git.pokylinux.org/poky-contrib ChenQi/oeqa-pkgdata

[OE-core] [PATCH 1/1] buildoptions.py: fix test_arch_work_dir_and_export_source

2019-06-17 Thread Chen Qi
If multilib is enabled, allarch is actually disabled. So take this into consideration in this test case, using /*/ instead of /allarch*/. Also, use xcursor-transparent-theme* instead of xcursor* for more accurate match. Signed-off-by: Chen Qi --- meta/lib/oeqa/selftest/cases/buildoptions.py |

[OE-core] [PATCH 0/1] buildoptions.py: fix test_arch_work_dir_and_export_source

2019-06-17 Thread Chen Qi
*** BLURB HERE *** The following changes since commit 27d60c5a812774f0e5c43161e5b514c4aebdf301: gstreamer1.0-libav: disable API documentation (2019-06-15 13:46:38 +0100) are available in the git repository at: git://git.pokylinux.org/poky-contrib ChenQi/oeqa-buildoptions

[OE-core] [PATCH v4] lttng-modules: Add git based recipe

2019-06-17 Thread zhe.he
From: He Zhe The git based recipe is for those who want to build lttng-modules with bleeding edge kernel, to avoid regularly backporting patches from upstream. Note that PREFERRED_VERSION needs to be set to select the git recipe instead of the tar ball one. Signed-off-by: He Zhe --- v2:

Re: [OE-core] [PATCH] xmlto: set CLEANBROKEN = "1"

2019-06-17 Thread Hongxu Jia
Ping //Hongxu On 5/21/19 4:49 PM, Hongxu Jia wrote: While rebuilding xmlto or xmlto-native, `make clean' in do_configure will remove man/man1/xmlif.1 which triger failure in do_compile $ bitbake xmlto-native $ bitbake xmlto-native -cconfigure -f $ bitbake xmlto-native -ccompile -f ...