Re: [oe] [PATCH 0/2] poppler nightmare

I recently tried to cross build the current version of poppler for an embedded ARM system. This was not under the Yocto/OE build environment, but I never could get quite the right cmake config file to get the thing to build. Since I just needed it for the pdftoraster cups filter, I punted and

Re: [oe] [PATCH 0/2] poppler nightmare

On Wed, Apr 4, 2018 at 3:32 AM, akuster808 wrote: > Andreas, > > > > On 04/03/2018 04:15 PM, Andreas Müller wrote: >> Not convinced that I'll get support at poppler project. Let's see what >> autobuilder says. If it fails, please unroll back to 0.57.0 - I am sure >> that

Re: [oe] [PATCH 0/2] poppler nightmare

Andreas, On 04/03/2018 04:15 PM, Andreas Müller wrote: > Not convinced that I'll get support at poppler project. Let's see what > autobuilder says. If it fails, please unroll back to 0.57.0 - I am sure > that disable glib causes trouble for evince. this didn't make it into the current world

Re: [oe] [meta-networking][PATCH] tcpdump: refresh local patches to avoid fuzz warnings

On 04/03/2018 04:03 PM, Denys Dmytriyenko wrote: > From: Denys Dmytriyenko > > Signed-off-by: Denys Dmytriyenko > --- at fix like this is in master-next already. - armin > .../recipes-support/tcpdump/tcpdump/add-ptest.patch | 13 +++-- >

Re: [oe] [PATCH] iperf3: refresh local patches to avoid fuzz warnings

On 04/04/2018 07:00 AM, Denys Dmytriyenko wrote: > From: Denys Dmytriyenko > > Signed-off-by: Denys Dmytriyenko > --- > ...nclude-stdint.h-for-various-std-c99-int-types.patch | 16 +++- > .../iperf3/0002-Remove-pg-from-profile_CFLAGS.patch| 12

[oe] [PATCH 0/2] poppler nightmare

Not convinced that I'll get support at poppler project. Let's see what autobuilder says. If it fails, please unroll back to 0.57.0 - I am sure that disable glib causes trouble for evince. Andreas Müller (2): poppler: Rework patch fixing do_configure poppler: update 0.62.0- > 0.63.0

[oe] [PATCH 1/2] poppler: Rework patch fixing do_configure

Turn the patch from a workaround into a proper fix. It was submitted to poppler bugzilla - but after endless discussions I won't follow this further. Signed-off-by: Andreas Müller --- ...0001-Do-not-overwrite-all-our-build-flags.patch | 36 -- 1 file

[oe] [PATCH 2/2] poppler: update 0.62.0- > 0.63.0

Signed-off-by: Andreas Müller --- .../recipes-support/poppler/{poppler_0.62.0.bb => poppler_0.63.0.bb} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta-oe/recipes-support/poppler/{poppler_0.62.0.bb => poppler_0.63.0.bb} (93%) diff --git

[oe] [meta-networking][PATCH] tcpdump: refresh local patches to avoid fuzz warnings

From: Denys Dmytriyenko Signed-off-by: Denys Dmytriyenko --- .../recipes-support/tcpdump/tcpdump/add-ptest.patch | 13 +++-- .../tcpdump/unnecessary-to-check-libpcap.patch| 19 ++- 2 files changed, 17 insertions(+), 15 deletions(-)

[oe] [PATCH] iperf3: refresh local patches to avoid fuzz warnings

From: Denys Dmytriyenko Signed-off-by: Denys Dmytriyenko --- ...nclude-stdint.h-for-various-std-c99-int-types.patch | 16 +++- .../iperf3/0002-Remove-pg-from-profile_CFLAGS.patch| 12 +--- .../iperf3/iperf3/automake-foreign.patch

[oe] [meta-oe][PATCH] rarpd, sblim-sfcb, openct: inherit systemd unconditionally

* the inherit was controlled by VIRTUAL-RUNTIME_init_manager and the installation of .service files by DISTRO_FEATURES and systemd was in DISTRO_FEATURES but not in VIRTUAL-RUNTIME_init_manager it was causing QA issues about unpackaged .service files ERROR: rarpd-ss981107-r0 do_package:

Re: [oe] [meta-networking][PATCH] wireshark: 2.2.11 -> 2.4.5

On 04/03/2018 12:30 AM, Huang Qiyu wrote: > 1.Upgrade wireshark from 2.2.11 to 2.4.5. > 2.Delete one configure option "--with-gcrypt", since it has been not > supported in 2.4.5. > 3.Add 0001-use-pkgconfig-to-check-libgcrypt.patch, since libgcrypt does no > longer provide > libgcrypt-config,

[oe] [meta-oe][PATCH 2/5] php7: upgrade to 7.2.4

* For changes, see: http://www.php.net/ChangeLog-7.php#7.2.4 * Remove patches as they've been upstreamed: - 0001-Specify-tag-with-libtool.patch - CVE-2017-16642.patch - CVE-2018-5711.patch * mcrypt module has been deprecated and as such dependency has been moved from php.inc to php5 recipe. *

[oe] [meta-oe][PATCH 1/5] php: move patches to a single directory

Having two directories with version numbers just leads to unnecessary churn everytime there's a version update. We can have all patches in one single directory and differentiate b/w specific version by prefix php5-/php7- Signed-off-by: Anuj Mittal ---

[oe] [meta-oe][PATCH 5/5] php: enable opcache by default

Signed-off-by: Anuj Mittal --- meta-oe/recipes-devtools/php/php.inc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta-oe/recipes-devtools/php/php.inc b/meta-oe/recipes-devtools/php/php.inc index 8ba218c..066b97c 100644 ---

[oe] [meta-oe][PATCH 4/5] php: add opcache extension to PACKAGECONFIG

OPcache improves PHP performance by storing precompiled script bytecode in shared memory, thereby removing the need for PHP to load and parse scripts on each request [1]. Add an option to enable opcache in php. AC_CHECK_FUNC isn't suitable for a cross-compile environment, so pass the configure

[oe] [meta-oe][PATCH 3/5] php5: upgrade to 5.6.35

For changes, see: http://php.net/ChangeLog-5.php#5.6.35 Split patches between php5 and php7 to ensure there are no fuzz warnings for both the versions. Signed-off-by: Anuj Mittal --- meta-oe/recipes-devtools/php/php.inc | 2 -

[oe] [meta-oe][PATCH 0/5] Upgrade php versions and enable opcache

These patches upgrade the versions of php recipes and enable opcache in both. I had to move around some patches to ensure both the versions compile without any fuzz warnings. There are still some unrelated issues with these recipes like the ini file not getting installed and the do_install logic

[oe] [meta-networking][PATCH] wireshark: 2.2.11 -> 2.4.5

1.Upgrade wireshark from 2.2.11 to 2.4.5. 2.Delete one configure option "--with-gcrypt", since it has been not supported in 2.4.5. 3.Add 0001-use-pkgconfig-to-check-libgcrypt.patch, since libgcrypt does no longer provide libgcrypt-config, and provide *.pc, so we should use pkgconfig to check.