[OE-core] [PATCH 1/1] autotools: do more cleanup when in do_configure

I met the following error when compiling some projects. | configure: error: `LDFLAGS' has changed since the previous run: | configure: former value: `-Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed' | configure: current value: `-Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed

[OE-core] [PATCH 0/1] autotools: do more cleanup when in do_configure

*** BLURB HERE *** The following changes since commit c710430aa1a5a30d3087c3102485d4621e8d179e: Revert "prelink: Fix SRC_URI and branch" (2018-09-06 14:49:28 +0100) are available in the git repository at: git://git.pokylinux.org/poky-contrib ChenQi/autotools-clean

Re: [OE-core] [oe-core][PATCH v4 1/3] udev-extraconf/mount.sh: add support to systemd

On 2018年08月24日 10:00, Randy MacLeod wrote: First, I have a few changes to make the log more clear. On 08/01/2018 10:50 PM, Hongzhi.Song wrote: Udev-extraconf works correctly with sysvinit in the aspect of automounting block devices. But it has a serious problem in case of systemd. Block

Re: [OE-core] [oe] [openembedded][wayland][weston]: How to configure screen resolution

Hi Mohamed, On 9.09.2018 14:10, Mohamed Dawod wrote: > Hello, > > I want to know how to change the screen resolution using weston.ini file ? You can set the resolution size width and height in pixels with property mode in the output section of weston.ini. For example: [output] mode=1680x1050

[OE-core] [PATCH] bind: patch for CVE-2018-5740

From: Changqing Li Signed-off-by: Changqing Li --- .../bind/bind/CVE-2018-5740.patch | 72 ++ meta/recipes-connectivity/bind/bind_9.11.4.bb | 1 + 2 files changed, 73 insertions(+) create mode 100644

[OE-core] [PATCH] attr: use u-a for setfattr

setfattr is now provided also by busybox since 1.29.2 upgrade and do_rootfs is failing with: update-alternatives: Error: not linking usr/bin/setfattr to /bin/busybox.nosuid since usr/bin/setfattr exists and is not a link Signed-off-by: Martin Jansa --- meta/recipes-support/attr/attr.inc | 6

[OE-core] [PATCH] ghostscript: fix CVE-2018-15908 & CVE-2018-15909 & CVE-2018-15910 & CVE-2018-15911

Signed-off-by: Hongxu Jia --- ...Bug-699665-memory-corruption-in-aesdecode.patch | 56 + ...Handle-LockDistillerParams-not-being-a-bo.patch | 53 + ...660-shading_param-incomplete-type-checkin.patch | 91 ++ .../0004-Hide-the-.shfill-operator.patch

[OE-core] ✗ patchtest: failure for bind: patch for CVE-2018-5740

== Series Details == Series: bind: patch for CVE-2018-5740 Revision: 1 URL : https://patchwork.openembedded.org/series/13987/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been executed on the

Re: [OE-core] [PATCH v2] python3{,-native}: update to 3.7.0

Large parts of dnf and friends have been rewritten in c++. I have not yet updated and reviewed that, that will happen in the next cycle. There's already enough disruption to deal with (postinsts errors, openssl 1.1, both caused by me :) Good that we got all the way to do_rootfs though with 3.7.

Re: [OE-core] [PATCH 1/1] autotools: do more cleanup when in do_configure

On 10 September 2018 at 11:02, Chen Qi wrote: > I met the following error when compiling some projects. > > | configure: error: `LDFLAGS' has changed since the previous run: > | configure: former value: `-Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed' > | configure: current value: `-Wl,-O1

[OE-core] [PATCH] tclibc-baremetal.inc: Remove BASEDEPENDS on compilerlibs

Without a libc the gcc-runtime provider of compilerlibs does not compile. As such avoid the default dependence on the virtual/${TARGET_PREFIX}compilerlibs provider. Signed-off-by: Nathan Rossi --- meta/conf/distro/include/tclibc-baremetal.inc | 3 +++ 1 file changed, 3 insertions(+) diff --git

[OE-core] [PATCH 3/4] python3: remove patch that inadvertently disables xattrs

This patch dates back to the addition of the Python 3 recipe to oe-core, and as listxattr is never added to supports_follow_symlinks the extended attribute support will never be enabled. Signed-off-by: Ross Burton --- meta/recipes-devtools/python/python3-native_3.5.5.bb| 1 -

[OE-core] [PATCH 4/4] python3: fix multiprocessing

glibc 2.28 slightly changed the behaviour of sigaddset() which broke multiprocessing. Backport a patch from Python 3.6 to solve this. Signed-off-by: Ross Burton --- meta/recipes-devtools/python/python3/signal.patch | 56 +++ meta/recipes-devtools/python/python3_3.5.5.bb

[OE-core] [PATCH 2/4] python3: remove redundant patch

None of the Python invocations that this changes are actually called, and there's no need to provide a HOSTPGEN variable when the recipe can just override PGEN directly. Signed-off-by: Ross Burton --- .../python/python3-native_3.5.5.bb | 1 -

[OE-core] [PATCH 1/4] python3: fix ftplib with TLS 1.3

With OpenSSL 1.1.x TLS 1.3 can be used, so backport a patch from Python 3.6 to fix the ftplib unit test. Signed-off-by: Ross Burton --- meta/recipes-devtools/python/python3/ftplib.patch | 57 +++ meta/recipes-devtools/python/python3_3.5.5.bb | 1 + 2 files changed, 58

Re: [OE-core] [PATCH 0/3] Misc fixes

I never saw these on the list, just the cover letter. So the serf change introduces three patches, two of which are backports with nice descriptions but one (0003-gen_def.patch) doesn't have a description, upstream-status, or signed-off-by. Can you add those as appropriate? Ross On 3 September

[OE-core] [PATCH] libgloss_3.0.0.bb: Fix up mv pattern to include libnosys

When installing libgloss libraries handle the ${TARGET_SYS}/lib contents so that it is placed in ${libdir} instead of ${libdir}/lib. This resolves a packaging QA issue. ERROR: libgloss-3.0.0-r0 do_package: QA Issue: libgloss: Files/directories were installed but not shipped in any package:

[OE-core] [PATCH] tclibc: For newlib and baremetal disable some security features

With GCCPIE being enabled by default with security_flags.inc the compiler will by default attempt to compile and link programs as PIE. The targets that use newlib and baremetal in general do not support PIE or are otherwise unable to use it due to how embedded targets are compiled and executed. As

[OE-core] [PATCH] serf: Document and add upstream status field for 0003-gen_def.patch

Signed-off-by: Khem Raj --- meta/recipes-support/serf/serf/0003-gen_def.patch | 5 + 1 file changed, 5 insertions(+) diff --git a/meta/recipes-support/serf/serf/0003-gen_def.patch b/meta/recipes-support/serf/serf/0003-gen_def.patch index e37e9034b0..0ea2cca9df 100644 ---

Re: [OE-core] [PATCH] tclibc-baremetal.inc: Remove BASEDEPENDS on compilerlibs

On Mon, Sep 10, 2018 at 5:45 AM Nathan Rossi wrote: > > Without a libc the gcc-runtime provider of compilerlibs does not > compile. As such avoid the default dependence on the > virtual/${TARGET_PREFIX}compilerlibs provider. > compilerlibs is compiler runtime, do we not have crtstuff and libgcc

Re: [OE-core] [PATCH v2] python3{,-native}: update to 3.7.0

> Am 10.09.2018 um 11:35 schrieb Alexander Kanavin : > > Large parts of dnf and friends have been rewritten in c++. I have not > yet updated and reviewed that, that will happen in the next cycle. If I can prepare something for you - drop me a note. Otherwise - the perl-5.28 update ("." in

Re: [OE-core] [PATCH v2] python3{,-native}: update to 3.7.0

> Am 10.09.2018 um 11:35 schrieb Alexander Kanavin >: > > Large parts of dnf and friends have been rewritten in c++. I have not > yet updated and reviewed that, that will happen in the next cycle. If I can prepare something for you - drop me a note. Otherwise -

Re: [OE-core] [PATCH] tclibc: For newlib and baremetal disable some security features

On Mon, Sep 10, 2018 at 5:44 AM Nathan Rossi wrote: > > With GCCPIE being enabled by default with security_flags.inc the > compiler will by default attempt to compile and link programs as PIE. > The targets that use newlib and baremetal in general do not support PIE > or are otherwise unable to

Re: [OE-core] [meta-oe][PATCH v2] minidlna: restore & fix recipe

this should be in meta-multmedia layer. On Mon, Sep 10, 2018 at 8:15 AM Baptiste Durand wrote: > > Restore minidlna recipe and bump it to v1.2.1 > > Signed-off-by: Baptiste Durand > --- > .../recipes-multimedia/minidlna/minidlna.inc | 41 +++ >

Re: [OE-core] [PATCH] libgloss_3.0.0.bb: Fix up mv pattern to include libnosys

On Mon, Sep 10, 2018 at 5:43 AM Nathan Rossi wrote: > > When installing libgloss libraries handle the ${TARGET_SYS}/lib contents > so that it is placed in ${libdir} instead of ${libdir}/lib. This > resolves a packaging QA issue. > > ERROR: libgloss-3.0.0-r0 do_package: QA Issue: libgloss: >

[OE-core] [meta-oe][PATCH v2] minidlna: restore & fix recipe

Restore minidlna recipe and bump it to v1.2.1 Signed-off-by: Baptiste Durand --- .../recipes-multimedia/minidlna/minidlna.inc | 41 +++ .../0001-Update-Gettext-version.patch | 34 +++ .../minidlna/minidlna_1.2.1.bb| 4 ++ 3 files changed, 79

Re: [OE-core] [PATCH 2/4] python3: remove redundant patch

On Mon, Sep 10, 2018 at 6:31 AM Ross Burton wrote: > > None of the Python invocations that this changes are actually called, and > there's no need to provide a HOSTPGEN variable when the recipe can just > override > PGEN directly. > patch is also substituting ./$(BUILDPYTHON) with

Re: [OE-core] [PATCH v2] python3{,-native}: update to 3.7.0

One thing to be aware of is that I've been fixing up Python's PGO support and there's a slew of patches in master-next and more just posted that this needs to be rebased on top of. Good news is that my patches remove two of the patches we've been carrying! Ross On 10 September 2018 at 17:36,

Re: [OE-core] [PATCH v2] python3{,-native}: update to 3.7.0

If you want to sort the perl situation, I guess this is not a bad starting point: http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=akanavin/perl-sanity Alex 2018-09-10 18:36 GMT+02:00 Jens Rehsack : > > > Am 10.09.2018 um 11:35 schrieb Alexander Kanavin : > > Large parts of dnf and

[OE-core] ✗ patchtest: failure for "python3: fix ftplib with TLS 1..." and 3 more

== Series Details == Series: "python3: fix ftplib with TLS 1..." and 3 more Revision: 1 URL : https://patchwork.openembedded.org/series/13994/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been

Re: [OE-core] [PATCH 0/3] Misc fixes

On Mon, Sep 10, 2018 at 4:14 AM Burton, Ross wrote: > > I never saw these on the list, just the cover letter. > > So the serf change introduces three patches, two of which are > backports with nice descriptions but one (0003-gen_def.patch) doesn't > have a description, upstream-status, or

Re: [OE-core] [PATCH 2/4] python3: remove redundant patch

On 10 September 2018 at 17:12, Khem Raj wrote: > patch is also substituting ./$(BUILDPYTHON) with $(HOSTPYTHON), how is > that taken care of ? > maybe try to a build where hostarch != targetarch might catch the > problem. If its handled in other > ways then its probably good riddance. Target

Re: [OE-core] [PATCH] ghostscript: fix CVE-2018-15908 & CVE-2018-15909 & CVE-2018-15910 & CVE-2018-15911

On 09/10/2018 12:21 AM, Hongxu Jia wrote: > Signed-off-by: Hongxu Jia > --- > ...Bug-699665-memory-corruption-in-aesdecode.patch | 56 + > ...Handle-LockDistillerParams-not-being-a-bo.patch | 53 + > ...660-shading_param-incomplete-type-checkin.patch | 91 >

Re: [OE-core] [PATCH 2/4] python3: remove redundant patch

Line-by-line breakdown of the patch: > diff --git a/Makefile.pre.in b/Makefile.pre.in > index 144c1f8629..f252ac2417 100644 > --- a/Makefile.pre.in > +++ b/Makefile.pre.in > @@ -223,6 +223,7 @@ LIBOBJS= @LIBOBJS@ > PYTHON= python$(EXE) > BUILDPYTHON= python$(BUILDEXE) > +HOSTPYTHON=

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

All, The triage team meets weekly and does its best to handle the bugs reported into the bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the

Re: [OE-core] [PATCH 2/4] python3: remove redundant patch

Thanks for the clarification. It seems to be fine then On Mon, Sep 10, 2018 at 9:24 AM Burton, Ross wrote: > > Line-by-line breakdown of the patch: > > > diff --git a/Makefile.pre.in b/Makefile.pre.in > > index 144c1f8629..f252ac2417 100644 > > --- a/Makefile.pre.in > > +++ b/Makefile.pre.in > >

Re: [OE-core] [RFC PATCH 1/6] openssl: rename openssl 1.0.x to openssl10 and make openssl 1.1.x the default version

On Wed, Sep 5, 2018 at 8:55 AM, Martin Jansa wrote: > https://wiki.debian.org/OpenSSL-1.1 says it will cause runtime bugs like > segmentation faults or just misbehaving applications. > > On Wed, Sep 5, 2018 at 5:45 PM Andre McCurdy wrote: >> >> On Wed, Sep 5, 2018 at 8:15 AM, Khem Raj wrote: >>

Re: [OE-core] [RFC PATCH 1/6] openssl: rename openssl 1.0.x to openssl10 and make openssl 1.1.x the default version

we are good with fixes in master-next On Mon, Sep 10, 2018 at 10:54 AM Andre McCurdy wrote: > > On Wed, Sep 5, 2018 at 8:55 AM, Martin Jansa wrote: > > https://wiki.debian.org/OpenSSL-1.1 says it will cause runtime bugs like > > segmentation faults or just misbehaving applications. > > > > On

Re: [OE-core] [PATCH v2] python3{,-native}: update to 3.7.0

> Am 10.09.2018 um 11:35 schrieb Alexander Kanavin >: > > Large parts of dnf and friends have been rewritten in c++. I have not > yet updated and reviewed that, that will happen in the next cycle. If I can prepare something for you - drop me a note. Otherwise -

Re: [OE-core] [PATCH v2] python3{,-native}: update to 3.7.0

Hey Jens, The compilation log for python3-native still shows that it didn't build the uuid module Python build finished successfully! The necessary bits to build these optional modules were not found: _uuid Please look at my previous reply to find how this can be solved (its likely a

Re: [OE-core] [meta-oe][PATCH v2] minidlna: restore & fix recipe

And don't use tag name in SRCREV, use git SHA, so that bitbake fetcher doesn't need to access the git repository every time it parses the recipe. On Mon, Sep 10, 2018 at 5:49 PM Khem Raj wrote: > this should be in meta-multmedia layer. > On Mon, Sep 10, 2018 at 8:15 AM Baptiste Durand > wrote:

Re: [OE-core] python test files installed in image on purpose?

Hey Andrew, I seem to remember some of them were required, both unittest and and sqlite3-tests can be removed from the python-modules package, as for the others, you would need to remove them at do_install() , and I would not mind making it optional. Cheers, Alejandro On 09/07/2018

Re: [OE-core] [PATCH v2] python3{,-native}: update to 3.7.0

Hey Alejandro, I fixed that for cross-compile only, since I would need add a patch and a dependency python3-native for one thing: calculate uuids. When you can explain to me why the python-native needs that, I'll change that from -target & nativesdk to all. From my point of view it's not a

[OE-core] [PATCH v3] kernel.bbclass: do not deploy fitImage; kernel-fitimage.bbclass does that.

kernel-fitimage.bbclass replaces an occurance of "fitImage" in KERNEL_IMAGETYPE_FOR_MAKE by an image type that is buildable for the architecture (such as zImage). The kernel-fitimage.bbclass packs that image as sub-image in a flattened image tree image (fitImage) and deploys this fitImage along

Re: [OE-core] [PATCH v2] python3{,-native}: update to 3.7.0

Hey Jens, As I explained before, when you create a manifest for python (target), it uses the native build as base (it literally runs the native python that was just built), it is assumed its the same version as target and contains all the modules provided by upstream, otherwise the missing

Re: [OE-core] [PATCH] ghostscript: fix CVE-2018-15908 & CVE-2018-15909 & CVE-2018-15910 & CVE-2018-15911

On 2018年09月10日 23:16, akuster808 wrote: Thank you for the fixes. Is updating to the  9.24 release an option? I believe there even are more vulnerabilities being addressed within that release. I am afraid it is code freeze, even though upgrading it, it could not be merged to 2.6 //Hongxu -

Re: [OE-core] [PATCH 1/1] autotools: do more cleanup when in do_configure

On 09/10/2018 06:24 PM, Burton, Ross wrote: On 10 September 2018 at 11:02, Chen Qi wrote: I met the following error when compiling some projects. | configure: error: `LDFLAGS' has changed since the previous run: | configure: former value: `-Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed' |

Re: [OE-core] [PATCH V2] bind: patch for CVE-2018-5740

Please ignore this patch,  I just noticed that Ross have fix Upstream-Status, and merge to master-next.  Thanks. On 09/11/2018 09:23 AM, changqing...@windriver.com wrote: From: Changqing Li Signed-off-by: Changqing Li --- .../bind/bind/CVE-2018-5740.patch | 72

[OE-core] [PATCH V2] bind: patch for CVE-2018-5740

From: Changqing Li Signed-off-by: Changqing Li --- .../bind/bind/CVE-2018-5740.patch | 72 ++ meta/recipes-connectivity/bind/bind_9.11.4.bb | 1 + 2 files changed, 73 insertions(+) create mode 100644

Re: [OE-core] [oe-core][PATCH] linux-yocto-rt: Add paravirt_kvm support for qemux86-64

On 2018-09-09 6:44 AM, Hongzhi.Song wrote: This feature includes paravirtualized KVM guest support, including KVMCLOCK for enhancing clock accuracy of guest OS. This is fine with me. I'll pull it into my queue. I expect my next pull request to be on Wednesday. Bruce Signed-off-by: He Zhe