[OE-core] [PATCH 1/1] lib/oe/package_manager.py: Fix extract for ipk and deb

From: Mariano Lopez With the move to use lists instead of strings in subprocess calls, package extraction was broken for ipk and deb. This fixes this issue. Signed-off-by: Mariano Lopez --- meta/lib/oe/package_manager.py | 6 +-

[OE-core] [PATCH 2/2] oeqa/utils/qemurunner.py: Be sure to stop qemu-system

From: Mariano Lopez When runqemu fails, qemu-system process would keep running and won't be killed, setpgrp() was used when runqemu was a shell script but it seems it doesn't work always with python. This would kill qemu-system explicity and to avoid leaving it

[OE-core] [PATCH 1/2] oeqa/utils/qemurunner.py: Add missing sys module

From: Mariano Lopez This adds the missing sys module used by the child process to exit. It seems the exception was cached in testimage and selftest. It seems nobody noticed this because the module is only used for sys.exit(). Signed-off-by: Mariano Lopez

[OE-core] [PATCH 0/2] Be sure to kill qemu-system on testimage

From: Mariano Lopez With refactor of runqemu to use python instead of shel scripting, the qemu-system process keeps running if runqemu fails. This series will fix this and will terminate qemu-system explicity. The following changes since commit

Re: [OE-core] [PATCH 2/2] glibc: Upgrade to 2.25

On Fri, 2017-01-13 at 10:52 -0800, Khem Raj wrote: > > I have sent a patchset with IFUNC change reverted for now until its > fixed. Yeah, I saw that.  But in light of recent developments it seems like it might be better to revert the earlier NPTL patch that apparently introduced the real

[OE-core] [PATCH V3] python3-docutils: upgrade to 0.13.1

Changed document date field and roman.py notes https://fossies.org/diffs/docutils/0.12_vs_0.13.1/COPYING.txt-diff.html Signed-off-by: Edwin Plauchu --- .../python/{python3-docutils_0.12.bb => python3-docutils_0.13.1.bb} | 6 +++--- 1 file changed, 3

[OE-core] [PATCH] openssl: Use linux-aarch64 target for aarch64

aarch64 target was being configured for linux-generic64 but openssl has linux-aarch64 target. Change to use linux-aarch64 as default. Signed-off-by: Fabio Berton --- meta/recipes-connectivity/openssl/openssl.inc | 2 +- 1 file changed, 1 insertion(+), 1

Re: [OE-core] [PATCH V2] python3-docutils: upgrade to 0.13.1

On 1/13/17 11:32 AM, Patrick Ohly wrote: > On Fri, 2017-01-13 at 12:13 -0600, Edwin Plauchu wrote: >> Changed document date field and several notes about folders > > Perhaps now would be a good time to start using beginline/endline > parameters? > may be it really depends on the change and I

Re: [OE-core] [PATCH V2] python3-docutils: upgrade to 0.13.1

On Fri, 2017-01-13 at 12:13 -0600, Edwin Plauchu wrote: > Changed document date field and several notes about folders Perhaps now would be a good time to start using beginline/endline parameters? -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although

Re: [OE-core] [PATCH 2/2] glibc: Upgrade to 2.25

On 1/13/17 10:45 AM, Phil Blundell wrote: > On Wed, 2017-01-11 at 12:19 +, Burton, Ross wrote: >> The gdk-pixbuf link does use -lpthread, is this saying that libpng >> should be linked against pthread too? I can replicate on demand if >> you have any suggestions. > > So, amusingly, it now

Re: [OE-core] [PATCH 2/2] glibc: Upgrade to 2.25

On Wed, 2017-01-11 at 12:19 +, Burton, Ross wrote: > > > The gdk-pixbuf link does use -lpthread, is this saying that libpng should be linked against pthread too?  I can replicate on demand if you have any suggestions. > > So, amusingly, it now appears that libpng in pthread-using programs

Re: [OE-core] [PATCH V2] python3-docutils: upgrade to 0.13.1

On 1/13/17 10:13 AM, Edwin Plauchu wrote: > Changed document date field and several notes about folders sorry to be picking on it again, it seems too vague still. perhaps you can just diff the two license files are add the diff to commit msg -- ___

[OE-core] [PATCH V2] python3-docutils: upgrade to 0.13.1

Changed document date field and several notes about folders Signed-off-by: Edwin Plauchu --- .../python/{python3-docutils_0.12.bb => python3-docutils_0.13.1.bb} | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) rename

Re: [OE-core] [PATCH] python3-docutils: upgrade to 0.13.1

On 1/13/17 9:53 AM, Edwin Plauchu wrote: > -LIC_FILES_CHKSUM = "file://COPYING.txt;md5=a722fbdc20347db7b69223594dd54574" > +LIC_FILES_CHKSUM = "file://COPYING.txt;md5=7a4646907ab9083c826280b19e103106" whatever is causign this change in checksums, document that in commit message --

[OE-core] [PATCH] python3-docutils: upgrade to 0.13.1

Signed-off-by: Edwin Plauchu --- .../python/{python3-docutils_0.12.bb => python3-docutils_0.13.1.bb} | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) rename meta/recipes-devtools/python/{python3-docutils_0.12.bb => python3-docutils_0.13.1.bb}

[OE-core] [PATCH v4] kernel-module-split: Append KERNEL_VERSION string to kernel module name

From: Ola Redell The KERNEL_VERSION string is added to kernel module package names in order to make the kernel modules for different kernel versions distinct packages instead of different versions of the same package. With this change, when a new kernel is installed

Re: [OE-core] [PATCH 00/80] Consolidated pull

On 1/13/17 6:25 AM, Burton, Ross wrote: > > On 13 January 2017 at 14:19, Bruce Ashfield > wrote: > > I'm not much good with musl unfortunately, but honestly, I'm > wondering how long we > can keep this out with relatively

Re: [OE-core] [PATCH] zlib: update SRC_URI to fix fetching

On 01/13/2017 05:36 PM, Joshua Lock wrote: Running checkpkg on the autobuilders won't really help as the autobuilders rely on the bitbake invocation returning a non-zero exit code to determine whether to mark the build step as failed, and that's not the case when checkpkg doesn't find an update

Re: [OE-core] [PATCH] zlib: update SRC_URI to fix fetching

On Fri, 2017-01-13 at 16:18 +0200, Alexander Kanavin wrote: > On 01/13/2017 03:51 PM, Lock, Joshua G wrote: > > > Noted, thanks. Do we maintain a list of things we'd like people to > > check, and how to do it, when making updates to recipes? > > I don't think there's such a list, perhaps we

Re: [OE-core] [PATCH 00/80] Consolidated pull

On 13 January 2017 at 15:09, Burton, Ross wrote: > On 13 January 2017 at 13:00, Ross Burton wrote: > >> Patrick Ohly (8): >> recipes: anonymous functions with priorities >> build.py: add preceedtask() API >> runqueue.py:

Re: [OE-core] [PATCH 00/80] Consolidated pull

On 13 January 2017 at 13:00, Ross Burton wrote: > Patrick Ohly (8): > recipes: anonymous functions with priorities > build.py: add preceedtask() API > runqueue.py: alternative rm_work scheduler > gcc-source.inc: cleanly disable do_rm_work >

Re: [OE-core] [PATCH 4/5] lttng-tools: upgrade to 2.9.3

Nathan Lynch writes: > "Burton, Ross" writes: > >> This upgrade is failing on the autobuilders: >> >> DEBUG: Executing shell function do_install_ptest_base >> install: failed to access >>

Re: [OE-core] [PATCH 1/2] rm_work.bbclass: allow preserving additional content

Hello! Please ignored the 1/2 in the subject. There's just one patch for OE-core, the other one I had locally needs to go into meta-swupd. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in

[OE-core] [PATCH v2 0/3] rm_work enhancements

This is the OE-core side of the rm_work.bbclass enhancements. Depends on the corresponding bitbake patch series. See the OE-core "rm_work + pybootchart enhancements" mail thread for further information. Changes since v1: - now based on the (tenative!) bb.event.RecipeTaskPreProcess instead

[OE-core] [PATCH v2 2/3] rm_work_and_downloads.bbclass: more aggressively minimize disk usage

rm_work.bbclass never deletes downloaded files, even if they are not going to be needed again during the build. rm_work_and_downloads.bbclass is more aggressive in minimizing the used disk space during a build, but has other disadvantages: - sources required by different recipes need to be fetched

[OE-core] [PATCH v2 3/3] rm_work.bbclass: clean up sooner

Having do_rm_work depend on do_build had one major disadvantage: do_build depends on the do_build of other recipes, to ensure that runtime dependencies also get built. The effect is that when work on a recipe is complete and it could get cleaned up, do_rm_work still doesn't run because it waits

[OE-core] [PATCH v2 1/3] gcc-source.inc: cleanly disable do_rm_work

Using "deltask" assumes that do_rm_work has been added already, which won't be the case anymore in the upcoming improved rm_work.bbclass, because then an anonymous python method will add do_rm_work. Setting RM_WORK_EXCLUDE works with the current and upcoming rm_work.bbclass and is the API that is

Re: [OE-core] [PATCH 1/2] ccache: enable max size setup for ccache dir

On 13 January 2017 at 14:23, Yannick Gicquel wrote: > +def init_ccache(): > +# dummy python version > +return > + > +init_ccache() { > +if [ -n "${CCACHE}" ]; then > +${CCACHE} -M ${CCACHE_MAX_SIZE} > +fi > +} > + > +do_compile_prepend() { > +

Re: [OE-core] [PATCH 00/80] Consolidated pull

On 13 January 2017 at 14:32, Bruce Ashfield wrote: > oh, and is this one logged in bugzilla ? (or elsewhere, I don't care .. i > just want to have a look > at the proposed fix so I can start a musl build and see if I can fix > things in the background). > It's not in

Re: [OE-core] [PATCH 00/80] Consolidated pull

On Fri, Jan 13, 2017 at 9:25 AM, Burton, Ross wrote: > > On 13 January 2017 at 14:19, Bruce Ashfield > wrote: > >> I'm not much good with musl unfortunately, but honestly, I'm wondering >> how long we >> can keep this out with relatively few

Re: [OE-core] [PATCH 00/80] Consolidated pull

On Fri, Jan 13, 2017 at 9:25 AM, Burton, Ross wrote: > > On 13 January 2017 at 14:19, Bruce Ashfield > wrote: > >> I'm not much good with musl unfortunately, but honestly, I'm wondering >> how long we >> can keep this out with relatively few

Re: [OE-core] [PATCH 00/80] Consolidated pull

On 13 January 2017 at 14:19, Bruce Ashfield wrote: > I'm not much good with musl unfortunately, but honestly, I'm wondering how > long we > can keep this out with relatively few build issues. In tree, they'll get > more attention. > This is a greater problem - the

[OE-core] [PATCH 1/2] rm_work.bbclass: allow preserving additional content

By default, do_rm_work either skips recipes entirely (when listed in RM_WORK_EXCLUDE) or removes everything except for temp. In meta-swupd, virtual image recipes collaborate on producing update data for the base recipe. Tasks running in the base recipe need some information from the virtual

[OE-core] [PATCH 2/2] cmake.bbclass: enable usage of ccache

This allows ccache usage for recipes which inherit cmake.bbclass. Since cmake v3.4, it can be enabled using some "-D" options. Here below are some metrics while using it for webkitgtk recipe. (machine is a 4x core i7 @ 3.4GHz) $ bitbake -c fetchall webkitgtk $ time bitbake webkitgtk real

[OE-core] [PATCH 1/2] ccache: enable max size setup for ccache dir

ccache directories are limited to 1G by default. This patch enables the configuration of their limits, and as default location is TMPDIR, it proposes a size limit to "0" (unlimited). The setup can be overloaded in local.conf by setting CCACHE_MAX_SIZE to a custom value if needed. Signed-off-by:

Re: [OE-core] [PATCH 00/80] Consolidated pull

On Fri, Jan 13, 2017 at 9:16 AM, Jussi Kukkonen wrote: > On 13 January 2017 at 15:39, Bruce Ashfield > wrote: > > > > > > > > On Fri, Jan 13, 2017 at 8:00 AM, Ross Burton > wrote: > >> > >> Hi, > >> > >> Another

Re: [OE-core] [PATCH] zlib: update SRC_URI to fix fetching

On 01/13/2017 03:51 PM, Lock, Joshua G wrote: Noted, thanks. Do we maintain a list of things we'd like people to check, and how to do it, when making updates to recipes? I don't think there's such a list, perhaps we should make one and place it in patch guidelines wiki. checkpkg isn't

Re: [OE-core] [PATCH 00/80] Consolidated pull

On 13 January 2017 at 15:39, Bruce Ashfield wrote: > > > > On Fri, Jan 13, 2017 at 8:00 AM, Ross Burton wrote: >> >> Hi, >> >> Another consolidated pull. Last run on the AB was mostly green: >> - byacc on beaglebone-lsb failed (upgrade removed)

Re: [OE-core] [PATCH] zlib: update SRC_URI to fix fetching

> On Fri, 2017-01-13 at 15:00 +0200, Alexander Kanavin wrote: > On 01/09/2017 02:56 PM, Alexander Kanavin wrote: > > On 01/05/2017 06:34 PM, Joshua Lock wrote: > > > Upstream have removed the file from zlib.net as a new version has > > > been released, switch to fetching from the official

Re: [OE-core] [PATCH 00/80] Consolidated pull

On Fri, Jan 13, 2017 at 8:00 AM, Ross Burton wrote: > Hi, > > Another consolidated pull. Last run on the AB was mostly green: > - byacc on beaglebone-lsb failed (upgrade removed) > - checkuri failed (transient, works now) > - selftest failed (fixed in branch, tests work

Re: [OE-core] [PATCH v2 1/7] image-live-artifacts: Add support for creating image artifacts only

On Fri, Jan 13, 2017 at 12:34 AM, Alejandro Hernandez < alejandro.hernan...@linux.intel.com> wrote: [snip] > > Not as far as I know, but so that would work when building something AND > the artifacts, but what if you want to build the artifacts only?, you would > have to build everything else as

Re: [OE-core] [PATCH 00/80] Consolidated pull

On 13 January 2017 at 13:00, Ross Burton wrote: > Markus Lehtonen (10): > oeqa.utils.metadata: re-organise host distro information > oeqa.utils.metadata: re-organise distro information > oeqa.utils.metadata: drop 'unknown' git data elements >

[OE-core] [PATCH v2 09/10] oeqa.utils.metadata: allow storing any bitbake config variables

Make it possible to store any bitbake config variables in the metadata. Config values will be stored under a new config element in the xml report: qemux86 The value of MACHINE is moved there instead of having a dedicated element. [YOCTO #10590] Signed-off-by: Markus Lehtonen

[OE-core] [PATCH v2 10/10] oeqa.utils.metadata: include BB_NUMBER_THREADS and PARALLEL_MAKE

Inlude values of BB_NUMBER_THREADS and PARALLEL_MAKE in the metadata. [YOCTO #10590] Signed-off-by: Markus Lehtonen --- meta/lib/oeqa/utils/metadata.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/lib/oeqa/utils/metadata.py

[OE-core] [PATCH v2 06/10] oeqa.utils.metadata: add commit count information

Makes it easier to put the commits into a timeline. [YOCTO #10590] Signed-off-by: Markus Lehtonen --- meta/lib/oeqa/utils/metadata.py | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/meta/lib/oeqa/utils/metadata.py

[OE-core] [PATCH v2 08/10] oeqa.utils.metadata: add bitbake revision information

[YOCTO #10590] Signed-off-by: Markus Lehtonen --- meta/lib/oeqa/utils/metadata.py | 32 +++- 1 file changed, 19 insertions(+), 13 deletions(-) diff --git a/meta/lib/oeqa/utils/metadata.py b/meta/lib/oeqa/utils/metadata.py index

[OE-core] [PATCH v2 07/10] oeqa.utils.metadata: have layer name as an attribute in xml

Have the layer name as an attribute instead of of the name of the element itself. That is, have instead of . A bit better XML design. [YOCTO #10590] Signed-off-by: Markus Lehtonen --- meta/lib/oeqa/utils/metadata.py | 8 +--- 1 file changed, 5

[OE-core] [PATCH v2 02/10] oeqa.utils.metadata: re-organise distro information

Use the same format, based on /etc/os-release, as for host distro information. [YOCTO #10590] Signed-off-by: Markus Lehtonen --- meta/lib/oeqa/utils/metadata.py | 17 ++--- scripts/oe-selftest | 4 ++-- 2 files changed, 12

[OE-core] [PATCH v2 05/10] oeqa.utils.metadata: rename 'revision' to 'commit'

Revision is a bit vague and could point to a tag, for example. Git commit objects are unambiguous and persistent so be explicit that the element should contain git commit hash. [YOCTO #10590] Signed-off-by: Markus Lehtonen --- meta/lib/oeqa/utils/metadata.py |

[OE-core] [PATCH v2 04/10] oeqa.utils.metadata: fix retrieval of git branch and revision

Always return a valid branch name, or, '(nobranch)' if the current HEAD is detached. Also, always return the hash of the commit object that HEAD is pointing to. Previous code returned an incorrect branch name (or crashed) e.g. in the case of detached HEAD. [YOCTO #10590] Signed-off-by: Markus

[OE-core] [PATCH v2 03/10] oeqa.utils.metadata: drop 'unknown' git data elements

It's better just to not have the xml elements than to have elements with faux data. One could have git branch named 'unknown', for example. [YOCTO #10590] Signed-off-by: Markus Lehtonen --- meta/lib/oeqa/utils/metadata.py | 7 +++ scripts/oe-selftest

[OE-core] [PATCH v2 00/10] oeqa.utils.metadata: update xml schema

Changes since v1: - import of git module moved back to function level - two new patches regarding config variables The following changes since commit acce512a0b85853b5acf2ef07e4163a3b4f33a98: selftest/devtool: update test to work with new mtd-utils (2017-01-09 13:34:32 +) are available

[OE-core] [PATCH v2 01/10] oeqa.utils.metadata: re-organise host distro information

Put all host distro data under one element. In addition take the data directly from /etc/os-release instead of the "lsb API". The /etc/os-release file is virtually ubiquitous, now, and using its field names and values provides a more standardized and extensible format. [YOCTO #10590]

Re: [OE-core] [PATCH] zlib: update SRC_URI to fix fetching

On 01/09/2017 02:56 PM, Alexander Kanavin wrote: On 01/05/2017 06:34 PM, Joshua Lock wrote: Upstream have removed the file from zlib.net as a new version has been released, switch to fetching from the official sourceforge mirror. [YOCTO #10879] If a new version has been released, you should

[OE-core] [PATCH 00/80] Consolidated pull

Hi, Another consolidated pull. Last run on the AB was mostly green: - byacc on beaglebone-lsb failed (upgrade removed) - checkuri failed (transient, works now) - selftest failed (fixed in branch, tests work locally now) Ross The following changes since commit

[OE-core] [PATCH 1/4] libproxy: update to version 0.4.14

0.4.13 -> 0.4.14 Signed-off-by: Maxin B. John --- .../libproxy/{libproxy_0.4.13.bb => libproxy_0.4.14.bb} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-support/libproxy/{libproxy_0.4.13.bb => libproxy_0.4.14.bb} (88%) diff

[OE-core] [PATCH 3/4] netbase: upgrade to version 5.4

5.3 -> 5.4 Refreshed the following patch: a) netbase-add-rpcbind-as-an-alias-to-sunrpc.patch Signed-off-by: Maxin B. John --- ...netbase-add-rpcbind-as-an-alias-to-sunrpc.patch | 24 +- .../netbase/{netbase_5.3.bb => netbase_5.4.bb} | 6 +++--- 2

[OE-core] [PATCH 2/4] mdadm: upgrade to version 4.0

3.4 -> 4.0 Removed the following upstreamed or backported patches: a) 0001-Fix-some-type-comparison-problems.patch b) 0001-Fix-typo-in-comparision.patch c) 0001-mdadm.h-bswap-is-already-defined-in-uclibc.patch d) 0001-raid6check-Fix-if-else-indentation.patch e)

[OE-core] [PATCH 4/4] harfbuzz: upgrade to 1.4.1

1.3.4 -> 1.4.1 Signed-off-by: Maxin B. John --- .../harfbuzz/{harfbuzz_1.3.4.bb => harfbuzz_1.4.1.bb} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-graphics/harfbuzz/{harfbuzz_1.3.4.bb => harfbuzz_1.4.1.bb} (88%) diff

Re: [OE-core] [PATCH v3] kernel-module-split: Append KERNEL_VERSION string to kernel module name

On 01/12/2017 02:44 PM, Bruce Ashfield wrote: Interesting. I think we've probably fallen off the radar of the casual reader that may have more bitbake knowledge to explain why the virtual package (kernel-modules) provides works with the same name and different versions, while a package

Re: [OE-core] [PATCH] recipes-test: exclude recipes from world target

On 9 January 2017 at 17:49, wrote: > These recipes should be excluded from target 'world' because these are > just intended to be used internally by oe-selftest (devtool, recipetool, > etc.) > You failed to update the reference files for after the

Re: [OE-core] [PATCH 6/7] byacc: upgrade to 20161202

On 13 January 2017 at 10:57, ChenQi wrote: > I've fixed the problem and updated the remote branch. > > Thanks Chen! Ross -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org

Re: [OE-core] [PATCH 6/7] byacc: upgrade to 20161202

On 01/13/2017 07:18 AM, Burton, Ross wrote: On 26 December 2016 at 08:10, Chen Qi > wrote: Signed-off-by: Chen Qi > I haven't yet looked into why it could be happening, but it

Re: [OE-core] [PATCH 1/3] piglit: Package tests in compressed form as well

On Mon, Dec 12, 2016 at 2:35 PM, Jussi Kukkonen wrote: > Modify packaging so that generated tests are available in two forms: > * piglit-generated-tests contains the tests as they are now (1.5GB > when installed) > * piglit-generated-tests-compressed contains a tar.gz

[OE-core] [morty] Please include the binutils-2.27 alignment frags for aarch64

Could this oe-core master commit be included in the "morty" branch please: f6f87019073d4f3caa7766aca89faa6781690fba "binutils-2.27.inc: Fix alignment frags for aarch64" Without this patch, arm-trusted-firmware (apparently a requirement to get arm64 machines to boot these days) fails to build