Re: [OE-core] [PATCH RFC 1/1] kernel.bbclass: Add kernel_version_sanity_check function

On 2016-08-24 5:56 PM, Burton, Ross wrote: Bruce, can you have a look at this? Wow. 8 days ago, and I admit that I didn't notice it go past. Yes, I'll have a look at this during the day on Thursday. Bruce Ross On 17 August 2016 at 06:25, California Sullivan

[OE-core] [PATCHv4 0/2] Add initial capability to check CVEs for recipes

From: Mariano Lopez This series add the cve-check-tool recipe, a tool used to identify potentially vulnerable software through version matching. It will check if a vulnerability has been addressed by a patch. Also add the new cve-check class that will add a task

[OE-core] [PATCHv4 1/2] cve-check-tool: Add recipe

From: Mariano Lopez cve-check-tool is a program for public CVEs checking. This tool also seek to determine if a vulnerability has been addressed by a patch. The recipe also includes the do_populate_cve_db task that will populate the database used by the tool.

[OE-core] [PATCHv4 2/2] cve-check.bbclass: Add class

From: Mariano Lopez This class adds a new task for all the recipes to use cve-check-tool in order to look for public CVEs affecting the packages generated. It is possible to use this class when building an image, building a recipe, or using the "world" or

Re: [OE-core] [PATCH 0/2] Toggle bind configure options

On 2016年08月25日 04:10, Burton, Ross wrote: On 24 August 2016 at 02:46, Kang Kai > wrote: I didn't see Wangxin's work to upgrade bind. So please comment the patches, and I will rebase them when the upgrade patch is merged. Looks

Re: [OE-core] [PATCH 1/1] bash: fix interpreter of ptest script

On 2016年08月25日 04:17, Burton, Ross wrote: On 24 August 2016 at 10:26, > wrote: The interpreter of bash ptest script tests/getopts5.sub is /local/bin/bash which is not suitable for oe. Use /bin/bash instead. Presumably this test

Re: [OE-core] [PATCH RFC 1/1] kernel.bbclass: Add kernel_version_sanity_check function

Bruce, can you have a look at this? Ross On 17 August 2016 at 06:25, California Sullivan < california.l.sulli...@intel.com> wrote: > The kernel being built should match what the recipe claims it is > building. This function ensures that happens for anyone using > LINUX_VERSION as they should.

Re: [OE-core] [oe-core][PATCH 1/1] useradd: do not delete users and groups during configure

On 24 August 2016 at 16:29, Randy MacLeod wrote: > I don't see this in oe-core/master[-next] yet. > It's in mut so assuming it doesn't break anything may be in master next week. Ross -- ___ Openembedded-core mailing list

[OE-core] [PATCH] linux-firmware: set a preferred provider for brcmfmac-sdio.bin

This recipe packages six alternatives to brcmfmac-sdio.bin but as they all have equal priority there is no determinism on what provider will be used if they are all installed. Arbitrarily select 4339 to be the highest priority. Signed-off-by: Ross Burton ---

[OE-core] Broadcom firmware

Every time I do an image build this is in the buildhistory: /lib/firmware/brcm/brcmfmac-sdio.bin changed symlink target from /lib/firmware/brcm/brcmfmac4339-sdio.bin to /lib/firmware/brcm/brcmfmac4329-sdio.bin Because linux-firmware has alternatives for brcmfmac-sdio.bin but none of the

Re: [OE-core] [PATCH v3] bind: 9.10.3-P3 -> 9.11.0b2

On 22 August 2016 at 10:52, Wang Xin wrote: > +EXTRA_OECONF = " ${ENABLE_IPV6} --with-python=python > --with-randomdev=/dev/random --disable-threads \ > @@ -81,7 +76,7 @@ do_install_append() { > install -d "${D}${sysconfdir}/init.d" > install -m

Re: [OE-core] [PATCH] kernel.bbclass: include signing keys when copying files required for module builds

On 12 August 2016 at 15:10, Waldo Mattias wrote: > The absence of certs/signing_key.* in $kerneldir made signing of > out-of-tree kernel modules fail (silently). Add copying of these files > during the shared_workdir task. > This doesn't apply to current master, can

[OE-core] [PATCH v2] oeqa/selftest Adds eSDK test cases to devtool verification.

The covered functions are, install libraries headers and image generation binary feeds. Signed-off-by: Francisco Pedraza --- meta/lib/oeqa/selftest/eSDK.py | 103 + 1 file changed, 103 insertions(+) create mode

[OE-core] [PATCH v2] /oeqa/sdkext Adds verification for devtool on eSDK.

The covered funcions are, build make, build esdk package, build cmake extend autotools recipe creation, kernel module, node.js installation and recipe creation. Signed-off-by: Francisco Pedraza --- meta/lib/oeqa/sdkext/devtool.py| 90

Re: [OE-core] [PATCH 1/1] bash: fix interpreter of ptest script

On 24 August 2016 at 10:26, wrote: > The interpreter of bash ptest script tests/getopts5.sub is > /local/bin/bash which is not suitable for oe. Use /bin/bash instead. > Presumably this test is executed under bash explicitly, so is this really worth fixing? Ross --

Re: [OE-core] [PATCH 0/2] Toggle bind configure options

On 24 August 2016 at 02:46, Kang Kai wrote: > I didn't see Wangxin's work to upgrade bind. So please comment the > patches, and I will rebase them when the upgrade patch is merged. > Looks good to me! Ross -- ___

Re: [OE-core] [PATCH 1/8] [autotools] export CCLD_FOR_BUILD

On 24 August 2016 at 12:28, Jérémy Rosen wrote: > ok, so CC_FOR_BUILD seems to be a common convention and CCLD_FOR_BUILD > seems only used by our patch for pcre. Fixing it to use CC_FOR_BUILD for > linking is trivial > > but the patch is marked as submitted upstream, so

[OE-core] weston startup problem

Hi All, The weston systemd startup implementation is not working correctly and I need some help fixing it. With systemd and pam on the image, the expected behavior is that XDG_RUNTIME_DIR would already be set when weston is launched from weston.service. Turns out XDG_RUNTIME_DIR is not set,

Re: [OE-core] [PATCH] linux-firmware: package carl9170 separately

> On Aug 24, 2016, at 5:22 AM, Ioan-Adrian Ratiu wrote: > > carl9170 is an atheros-based firmware, the succesor of ar9170 which is > deprecated and its driver (ar9170) was removed from the kernel tree. > carl9170 comes both as a binary blob and also with free sources; the >

Re: [OE-core] [oe-core][PATCH 1/1] useradd: do not delete users and groups during configure

On 2016-08-16 02:16 PM, Joe Slater wrote: If two recipes both create the same users and groups, the second recipe can delete items created by the first causing things like "chown" to fail for the first recipe. Signed-off-by: Joe Slater --- meta/classes/useradd.bbclass |

Re: [OE-core] [PATCH 3/8] [rpm] force a configure before make distclean

On 8/24/16 9:17 AM, Jérémy Rosen wrote: > > > On 24/08/2016 16:13, Mark Hatle wrote: >> >> Make often has a rule looking at the time stamp of specific files and >> re-running >> specific autotools if they are 'out of date'. That COULD be the cause of the >> errant call to gcc? > that would

Re: [OE-core] [PATCH 3/8] [rpm] force a configure before make distclean

On 24/08/2016 16:13, Mark Hatle wrote: Make often has a rule looking at the time stamp of specific files and re-running specific autotools if they are 'out of date'. That COULD be the cause of the errant call to gcc? that would make sense... I have not observed the above occurring -- but

Re: [OE-core] [PATCH 3/8] [rpm] force a configure before make distclean

On 8/24/16 2:44 AM, Jérémy Rosen wrote: > > > On 23/08/2016 19:16, Mark Hatle wrote: >> On 8/23/16 11:54 AM, Burton, Ross wrote: >>> On 23 August 2016 at 08:25, Jérémy Rosen >> > wrote: >>> >>> - ( cd ${S}/syck ; set +e ; rm -- -l*

Re: [OE-core] [PATCH 2/6] linux-yocto/4.1: bump to v4.1.29

On Wed, Aug 24, 2016 at 7:25 AM, Richard Purdie < richard.pur...@linuxfoundation.org> wrote: > On Fri, 2016-08-19 at 10:57 -0400, Bruce Ashfield wrote: > > On 2016-08-18 11:20 AM, Richard Purdie wrote: > > > On Thu, 2016-08-18 at 11:16 -0400, Bruce Ashfield wrote: > > > > On 2016-08-18 11:15 AM,

[OE-core] [PATCH] linux-firmware: package carl9170 separately

carl9170 is an atheros-based firmware, the succesor of ar9170 which is deprecated and its driver (ar9170) was removed from the kernel tree. carl9170 comes both as a binary blob and also with free sources; the sources are deleted in linux-firmware.bb to avoid depeding on bash/etc. Package the

Re: [OE-core] [PATCH] gitpkgv: Fix $GITPKV for a single named git source

Hi, Clemens Lang wrote: > Shameless bump. I haven’t heard any feedback on this other than this “looks > good” comment, but it isn’t merged. Is there a problem with the patch? My apologies, it seems this patch should have gone to openembedded-devel rather than this

Re: [OE-core] inherit allarch and use RDEPENDS

On 24-08-16 09:18, Richard Purdie wrote:> On Wed, 2016-08-24 at 08:35 +0200, Mike Looijmans wrote:>> First time I've heard about this limitation, I don't understand>> what's this about either. I've been telling people to put their arch>> or machine specific code into a seperate package and

Re: [OE-core] [PATCH 1/8] [autotools] export CCLD_FOR_BUILD

(Adding original patch author to mail) On 24/08/2016 13:05, Jérémy Rosen wrote: [...] +export CCLD_FOR_BUILD = "${BUILD_CCLD}” if its used by just one recipe then its not worth abstracting it out. Perhaps fixing

Re: [OE-core] [PATCH 2/6] linux-yocto/4.1: bump to v4.1.29

On Fri, 2016-08-19 at 10:57 -0400, Bruce Ashfield wrote: > On 2016-08-18 11:20 AM, Richard Purdie wrote: > > On Thu, 2016-08-18 at 11:16 -0400, Bruce Ashfield wrote: > > > On 2016-08-18 11:15 AM, Richard Purdie wrote: > > > > On Mon, 2016-08-15 at 14:26 -0400, Bruce Ashfield wrote: > > > > >

Re: [OE-core] [PATCH 1/8] [autotools] export CCLD_FOR_BUILD

On 24/08/2016 02:50, Khem Raj wrote: On Aug 23, 2016, at 12:25 AM, Jérémy Rosen wrote: The autotools class already export most *_FOR_BUILD from bitbake's BUILD_* variables. Somehow the variable CCLD_FOR_BUILD was missing At least libpcre uses that variable and will

Re: [OE-core] [PATCH] gitpkgv: Fix $GITPKV for a single named git source

Hi everybody, Khem Raj wrote: >> On Aug 11, 2016, at 3:04 AM, Clemens Lang >> wrote: >> >> Recipes that fetch from a single git source, assign a name to this >> source and do not set SRCREV_FORMAT to this name will always get >> a GITPKGV value

[OE-core] [PATCH] combo-layer: python3: fix UnicodeDecodeError

check_patch function opens patch file in text mode. This causes python3 to throw exception when calling readline(): UnicodeDecodeError: 'utf-8' codec can't decode byte 0xa7 in position : invalid start byte Opening file in binary mode and using binary type instead

[OE-core] [PATCH 0/1] bash: fix interpreter of ptest script

From: Kai Kang The following changes since commit 94646f4828c2aa11a89996763edaa2e9d57106a9: oeqa/buildiptables: Switch from netfilter.org to yoctoproject.org mirror (2016-08-23 17:59:43 +0100) are available in the git repository at:

[OE-core] [PATCH 1/1] bash: fix interpreter of ptest script

From: Kai Kang The interpreter of bash ptest script tests/getopts5.sub is /local/bin/bash which is not suitable for oe. Use /bin/bash instead. Signed-off-by: Kai Kang --- meta/recipes-extended/bash/bash.inc | 2 ++ 1 file changed, 2

[OE-core] [PATCH] groff: correct the location path for awk

awk is located at /usr/bin/, but not /bin/ Signed-off-by: Zhenbo Gao --- meta/recipes-extended/groff/groff_1.22.3.bb | 6 ++ 1 file changed, 6 insertions(+) diff --git a/meta/recipes-extended/groff/groff_1.22.3.bb b/meta/recipes-extended/groff/groff_1.22.3.bb

Re: [OE-core] [PATCH 7/8] [sanity] fix hardcoded references to gcc

On 23/08/2016 17:40, Jérémy Rosen wrote: On 23/08/2016 17:11, Burton, Ross wrote: On 23 August 2016 at 15:53, Burton, Ross > wrote: I think this is because BUILD_CC by default contains whitespace, and bb.utils.which looks for

[OE-core] [PATCH v2 0/9] oe-build-perf-test: use Python unittest framework

Patch #8, i.e. the patch suppressing logger output was too aggressive in v1 of this patchset. We want to get most of the logger output to stderr, after all. In v2 the logger output to stderr is only disabled during the time the tests are being run. Other patches are not changed (except for rebase

Re: [OE-core] [PATCH 5/8] [linux-libc-headers] allow overriding compiler name in KConfig

[...] If this is broken, it needs to be fixed upstream. I agree. now a days we have more than gcc available as system C compiler perhaps your patch might be upstream worthy. As stated elsewhere, I now have a proper way to override the variables without patching the build system. V2 of

Re: [OE-core] [PATCH 3/8] [rpm] force a configure before make distclean

On 23/08/2016 19:16, Mark Hatle wrote: On 8/23/16 11:54 AM, Burton, Ross wrote: On 23 August 2016 at 08:25, Jérémy Rosen > wrote: - ( cd ${S}/syck ; set +e ; rm -- -l* ; make distclean ) || : + ( cd ${S}/syck ; set +e

Re: [OE-core] inherit allarch and use RDEPENDS

On Wed, 2016-08-24 at 08:35 +0200, Mike Looijmans wrote: > First time I've heard about this limitation, I don't understand > what's this about either. I've been telling people to put their arch > or machine specific code into a seperate package and RDEPEND on it > from an allarch package that

[OE-core] [PATCH 19/19] build-perf-test-wrapper.sh: make workdir configurable

New command line argument '-w' may be used to specify work dir other than the default /build-perf-test. Signed-off-by: Markus Lehtonen --- scripts/contrib/build-perf-test-wrapper.sh | 12 +--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git

[OE-core] [PATCH 16/19] build-perf-test-wrapper.sh: parse args with getopts

Use getopts for parsing the command line. This changes the usage so that if a commit (to-be-tested) is defined it must be given by using '-c', instead of a positional argument. Signed-off-by: Markus Lehtonen --- scripts/contrib/build-perf-test-wrapper.sh | 30

[OE-core] [PATCH 14/19] oeqa.buildperf: add git commit count to result data

This number represents the number of commits since the beginning of git history until the tested revision. This helps e.g. in ordering results. Signed-off-by: Markus Lehtonen --- meta/lib/oeqa/buildperf/base.py | 18 +++--- 1 file changed, 11

[OE-core] [PATCH 11/19] oe-build-perf-test: pre-check Git repo when using --commit-results

Do a pre-check on the path that is specified with --commit-results before running any tests. The script will create and/or initialize a fresh Git repository if the given directory does not exist or if it is an empty directory. It fails if it finds a non-empty directory that is not a Git

[OE-core] [PATCH 13/19] oe-build-perf-test: new {tag_num} keyword for --commit-results-tag

This makes it possible to create numbered tags, where the "basename" of the tag is the same and the only difference is an (automatically) increasing index number. This is useful if you do multiple test runs on the same commit. For example, using: --commit-results-tag

[OE-core] [PATCH 12/19] oe-build-perf-test: tag results committed to Git

Create a Git tag when committing results to a Git repository. This patch also implements --commit-results-tag command line option for controlling the tag name. The value is a format string where the following fields may be used: - {git_branch} - target branch being tested - {git_commit} - target

[OE-core] [PATCH 09/19] oe-build-perf-test: implement --commit-results-branch

A new command line option for defining the branch where results are commited. The value is actually a format string accepting two field names: - {git_branch} expands to the name of the target branch being tested - {tester_host} expands to the hostname of the tester machine The option has no

[OE-core] [PATCH 06/19] oeqa.utils.git.GitRepo: new arg to require topdir

Add a new 'is_topdir' argument to the GitRepo init method which validates that the given path is the top directory of a Git repository. Without this argument GitRepo also accepts subdirectories of a Git repository (in which case GitRepo will point to the parent directory that is the top directory

[OE-core] [PATCH 05/19] oeqa.utils.git: implement GitRepo.get_current_branch()

Signed-off-by: Markus Lehtonen --- meta/lib/oeqa/buildperf/base.py | 7 ++- meta/lib/oeqa/utils/git.py | 8 2 files changed, 10 insertions(+), 5 deletions(-) diff --git a/meta/lib/oeqa/buildperf/base.py b/meta/lib/oeqa/buildperf/base.py index

[OE-core] [PATCH 17/19] build-perf-test-wrapper.sh: allow saving results in Git

Add new command line argument '-C' that allows saving results in a Git repository. Signed-off-by: Markus Lehtonen --- scripts/contrib/build-perf-test-wrapper.sh | 14 +++--- 1 file changed, 11 insertions(+), 3 deletions(-) diff --git

[OE-core] [PATCH 18/19] build-perf-test-wrapper.sh: make archive dir configurable

Add new command line argument '-a' that can be used to define the directory where results (tarballs) are archived. Giving an empty string disables archiving which makes sense if you store results in Git. Signed-off-by: Markus Lehtonen ---

[OE-core] [PATCH 10/19] oeqa.utils.git: implement init() method

Method for doing 'git init'. Signed-off-by: Markus Lehtonen --- meta/lib/oeqa/utils/git.py | 6 ++ 1 file changed, 6 insertions(+) diff --git a/meta/lib/oeqa/utils/git.py b/meta/lib/oeqa/utils/git.py index ca84680..ae85d27 100644 ---

[OE-core] [PATCH 15/19] oe-build-perf-test: add {git_commit_count} keyword for --commit-results-tag

Makes it possible to create easily sortable tags. Also, the default tag format is updated to use the new keyword. Signed-off-by: Markus Lehtonen --- meta/lib/oeqa/buildperf/base.py | 1 + scripts/oe-build-perf-test | 2 +- 2 files changed, 2 insertions(+),

[OE-core] [PATCH 07/19] oeqa.buildperf: use term commit instead of revision

This is basically a internal change, at this point. Term 'commit' better represents the data we actually have. Term 'revision' is more vague and could be understood to point to a tag object, for example. Signed-off-by: Markus Lehtonen ---

[OE-core] [PATCH 08/19] oe-build-perf-test: support committing results data to Git

Implement a new command line option '--commit-results' which commits the test results data into a Git repository. The given path must be an existing initialized local Git repository. Signed-off-by: Markus Lehtonen --- meta/lib/oeqa/buildperf/base.py | 35

[OE-core] [PATCH 01/19] oe-build-perf-test: implement --run-tests option

Makes it possible to run only a subset of tests. NOTE: The tests currently have (unwritten) dependencies on each other so use this option with care. Mainly for debugging. Signed-off-by: Markus Lehtonen --- scripts/oe-build-perf-test | 7 ++- 1 file changed,

[OE-core] [PATCH 00/19] oe-build-pef-test: support saving results in a Git repo

This patchset makes it possible to store build performance test results in a Git repository. The support is written directly in oe-build-perf-test script which hopefully makes it easier use. The new feature is disabled by default, and, it must be enabled with --commit-results option. Further

[OE-core] [PATCH 04/19] oeqa.utils.git: introduce GitRepo.rev_parse()

Signed-off-by: Markus Lehtonen --- meta/lib/oeqa/buildperf/base.py | 2 +- meta/lib/oeqa/utils/git.py | 7 +++ 2 files changed, 8 insertions(+), 1 deletion(-) diff --git a/meta/lib/oeqa/buildperf/base.py b/meta/lib/oeqa/buildperf/base.py index

[OE-core] [PATCH 03/19] oeqa.utils.git: support git commands with updated env

Extend GitRepo.run_cmd so that the caller may redefine and/or define additional environment variables that will be used when the git command is run. Signed-off-by: Markus Lehtonen --- meta/lib/oeqa/utils/git.py | 8 ++-- 1 file changed, 6 insertions(+), 2

[OE-core] [PATCH 02/19] oe-build-perf-test: use absolute paths in cmdline args

This is safer as the current working directory may change. Signed-off-by: Markus Lehtonen --- scripts/oe-build-perf-test | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/scripts/oe-build-perf-test b/scripts/oe-build-perf-test index

[OE-core] [PATCH] perl: Correct perl path for ptest

From: He Zhe Substitute /usr/local with ${bindir} Signed-off-by: He Zhe --- meta/recipes-devtools/perl/perl-ptest.inc | 1 + 1 file changed, 1 insertion(+) diff --git a/meta/recipes-devtools/perl/perl-ptest.inc

[OE-core] [PATCH] nasm: 2.11.08 -> 2.12.02

Upgrade nasm from 2.11.08 to 2.12.02. Signed-off-by: Dai Caiyun --- meta/recipes-devtools/nasm/{nasm_2.11.08.bb => nasm_2.12.02.bb} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-devtools/nasm/{nasm_2.11.08.bb => nasm_2.12.02.bb} (81%)

[OE-core] [PATCH] lsbinitscripts: 9.64 -> 9.68

Upgrade lsbinitscripts from 9.64 to 9.68. Signed-off-by: Wang Xin --- .../0001-functions-avoid-exit-1-which-causes-init-scripts-to-.patch | 5 +++-- .../lsb/{lsbinitscripts_9.64.bb => lsbinitscripts_9.68.bb} | 6 +++--- 2 files changed, 6 insertions(+),

Re: [OE-core] inherit allarch and use RDEPENDS

On 23-08-16 17:32, Richard Purdie wrote:> On Tue, 2016-08-23 at 15:15 +, Peter Kjellerstedt wrote:>> This is the first I heard about limits to recipes that inherit>> allarch>> and also use RDEPENDS. So after I read the above, I went and read the>> documentation for the allarch class, which