[OE-core] [PATCH V2] apr: 1.6.2 -> 1.6.3

1. Improve inappropriate patches: - Drop inappropriate configure_fixes.patch Use setting variable ac_cv_file__dev_zero and ac_cv_sizeof_struct_iovec to replace - Drop cleanup.patch Aassign variable libtool at ./buildconf executing and use 0001-build-buildcheck.sh-improve-libtool-detection.

Re: [OE-core] [PATCH V2] apr: 1.6.2 -> 1.6.3

Sorry for the wrong thread, Hi Ross, I also updated the remote repo for it. git://git.pokylinux.org/poky-contrib hongxu/upgrade-20180131 http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=hongxu/upgrade-20180131 //Hongxu -- ___ Openembedded-core m

[OE-core] ✗ patchtest: failure for improve reproducibility of 6 recipes (rev2)

== Series Details == Series: improve reproducibility of 6 recipes (rev2) Revision: 2 URL : https://patchwork.openembedded.org/series/10508/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been exe

Re: [OE-core] [PATCH 01/20] oe-selftest: add a test for recipes without maintainers

On 02/01/2018 10:41 PM, Paul Eggleton wrote: I understand the intention, but I don't think oe-selftest is the right place to be doing this. It's going to fail for sure if you have any non-OE-Core layers in your configuration. One thing I have continued to campaign for (and I'm aware that not ev

Re: [OE-core] Adding a "tiny" DISTRO_FEATURE and having packages build smaller

On Fri, Feb 2, 2018 at 3:21 AM, Daniel F. Dickinson wrote: > On 01/02/18 09:19 AM, Burton, Ross wrote: >> >> On 1 February 2018 at 14:17, Daniel F. Dickinson > > wrote: >> >> On 01/02/18 09:12 AM, Burton, Ross wrote: >> >> On 1 February 2018 at 14:10, Dani

[OE-core] [PATCH 1/2] libsolv: upgrade to version 0.6.31

Remove upstreamed patch: 0001-repo_rpmdb.c-increase-MAX_HDR_CNT-and-MAX_HDR_DSIZE.patch Signed-off-by: Maxin B. John --- c-increase-MAX_HDR_CNT-and-MAX_HDR_DSIZE.patch | 35 -- .../{libsolv_0.6.29.bb => libsolv_0.6.31.bb} | 3 +- 2 files changed, 1 insertio

[OE-core] [PATCH 2/2] x264: upgrade to latest revision

Change dependency from yasm to nasm following this change: commit d2b5f4873e2147452a723b61b14f030b2ee760a5 Author: Henrik Gramner Date: Sat Mar 18 18:50:36 2017 +0100 x86: Change assembler from yasm to nasm Refreshed the following patch: don-t-default-to-cortex-a9-with-neon.patch

Re: [OE-core] [PATCH V2] apr: 1.6.2 -> 1.6.3

Yes, that. Thanks very much! Ross On 2 February 2018 at 09:06, Hongxu Jia wrote: > 1. Improve inappropriate patches: > - Drop inappropriate configure_fixes.patch > Use setting variable ac_cv_file__dev_zero and > ac_cv_sizeof_struct_iovec to replace > > - Drop cleanup.patch > Aassign vari

Re: [OE-core] ✗ patchtest: failure for e2fsprogs: fixes for ptest

Yes, this clearly isn't right. On 2 February 2018 at 07:52, Huang, Jie (Jackie) wrote: > > > > -Original Message- > > From: Patchwork [mailto:patchw...@do.openembedded.org] > > Sent: Friday, February 02, 2018 15:33 > > To: Huang, Jie (Jackie) > > Cc: openembedded-core@lists.openembedded.

Re: [OE-core] [PATCH 3/4] runqemu: check for qemuboot.conf and raise error

On 2018-02-01 10:23 PM, Robert Yang wrote: [YOCTO #12503] Signed-off-by: Robert Yang --- scripts/runqemu | 3 +++ 1 file changed, 3 insertions(+) diff --git a/scripts/runqemu b/scripts/runqemu index 0ca62f4..d50c6d1 100755 --- a/scripts/runqemu +++ b/scripts/runqemu @@ -417,6 +417,9 @@ clas

[OE-core] [PATCH 1/2] gtk-doc: update to 1.27

Gtk-doc has been rewritten in Python, so drop perl dependencies (good riddance!), and adjust patches to reflect that. Signed-off-by: Alexander Kanavin --- ...r-out-if-perl-is-not-found-or-its-version.patch | 40 -- ...hardocode-paths-to-perl-python-in-scripts.patch | 155 +++---

[OE-core] [PATCH 2/2] libfm: add a patch to fix build errors with recent versions of gtk-doc

Signed-off-by: Alexander Kanavin --- ...Enclose-text-in-programlisting-into-CDATA.patch | 76 ++ meta/recipes-support/libfm/libfm_1.2.5.bb | 4 +- 2 files changed, 79 insertions(+), 1 deletion(-) create mode 100644 meta/recipes-support/libfm/libfm/0001-Enclose-text

Re: [OE-core] ✗ patchtest: failure for ninja: Upgrade from 1.7.2 to major release 1.8.2 (rev2)

This makes no sense to me, I rebased to master just before sending it. -Original Message- From: Patchwork [mailto:patchw...@patchwork.openembedded.org] Sent: Thursday, February 1, 2018 2:33 PM To: Alejandro Enedino Hernandez Samaniego Cc: openembedded-core@lists.openembedded.org Subject:

[OE-core] [PATCH] packagegroup-core-tools-profile: disable valgrind on armeb

Valgrind supports only little endian ARM. Signed-off-by: Mariia Movchan --- meta/recipes-core/packagegroups/packagegroup-core-tools-profile.bb | 1 + 1 file changed, 1 insertion(+) diff --git a/meta/recipes-core/packagegroups/packagegroup-core-tools-profile.bb b/meta/recipes-core/packagegroups

Re: [OE-core] ✗ patchtest: failure for ninja: Upgrade from 1.7.2 to major release 1.8.2 (rev2)

On 2 February 2018 at 19:06, Alejandro Enedino Hernandez Samaniego < aleja...@xilinx.com> wrote: > This makes no sense to me, I rebased to master just before sending it. > Are you sure that the master you're rebasing is the actual upstream master? Applying: ninja: Upgrade from 1.7.2 to major rel

Re: [OE-core] ✗ patchtest: failure for ninja: Upgrade from 1.7.2 to major release 1.8.2 (rev2)

So I'm 99% sure this is Exchange tramping the mail and git not handling that, as the patch is quoted-printable encoded.I'll pick from the branch :) Ross On 2 February 2018 at 21:28, Alejandro Enedino Hernandez Samaniego < alejandro.enedino.hernandez-samani...@xilinx.com> wrote: > I might be

Re: [OE-core] ✗ patchtest: failure for ninja: Upgrade from 1.7.2 to major release 1.8.2 (rev2)

This is what I got: $ git remote show origin * remote origin Fetch URL: git://git.yoctoproject.org/poky Push URL: git://git.yoctoproject.org/poky HEAD branch: master latest commit: bca260ef4dca87c11fc9d30b2b8a17664dc2d879 ninja: Upgrade from 1.7.2 to major release 1.8.2 385944254d0ef88

Re: [OE-core] ✗ patchtest: failure for ninja: Upgrade from 1.7.2 to major release 1.8.2 (rev2)

I might be wrong but you can check it here as well: https://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=aehs29/ninja On 02/02/2018 01:22 PM, Alejandro Enedino Hernandez Samaniego wrote: This is what I got: $ git remote show origin * remote origin Fetch URL: git://git.yoctoproje

Re: [OE-core] [PATCH v2] ninja: Upgrade from 1.7.2 to major release 1.8.2

On 02/01/2018 02:10 PM, Alejandro Enedino Hernandez Samaniego wrote: Signed-off-by: Alejandro Enedino Hernandez Samaniego --- meta/recipes-devtools/ninja/ninja_1.7.2.bb | 30 -- meta/recipes-devtools/ninja/ninja_1.8.2.bb | 30 ++ 2 fi

[OE-core] [PATCH] apt-native: Add libapt-pkg headers

From: Jan Siegmund Native tools were not able to use the headers of apt-pkg. This patch adds the feature. The headers were added from apt-pkg and apt-inst to the native recipe. The shipped headers match the ones in the Ubuntu package libapt-pkg-dev. Signed-off-by: Jan Siegmund --- meta/recipes

Re: [OE-core] [PATCH v2] ninja: Upgrade from 1.7.2 to major release 1.8.2

Hey Cal, On 02/01/2018 02:10 PM, Alejandro Enedino Hernandez Samaniego wrote: > Signed-off-by: Alejandro Enedino Hernandez Samaniego > > --- > meta/recipes-devtools/ninja/ninja_1.7.2.bb | 30 > -- > meta/recipes-devtools/ninja/ninja_1.8.2.bb | 30 > ++

[OE-core] [PATCH] gcc: enable build-id in gcc-cross-initial

Normal gcc-cross has build-id feature enabled by default, so most of target binaries has build-id. But libc (glibc, musl) doesn't have build-id, because it is built with gcc-cross-initial. Build-id is a useful feature, so enable it for gcc-cross-initial too. Signed-off-by: Taras Kondratiuk ---

Re: [OE-core] ✗ patchtest: failure for ninja: Upgrade from 1.7.2 to major release 1.8.2 (rev2)

Cool, thanks! Alejandro From: Burton, Ross [mailto:ross.bur...@intel.com] Sent: Friday, February 2, 2018 1:35 PM To: Alejandro Enedino Hernandez Samaniego Cc: openembedded-core@lists.openembedded.org Subject: Re: [OE-core] ✗ patchtest: failure for ninja: Upgrade from 1.7.2 to major release 1.8.

[OE-core] [PATCH] libacpi: update libacpi_fix_for_x32.patch to use libdir

Prefix plus base_libdir generates an invalid path when building with usrmerge, so change libacpi_fix_for_x32.patch to use libdir instead as it provides the right path in both cases. Signed-off-by: Ricardo Salveti --- .../libacpi/files/libacpi_fix_for_x32.patch| 30 --