Re: [OE-core] [AUH] u-boot-mkimage: upgrading to 2018.03 FAILED

On 03/19/2018 12:53 PM, Marek Vasut wrote: Try building with UBOOT_MACHINE = "qemu-x86_defconfig" . | unable to execute 'swig': No such file or directory | error: command 'swig' failed with exit status 1 Alex -- ___ Openembedded-core mailing list

Re: [OE-core] [AUH] u-boot-mkimage: upgrading to 2018.03 FAILED

On 03/19/2018 09:50 AM, Alexander Kanavin wrote: > On 03/17/2018 06:27 PM, Marek Vasut wrote: > >>> You are receiving this email because you are the maintainer >>> of *u-boot-mkimage* recipe and this is to let you know that the >>> automatic attempt >>> to upgrade the recipe to *2018.03* has

Re: [OE-core] [AUH] u-boot-mkimage: upgrading to 2018.03 FAILED

On 03/19/2018 11:55 AM, Marek Vasut wrote: I'm not sure how to solve it - perhaps you can simply take the email as a reminder to update the whole set on your machine manually? I was hoping the tool will take care of that, now that I've finally plucked all the extra patches out. You can

[OE-core] ✗ patchtest: failure for opkg-utils: use multithreaded xz when building packages

== Series Details == Series: opkg-utils: use multithreaded xz when building packages Revision: 1 URL : https://patchwork.openembedded.org/series/11449/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests

[OE-core] [PATCH] opkg-utils: use multithreaded xz when building packages

Signed-off-by: Ross Burton --- .../opkg-utils/opkg-utils/threaded-xz.patch| 18 ++ meta/recipes-devtools/opkg-utils/opkg-utils_0.3.6.bb | 1 + 2 files changed, 19 insertions(+) create mode 100644

Re: [OE-core] [AUH] u-boot-mkimage: upgrading to 2018.03 FAILED

On 03/19/2018 11:31 AM, Alexander Kanavin wrote: > On 03/19/2018 12:08 PM, Marek Vasut wrote: > I'm not sure how to solve it - perhaps you can simply take the > email as > a reminder to update the whole set on your machine manually? I was hoping the tool will take care of

Re: [OE-core] [PATCH V3] gcc: Do not use --with-linker-hash-style if LINKER_HASH_STYLE is empty

On 16 March 2018 at 21:43, Andre McCurdy wrote: > On Fri, Mar 16, 2018 at 2:41 PM, Khem Raj wrote: > > We allow to set LINKER_HASH_STYLE to be empty so this would fail > > since --with-linker-hash-style needs an argument and cant be empty > > > >

Re: [OE-core] [PATCH 3/5] x264: Use updated gnu-config artifacts

On 17 March 2018 at 03:40, Khem Raj wrote: > It is not using autoconf completely, therefore there > is no autoreconf happening, so when we depend on latest > gnu-config changes e.g. new architectures like riscv > the build does not see them and fails. > > Installing these

[OE-core] [PATCH] package-index: index also subdirectories when using rpm

Previously only the top-level index was created, which did not work if PACKAGE_FEED_ARCHS whitelisting (or explicitly listing architectures in dnf repo files by hand) was in use: https://lists.yoctoproject.org/pipermail/yocto/2018-March/040327.html

Re: [OE-core] [AUH] u-boot-mkimage: upgrading to 2018.03 FAILED

On 03/19/2018 12:08 PM, Marek Vasut wrote: I'm not sure how to solve it - perhaps you can simply take the email as a reminder to update the whole set on your machine manually? I was hoping the tool will take care of that, now that I've finally plucked all the extra patches out. You can

Re: [OE-core] [PATCH] glibc: fix upstream version check

On Mon, Mar 19, 2018 at 1:53 AM Alexander Kanavin < alexander.kana...@linux.intel.com> wrote: > On 03/17/2018 05:16 PM, Khem Raj wrote: > > On Sat, Mar 17, 2018 at 4:15 AM, Alexander Kanavin > > wrote: > >> Exclude x.y.90* pre-release versions in particular. >

[OE-core] [pyro][PATCH] qemu: fix memfd_create with glibc 2.27

From: Ross Burton glibc 2.27 has added memfd_create() but this conflicts with a copy in qemu, so take a patch from upstream to fix building with glibc 2.27. Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

[OE-core] [rocko][PATCH] qemu: fix memfd_create with glibc 2.27

From: Ross Burton glibc 2.27 has added memfd_create() but this conflicts with a copy in qemu, so take a patch from upstream to fix building with glibc 2.27. Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

[OE-core] [PATCH] libsolv: refresh the patches

fixes: WARNING: libsolv-0.6.33-r0 do_patch: Some of the context lines in patches were ignored. This can lead to incorrectly applied patches. The context lines in the patches can be updated with devtool: devtool modify devtool finish --force-patch-refresh Then the updated patches and the

[OE-core] [PATCH] Revert "lttng-tools: Upgrade 2.9.5 -> 2.10.2"

None of the test suite works, so something quite fundamental broke. [ YOCTO #12606 ] This reverts commit 406ea737f1ce5bb5fed46c8cbeb5c7c13bf3b8ad. Signed-off-by: Ross Burton --- .../lttng/{lttng-tools_2.10.2.bb => lttng-tools_2.9.5.bb} | 6 +++--- 1 file

[OE-core] [PATCH] cmake: upgrade 3.10.2 -> 3.10.3

,[ Changes in 3.10.3 ] | Brad King (1): | CMake 3.10.3 | | Craig Scott (1): | GoogleTest: Rename TIMEOUT parameter to avoid clash | | Sebastian Holtermann (1): | Autogen: Fix for the empty source file crash in 3.10.2 | | Tianhao Chai (1): | ccmake: fix status line

Re: [OE-core] [PATCH] ca-certificates: run postinst script only for -target package

Do you already have similar patch for nativesdk-shadow somewhere? One thing I've noticed with new set -e is that you get only one failure per run, which is expected. Just when I had 8 different update-alternatives call failing in busybox postinst (due to different defconfig we use) I would

[OE-core] Yocto Project Status WW12’18

Current Dev Position: YP 2.5 M3 final close out. Next Deadline: YP 2.5 M3 cut off was 2/19/18 *** FEATURE FREEZE for 2.5 has passed *** SWAT lead is currently Ross. SWAT team rotation: Armin -> Ross on March 23, 2018 SWAT team rotation: Ross -> Juro on March 30, 2018

[OE-core] [PATCH][rocko] lame: revert "lame: fix CVE-2017-13712"

I don't know how this made it in, but the backported patch most definitely fails to apply: ERROR: lame-3.99.5-r1 do_patch: Command Error: 'quilt --quiltrc /home/ak/development/poky/build-musl/tmp/work/core2-64-poky-linux-musl/lame/3.99.5-r1/recipe-sysroot-native/etc/quiltrc push' exited with 0

Re: [OE-core] [PATCH] libsolv: refresh the patches

On 03/19/2018 03:59 PM, Maxin B. John wrote: diff --git a/meta/recipes-extended/libsolv/libsolv/0002-Fixes-to-internal-fopencookie-implementation.patch b/meta/recipes-extended/libsolv/libsolv/0002-Fixes-to-internal-fopencookie-implementation.patch index efb4e3a..93b8cc9 100644 ---

[OE-core] [morty][PATCH] qemu: fix memfd_create with glibc 2.27

From: Ross Burton glibc 2.27 has added memfd_create() but this conflicts with a copy in qemu, so take a patch from upstream to fix building with glibc 2.27. Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

Re: [OE-core] [PATCH 3/5] x264: Use updated gnu-config artifacts

Thanks for the tip! On Mon, Mar 19, 2018 at 4:37 AM Burton, Ross wrote: > On 17 March 2018 at 03:40, Khem Raj wrote: > >> It is not using autoconf completely, therefore there >> is no autoreconf happening, so when we depend on latest >> gnu-config

Re: [OE-core] [PATCH] uninative: add variables to the whitelist so that it does not re-triger recipe parsing

> > On Fri, Mar 16, 2018 at 10:31 AM Cuero Bugot > > wrote: > > When uninative is activated (poky's default) internal datastore variables > > are modified (NATIVELSBSTRING and SSTATEPOSTUNPACKFUNCS) to enable uninative > > support. This is happening after

Re: [OE-core] [PATCH] uninative: add variables to the whitelist so that it does not re-triger recipe parsing

> > On Fri, Mar 16, 2018 at 10:31 AM Cuero Bugot > > wrote: > > When uninative is activated (poky's default) internal datastore variables > > are modified (NATIVELSBSTRING and SSTATEPOSTUNPACKFUNCS) to enable uninative > > support. This is happening after

Re: [OE-core] [PATCH v2] gstreamer: enable ptest support

Hi Ross, On 03/15/2018 01:03 AM, Burton, Ross wrote: > On 28 February 2018 at 02:51, Anuj Mittal > wrote: > > +diff --git a/Makefile.am b/Makefile.am > +index de057c4..42e90fe 100644 > +--- a/Makefile.am > b/Makefile.am

Re: [OE-core] [oe-core] system lock down in middle of build

On Mon, Mar 19, 2018 at 3:38 PM, Burton, Ross wrote: > On 19 March 2018 at 20:35, Rajath C S wrote: >> >> so i am workin gon yocto development on my PC as well as on my laptop. >> I have also worked on it on others systems, but the strange thing is

[OE-core] [PATCH] site/risc-v: Cache more variables to build libIDL

These variables force runtime tests during configure they are already cached for other architectures Signed-off-by: Khem Raj --- meta/site/riscv32-linux | 13 + meta/site/riscv64-linux | 8 2 files changed, 21 insertions(+) diff --git

Re: [OE-core] [AUH] u-boot-mkimage: upgrading to 2018.03 FAILED

On 03/19/2018 10:57 AM, Alexander Kanavin wrote: > On 03/19/2018 11:55 AM, Marek Vasut wrote: > >>> I'm not sure how to solve it - perhaps you can simply take the email as >>> a reminder to update the whole set on your machine manually? >> >> I was hoping the tool will take care of that, now that

Re: [OE-core] [AUH] linux-yocto: upgrading to 4.15.7 FAILED

On 2018-03-19 4:54 AM, Alexander Kanavin wrote: On 03/17/2018 11:32 PM, Bruce Ashfield wrote: How do I get linux-libc-headers and linux-yocto removed from the AUH list of recipes ? These follow a specific cadence, and shouldn't be included in these attempts. You ask me to blacklist them.

Re: [OE-core] Build Error

Are you mixing and matching branches between layers? Is your meta-openembedded on rocko or master? On Mon, Mar 19, 2018 at 3:44 PM, Rajath C S wrote: > Hi, > > 1. So while building the target i get the following error, > > bitbake core-image-sato > Loading cache: 100%

Re: [OE-core] [PATCH 3/5] x264: Use updated gnu-config artifacts

Huh, I was hoping that passing a path would just force it. Maybe we should stop the script being so "clever". Ross On 19 March 2018 at 17:48, Khem Raj wrote: > On Mon, Mar 19, 2018 at 10:23 AM, Burton, Ross > wrote: > > On 19 March 2018 at 16:54,

Re: [OE-core] Yocto Project Status WW12’18

On 03/19/2018 08:45 AM, Jordan, Robin L wrote: > > Current Dev Position: YP 2.5 M3 final close out. > > Next Deadline: YP 2.5 M3 cut off was 2/19/18 > > *** FEATURE FREEZE for 2.5 has passed *** > >   > > SWAT lead is currently Ross. > > SWAT team rotation: Armin -> Ross on March 23, 2018 > >

[OE-core] Branch shifting [image-build]

What is the reason that we shift to a branch called rocko while installing poky? The reason I ask this is , I was getting an error named classes/.pypi inherit not found.. So I shifted the branch to master and ran bitbake and it doesn't show any errors. Will I have any problems later or is

[OE-core] Build Error

Hi, 1. So while building the target i get the following error, bitbake core-image-sato Loading cache: 100% |#| Time: 0:00:00 Loaded 1 entries from dependency cache. ERROR: ParseError

Re: [OE-core] [PATCH] glibc: fix upstream version check

On 03/19/2018 05:29 PM, Khem Raj wrote: It lists all tags regardless of branch and picks the highest. I think that does not work effectively for how glibc release works we should probably track the Release branch name and deduce version from there Glibc does tag their releases, so I'm

Re: [OE-core] [PATCH] glibc: fix upstream version check

On Mon, Mar 19, 2018 at 9:23 AM, Alexander Kanavin wrote: > On 03/19/2018 05:29 PM, Khem Raj wrote: >> >> It lists all tags regardless of branch and picks the highest. >> >> >> I think that does not work effectively for how glibc release works we >> should

Re: [OE-core] [PATCH v3] gstreamer: enable ptest support

So the problem is that the tests explicitly search the build tree for plugins (as they're testing the built plugins, not the system ones). This is easily solved by deleting bits from the makefile: --- a/tests/check/Makefile.am +++ b/tests/check/Makefile.am @@ -8,11 +8,7 @@ REGISTRY_ENVIRONMENT =

Re: [OE-core] [PATCH 3/5] x264: Use updated gnu-config artifacts

On Mon, Mar 19, 2018 at 4:36 AM, Burton, Ross wrote: > On 17 March 2018 at 03:40, Khem Raj wrote: >> >> It is not using autoconf completely, therefore there >> is no autoreconf happening, so when we depend on latest >> gnu-config changes e.g. new

Re: [OE-core] [PATCH] ca-certificates: run postinst script only for -target package

On 03/19/2018 05:32 PM, Martin Jansa wrote: Do you already have similar patch for nativesdk-shadow somewhere? Nope. Hopefully the maintainer of the shadow recipe can step in? It would be great if the output of postinst script could be extracted to separate file or the warning provided some

Re: [OE-core] [PATCH v3] gstreamer: enable ptest support

You're missing a dependency on make in PN-ptest, but installing that results in about 20% of the tests failing. Should they all work? Ross On 19 March 2018 at 06:49, Anuj Mittal wrote: > Make sure that the tests are packaged and can be executed > when ptest is enabled.

Re: [OE-core] [PATCH 3/5] x264: Use updated gnu-config artifacts

On 19 March 2018 at 16:54, Khem Raj wrote: > this only works if the system uses autotools > in full respect. x264 has a hand woven configure > but rely on other parts of autotools. So we have to > stay with proposed solution. > gnu-configize should be sufficiently dumb that

Re: [OE-core] [PATCH] glibc: fix upstream version check

On 03/19/2018 06:36 PM, Khem Raj wrote: that works too I guess if we have good enough filters to detect it. It seems there is more noise in tags than in branches, That's what UPSTREAM_CHECK_GITTAGREGEX is for. You can set it to filter precisely the tags you want. Alex --

Re: [OE-core] [oe-commits] [openembedded-core] 02/03: reproducible_build_simple.bbclass: simple environment for reproducible binaries

Hi Martin, thanks for your feedback. I will send to ML a new version of the patch within a day or two. The patch you mentioned (v2) had a few short-comings, hopefully fixed in the next one (currently being tested). Meanwhile, you may want to have a look at the recently updated wiki page (and it

Re: [OE-core] [PATCH 3/5] x264: Use updated gnu-config artifacts

On Mon, Mar 19, 2018 at 10:23 AM, Burton, Ross wrote: > On 19 March 2018 at 16:54, Khem Raj wrote: >> >> this only works if the system uses autotools >> in full respect. x264 has a hand woven configure >> but rely on other parts of autotools. So we have

Re: [OE-core] Need arm64/qemu help

On Mon, 19 Mar 2018, Alex Bennée wrote: Victor Kamensky writes: On Sun, 18 Mar 2018, Alex Bennée wrote: Victor Kamensky writes: Hi Folks, I am back from ELC and I am looking at this issue again. Alex Bennée from Linaro QEMU team reported

Re: [OE-core] Build Error

On Mon, Mar 19, 2018 at 4:05 PM, Rajath C S wrote: > I am not mixing and matching the branches. > > My meta-openembedded is on master branch. > The reason that it is on master branch is : I had not got > meta-openembedded when I cloned poky and later I cloned

[OE-core] [oe-core] system lock down in middle of build

Hi, so i am workin gon yocto development on my PC as well as on my laptop. I have also worked on it on others systems, but the strange thing is only on my PC & laptop the systems gets logged out automatically in the midst of target build. Is this a bug? PS: both my PC & laptop are of high-end

Re: [OE-core] Yocto Project Status WW12’18

On 19 March 2018 at 19:22, akuster808 wrote: > YP 2.5 M3 is in feature freeze. See status above. > > Does this include package updates? > Yes, upgrades count as features. > Do we have a place identified for new changes (2.6) while 2.5 stabilizes. > A formal place, no.

Re: [OE-core] [oe-core] system lock down in middle of build

On Tue, 2018-03-20 at 02:05 +0530, Rajath C S wrote: > Hi, > > so i am workin gon yocto development on my PC as well as on my > laptop. > I have also worked on it on others systems, but the strange thing is > only on my PC & laptop the systems gets logged out automatically in > the midst of

Re: [OE-core] Need arm64/qemu help

On Mon, 19 Mar 2018, Peter Maydell wrote: On 19 March 2018 at 17:46, Victor Kamensky wrote: In v2.11.1 of qemu, that we use, we already have b29fd33db578decacd14f34933b29aece3e7c25e. Previous testing and collected log was done with it present. But my understanding that

Re: [OE-core] [PATCHv3] iputils: add PACKAGECONFIG for libidn and disable it by default

On Sat, Mar 17, 2018 at 4:26 AM, Martin Jansa wrote: > * it got enabled by default, but without the dependency on libidn in: > commit 5997981fa2c22609a88b8cbb595dbf7758b2f7c2 > Author: Alexander Kanavin > AuthorDate: Thu Feb 1

Re: [OE-core] Branch shifting [image-build]

On Mon, Mar 19, 2018 at 12:29 PM Rajath C S wrote: > What is the reason that we shift to a branch called rocko while installing > poky? > The reason I ask this is , I was getting an error named classes/.pypi > inherit not found.. So I shifted the branch to master and

Re: [OE-core] [oe-core] system lock down in middle of build

Depends on whether it's literally logging out, or rebooting. Neither of which would be caused by Yocto directly. If it is logging out then that is most likely the kernels out-of-memory handler killing your entire X session to get some memory back. Turn down the parallelisation options, or buy

[OE-core] [PATCH] xserver-xorg: import distro patch to use modesetting driver on newer hardware

Debian and Fedora both carry this patch, and the xf86-video-modesetting driver seems better on recent hardware. As an example, on a NUC6CAYS, the x11perf -aa10text and -rgb10text tests see around a 20x increase. [YOCTO #12019] [YOCTO #12390] Signed-off-by: California Sullivan

[OE-core] [PATCH] tiff: Security fixes

Fix CVE-2017-99935, CVE-2017-18013, CVE-2018-5784 References: https://nvd.nist.gov/vuln/detail/CVE-2017-9935 https://nvd.nist.gov/vuln/detail/CVE-2017-18013 https://nvd.nist.gov/vuln/detail/CVE-2018-5784 Patches from: CVE-2017-9935:

[OE-core] [PATCH V2] site/risc-v: Cache common variables to build libIDL

These variables force runtime tests during configure they are already cached for other architectures Signed-off-by: Khem Raj --- Changes from v1 -> v2: - Drop libIDL specific setting since they need to be in meta-gnome meta/site/riscv32-linux | 10 ++

[OE-core] [PATCH] glibc-2.27: Update to bring in 2.27 bug fixes since release

Here is full list of fixes https://sourceware.org/git/?p=glibc.git;a=shortlog;h=df3ff4e49d4ee3cbbdaeb0b1cb5dc2344c08be98;hp=23158b08a0908f381459f273a984c6fd328363cb Signed-off-by: Khem Raj --- meta/recipes-core/glibc/cross-localedef-native_2.27.bb | 2 +-

Re: [OE-core] Need arm64/qemu help

On Mon, 19 Mar 2018, Alex Bennée wrote: Peter Maydell writes: On 19 March 2018 at 17:46, Victor Kamensky wrote: In v2.11.1 of qemu, that we use, we already have b29fd33db578decacd14f34933b29aece3e7c25e. Previous testing and collected log was

Re: [OE-core] Need arm64/qemu help

On Mon, 19 Mar 2018, Richard Henderson wrote: On 03/20/2018 07:24 AM, Victor Kamensky wrote: target/arm/translate-a64.c:handle_sys() is setting    s->base.is_jmp = DISAS_UPDATE; which it thinks will end the TB, specifically because system register writes might do things like unmask

[OE-core] [PATCH 0/3] Package upgrades

From: Denys Dmytriyenko Upgrades for lzip, hdparm and lz4. The following changes since commit c94271d87d16323f920891344642f76dfb3c994f: buildperf: measure the size of core-image-sato rootfs (2018-03-16 03:42:03 -0700) are available in the git repository at:

[OE-core] [PATCH 1/3] lzip: upgrade 1.19 -> 1.20

From: Denys Dmytriyenko Signed-off-by: Denys Dmytriyenko --- meta/recipes-extended/lzip/{lzip_1.19.bb => lzip_1.20.bb} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-extended/lzip/{lzip_1.19.bb => lzip_1.20.bb} (88%) diff --git

[OE-core] [PATCH 2/3] hdparm: upgrade 9.53 -> 9.55

From: Denys Dmytriyenko Signed-off-by: Denys Dmytriyenko --- meta/recipes-extended/hdparm/{hdparm_9.53.bb => hdparm_9.55.bb} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-extended/hdparm/{hdparm_9.53.bb => hdparm_9.55.bb} (90%) diff

[OE-core] [PATCH 3/3] lz4: upgrade 1.7.4 -> 1.8.1.2

From: Denys Dmytriyenko 0001-tests-Makefile-don-t-use-LIBDIR-as-variable.patch accepted upstream. License-Update: rephrased clarification regarding lib/ vs. programs/, tests/ and examples/ https://github.com/lz4/lz4/commit/97df1c9789cbc8a7891cadbd49ea5053574e2f72 Signed-off-by:

[OE-core] [PATCH v3] gstreamer: enable ptest support

Make sure that the tests are packaged and can be executed when ptest is enabled. Also, remove build host specific references from Makefile. Signed-off-by: Anuj Mittal --- .../files/add-a-target-to-compile-tests.patch | 46 ++

[OE-core] Building keras and tensor flow on yocto

I have been trying to build keras and tensor flow packages on yocto's image that is poky but not able to do so. Until now I have tried looking for their respective recipe but couldn't find. What's the way to add keras and tensor flow packages to poky? --

Re: [OE-core] Need arm64/qemu help

On Sun, 18 Mar 2018, Alex Bennée wrote: Victor Kamensky writes: Hi Folks, I am back from ELC and I am looking at this issue again. Alex Bennée from Linaro QEMU team reported that he tried to reproduce the issue, even he went and build the same OE images - but he

Re: [OE-core] [PATCH] glibc: fix upstream version check

On 03/17/2018 05:16 PM, Khem Raj wrote: On Sat, Mar 17, 2018 at 4:15 AM, Alexander Kanavin wrote: Exclude x.y.90* pre-release versions in particular. Looks ok. So I guess it pokes at master branch right ? It lists all tags regardless of branch and picks

Re: [OE-core] [AUH] u-boot-mkimage: upgrading to 2018.03 FAILED

On 03/17/2018 06:27 PM, Marek Vasut wrote: You are receiving this email because you are the maintainer of *u-boot-mkimage* recipe and this is to let you know that the automatic attempt to upgrade the recipe to *2018.03* has Failed(do_compile). Detailed error information: do_compile failed

Re: [OE-core] [AUH] linux-yocto: upgrading to 4.15.7 FAILED

On 03/17/2018 11:32 PM, Bruce Ashfield wrote: How do I get linux-libc-headers and linux-yocto removed from the AUH list of recipes ? These follow a specific cadence, and shouldn't be included in these attempts. You ask me to blacklist them. Which I've just done :) Alex --

Re: [OE-core] [PATCH 1/3] systemd: upgrade to 237

On 03/19/2018 06:53 AM, ChenQi wrote: For autotools, 1) if the test framework of some package is a standalone set of scripts or it could be easily decoupled from Makefile, adding ptest support for such package is easy. 2) if the test framework of some package is coupled with Makefile, we