[OE-core] [PATCH 0/1] dhcp: add dhclient.service

The following changes since commit 57f606b12b339c82e6981d7ac32450c00d787085: libgcrypt: upgrade to 1.7.8 (2017-07-19 15:13:40 +0100) are available in the git repository at: git://git.pokylinux.org/poky-contrib ChenQi/dhclient_service http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=Ch

[OE-core] [PATCH 1/1] dhcp: add dhclient.service

Add dhclient.service. This service file mainly comes from meta-systemd, with modifications to take nfs boot into consideration. While using eth0 as the nfsboot interface, we'd like dhclient service to skip it like what ifup and connman do in sysvinit. Signed-off-by: Chen Qi --- meta/recipes-con

Re: [OE-core] [PATCHv3] vulkan-demos: Add recipe

On 2017年07月11日 20:26, Jussi Kukkonen wrote: Sascha Willems collection of Vulkan demos is useful as a smoke testing tool. * Add patch to install binaries and data. * Add patch to fix build on X86 * Use a combination of patch and do_install_append to avoid some 3D models with unclear licensing. S

Re: [OE-core] [PATCH 4/6] bluez5: upgrade to 5.46

Hi Marc, On Wed, Jul 19, 2017 at 11:13:16AM -0400, Marc Ferland wrote: > On Wed, Jul 19, 2017 at 11:01 AM, Maxin B. John wrote: > > > > 5.45 -> 5.46 > > > > Signed-off-by: Maxin B. John > > --- > > meta/recipes-connectivity/bluez5/{bluez5_5.45.bb => bluez5_5.46.bb} | 4 > > ++-- > > 1 file cha

Re: [OE-core] Fwd: Nothing PROVIDES 'libvdpau'

Hi Jason, On Wed, Jul 19, 2017 at 10:34:36AM -0700, Jason Liu wrote: > Hello Openembedded, > For recipes in "meta-openembedded", you will get faster response from "openembedded-de...@lists.openembedded.org" mailing list. >Currently I have a compile error saying: Nothing PROVIDES 'libvdpau'. >I o

Re: [OE-core] [PATCH 3/3] recipetool: create: being able to set branch when revision is provided

On 13 July 2017 at 04:33, Chang Rebecca Swee Fun < rebecca.swee.fun.ch...@intel.com> wrote: > if not srcuri: > lines_before.append('# No information for SRC_URI yet (only an > external source tree was specified)') > +# Check if users has provide a branch > +append_branch = br

[OE-core] [PATCH] meta: fix bfd "cannot make copy relocation for protected symbol" issues

From: Ming Liu Quite a few such compiling issues were found when I was building with following configs: ... MACHINE = "beaglebone" TCLIBC = "musl" DISTRO_FEATURES_append = " ld-is-gold" ... There is already a workaround fixed a same issue but only for libunwind: commit 482733bae05bdc7b149e515fb2

[OE-core] [PATCHv2 0/4] devtool: add: automatically set branch for git URLs if not master

Hi Ross, Change log on v2: Fixed the tracebacks on local variable being referenced before assignment. Along with this series, I have take in Stanley's patch on YOCTO #11393 which has a dependency on my series. Thank you. Rebecca ... ... Cover letter on first submission: Quoted from Bugzilla

[OE-core] [PATCHv2 1/4] recipetool: create: disable PREMIRRORS and MIRRORS by default

When creating new recipes, we are almost certainly fetching a new source rather that something that has already been fetched. I have disable PREMIRRORS and MIRRORS settings from datastore while leaving an option for users to enable them manually if needed. Signed-off-by: Chang Rebecca Swee Fun --

[OE-core] [PATCHv2 4/4] recipetool: create: handle git URLs specifying only a tag

From: Stanley Phoong If a git URL is passed to recipetool create with a tag=, recipetool should handle it assuming that the tag is valid. Also, during the creation of recipe, it seems that the automation for replacing ${PV} at the SRCURI for tag, (e.g mbed-tls-${PV}) is causing some issue due to

[OE-core] [PATCHv2 2/4] devtool: standard: enable options for PREMIRRORS and MIRRORS

Since we have provide an option to manually enable PREMIRRORS and MIRRORS in recipetool, we need to make sure devtool is having the same options as devtool uses recipetool in creating new recipes. Signed-off-by: Chang Rebecca Swee Fun --- scripts/lib/devtool/standard.py | 3 +++ 1 file changed,

[OE-core] [PATCHv2 3/4] recipetool: create: being able to set branch when revision is provided

When recipetool create is run on a git URL and a revision specified that is not on master, and "branch=" isn't already in the URL, then we should get the correct branch and append the branch to the URL. If the revision was found on multiple branches, we will display error to inform user to provide

[OE-core] [morty][PATCH 1/2] libpng: move SRC_URI back to SOURCEFORGE_MIRROR

Since GENTOO_MIRROR removes older binaries, move back to SOURCEFORGE_MIRROR [YOCTO #11554] Signed-off-by: Maxin B. John --- meta/recipes-multimedia/libpng/libpng_1.6.24.bb | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/meta/recipes-multimedia/libpng/libpng_1.6.24.bb

[OE-core] [PATCH] libpng: upgrade to 1.6.30

1.6.29 -> 1.6.30 No changes in License.The license checksums changed because of update in Copyright dates in LICENSE and png.h files. Since GENTOO_MIRROR also removes the older releases of libpng, it makes sense to move back to the original SOURCEFORGE_MIRROR and provide an additional MIRROR to t

[OE-core] [morty][PATCH 2/2] libpng12: move SRC_URI back to SOURCEFORGE_MIRROR

Since GENTOO_MIRROR removes older binaries, move back to SOURCEFORGE_MIRROR. Also provide a MIRROR to "older-releases" directory. [YOCTO #11556] Signed-off-by: Maxin B. John --- meta/recipes-lsb4/libpng/libpng12_1.2.56.bb | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/

[OE-core] [PATCH] ffmpeg: fix pkg-config utilization

in config.log we can see: WARNING: aarch64-linaro-linux-pkg-config not found, library detection may fail. ffmpeg configure script is not looking for pkg-config at the rigt place since it is assuming cross compilation. let's force its value in the recipe. This patches 'fixes' library detection and

[OE-core] [PATCH v2] bluez5: upgrade to 5.46

5.45 -> 5.46 This includes the new testing utility "advtest" Signed-off-by: Maxin B. John --- meta/recipes-connectivity/bluez5/{bluez5_5.45.bb => bluez5_5.46.bb} | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) rename meta/recipes-connectivity/bluez5/{bluez5_5.45.bb => bluez5_5.46.bb

[OE-core] [PATCH] rpm/dnf: fix Upstream-Status to reflect upstream submission status

Signed-off-by: Alexander Kanavin --- .../createrepo-c/0001-Correctly-install-the-shared-library.patch| 2 +- .../dnf/0001-Move-releasever-check-after-the-etc-dnf-vars-substit.patch | 2 +- .../libcomps/0002-Set-library-installation-path-correctly.patch | 2 +- .../0001-FindGtkDoc.

[OE-core] [PATCH] glibc: fix upstream-status tag in a patch

Signed-off-by: Ross Burton --- .../glibc/glibc/0025-locale-fix-hard-coded-reference-to-gcc-E.patch | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-core/glibc/glibc/0025-locale-fix-hard-coded-reference-to-gcc-E.patch b/meta/recipes-core/glibc/glibc/0025-loca

Re: [OE-core] [PATCH 1/2] glibc: Update to latest on 2.26 pre-release

Fails in glibc-locale here: | LC_ADDRESS: language abbreviation `agr' not defined | Makefile:1039: recipe for target '/data/poky-tmp/master/build/work/corei7-64-poky-linux/glibc-locale/2.25.90-r0/locale-tree/usr/lib/locale/agr_PE' failed | make: *** [/data/poky-tmp/master/build/work/corei7-64-poky

Re: [OE-core] [PATCH] ffmpeg: fix pkg-config utilization

On Thu, Jul 20, 2017 at 1:56 PM, Nicolas Dechesne wrote: > > in config.log we can see: > WARNING: aarch64-linaro-linux-pkg-config not found, library detection may > fail. > > ffmpeg configure script is not looking for pkg-config at the rigt place since > it > is assuming cross compilation. let's

Re: [OE-core] [PATCH 1/2] glibc: Update to latest on 2.26 pre-release

On Thu, Jul 20, 2017 at 8:51 AM, Burton, Ross wrote: > Fails in glibc-locale here: > > | LC_ADDRESS: language abbreviation `agr' not defined > | Makefile:1039: recipe for target > '/data/poky-tmp/master/build/work/corei7-64-poky-linux/glibc-locale/2.25.90-r0/locale-tree/usr/lib/locale/agr_PE' > fa

Re: [OE-core] [PATCH] ffmpeg: fix pkg-config utilization

On 20 July 2017 at 13:58, Nicolas Dechesne wrote: > and it would make this patch a no-op instead. the patch would only > 'fix' the pkg-config mistmatch. and we can fixup the xcb dependencies > as a follow up patch instead. i am opened to suggestions.. > Enabling those is good, although there sho

[OE-core] [PATCH 00/23] cve-check related fixes

Results from cve-check are not very good at the moment. One of the reasons for this is that component names used in CVE database differ from yocto recipe names. This series fixes several of those name mapping problems by setting the CVE_PRODUCT correctly in the recipes. To check this mapping with a

[OE-core] [PATCH 03/23] acpid.inc: set CVE_PRODUCT to acpid2

It is used in NVD database for CVE's like: https://nvd.nist.gov/vuln/detail/CVE-2011-4578 Signed-off-by: Mikko Rapeli --- meta/recipes-bsp/acpid/acpid.inc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta/recipes-bsp/acpid/acpid.inc b/meta/recipes-bsp/acpid/acpid.inc index 12ec19b..766

[OE-core] [PATCH 04/23] bluez5.inc: set CVE_PRODUCT to bluez

bluez is the product name in NVD database for CVE's like: https://nvd.nist.gov/vuln/detail/CVE-2016-7837 Signed-off-by: Mikko Rapeli --- meta/recipes-connectivity/bluez5/bluez5.inc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta/recipes-connectivity/bluez5/bluez5.inc b/meta/recipes-

[OE-core] [PATCH 01/23] buildhistory.bbclass: add LICENSE and CVE_PRODUCT to recipe and package data

LICENSE can be used in various checks after builds. Reading license data from buildhistory is better than trying to parse recipes in a source tree. CVE_PRODUCT can be used by scripts to e.g. check if it matches to the CVE product names in CVE/NVD database. It the two are combined, a CVE product n

[OE-core] [PATCH 02/23] buildhistory.bbclass: add BUILDHISTORY_FORCE_UPDATE option

Setting BUILDHISTORY_FORCE_UPDATE = "1" in local.conf forces buildhistory updates and recipe rebuilds also when only buildhistory.bbclass changed. This is handy when using sstate cache and modifying buildhistory to include new data like recipe and package LICENSE fields. By default new buildhisto

[OE-core] [PATCH 08/23] glib.inc: set CVE_PRODUCT to glib

NVD uses product glib and vendor gnome for CVE's like: https://nvd.nist.gov/vuln/detail/CVE-2016-6855 Signed-off-by: Mikko Rapeli --- meta/recipes-core/glib-2.0/glib.inc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta/recipes-core/glib-2.0/glib.inc b/meta/recipes-core/glib-2.0/glib.

[OE-core] [PATCH 09/23] glibc-common.inc: set CVE_PRODUCT to glibc

All recipes which include this .inc map to glibc NVD component. Signed-off-by: Mikko Rapeli --- meta/recipes-core/glibc/glibc-common.inc | 1 + 1 file changed, 1 insertion(+) diff --git a/meta/recipes-core/glibc/glibc-common.inc b/meta/recipes-core/glibc/glibc-common.inc index bba1568..b05e162

[OE-core] [PATCH 05/23] eglinfo.inc: set CVE_PRODUCT to eglinfo

Upstream is called eglinfo no matter how the recipes are named. There are no existing CVE's for eglinfo in NVD yet. Signed-off-by: Mikko Rapeli --- meta/recipes-graphics/eglinfo/eglinfo.inc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta/recipes-graphics/eglinfo/eglinfo.inc b/meta/re

[OE-core] [PATCH 07/23] gcc-common.inc: set CVE_PRODUCT to gcc

All recipes which include this are using gcc as product name in NVD like https://nvd.nist.gov/vuln/detail/CVE-2015-5276 Signed-off-by: Mikko Rapeli --- meta/recipes-devtools/gcc/gcc-common.inc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta/recipes-devtools/gcc/gcc-common.inc b/meta

[OE-core] [PATCH 06/23] flac_1.3.1.bb: set CVE_PRODUCT to libflac

NVD uses product name libflac for CVE's like: https://nvd.nist.gov/vuln/detail/CVE-2014-8962 Signed-off-by: Mikko Rapeli --- meta/recipes-multimedia/flac/flac_1.3.2.bb | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta/recipes-multimedia/flac/flac_1.3.2.bb b/meta/recipes-multimedia/fla

[OE-core] [PATCH 11/23] libpcre_8.40.bb: set CVE_PRODUCT to prce

It is used in NVD for CVE's like: https://nvd.nist.gov/vuln/detail/CVE-2017-7246 Signed-off-by: Mikko Rapeli --- meta/recipes-support/libpcre/libpcre_8.40.bb | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta/recipes-support/libpcre/libpcre_8.40.bb b/meta/recipes-support/libpcre/libpcr

[OE-core] [PATCH 10/23] icu.inc: set CVE_PRODUCT to international_components_for_unicode

NVD uses it for CVE's like: https://nvd.nist.gov/vuln/detail/CVE-2014-8146 Signed-off-by: Mikko Rapeli --- meta/recipes-support/icu/icu.inc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta/recipes-support/icu/icu.inc b/meta/recipes-support/icu/icu.inc index 5286274..a1ef9ec 100644 ---

[OE-core] [PATCH 14/23] libsndfile1_1.0.28.bb: set CVE_PRODUCT to libsndfile

It is used in NVD to CVE's like: https://nvd.nist.gov/vuln/detail/CVE-2017-6892 Signed-off-by: Mikko Rapeli --- meta/recipes-multimedia/libsndfile/libsndfile1_1.0.28.bb | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta/recipes-multimedia/libsndfile/libsndfile1_1.0.28.bb b/meta/recipes

[OE-core] [PATCH 13/23] libsamplerate0_0.1.9.bb: set CVE_PRODUCT to libsamplerate

It is used in NVD for CVE's like: https://nvd.nist.gov/vuln/detail/CVE-2017-7697 Signed-off-by: Mikko Rapeli --- meta/recipes-multimedia/libsamplerate/libsamplerate0_0.1.9.bb | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta/recipes-multimedia/libsamplerate/libsamplerate0_0.1.9.bb b/m

[OE-core] [PATCH 15/23] nspr_4.14.bb: set CVE_PRODUCT to netscape_portable_runtime

This is used in NVD database entries like CVE: https://nvd.nist.gov/vuln/detail/CVE-2016-1951 Signed-off-by: Mikko Rapeli --- meta/recipes-support/nspr/nspr_4.14.bb | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta/recipes-support/nspr/nspr_4.14.bb b/meta/recipes-support/nspr/nspr_4.1

[OE-core] [PATCH 12/23] libpcre2_10.23.bb: set CVE_PRODUCT to pcre2

It is used in NVD as product name for CVE's like: https://nvd.nist.gov/vuln/detail/CVE-2017-8786 Signed-off-by: Mikko Rapeli --- meta/recipes-support/libpcre/libpcre2_10.23.bb | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta/recipes-support/libpcre/libpcre2_10.23.bb b/meta/recipes-su

[OE-core] [PATCH 16/23] python.inc: set CVE_PRODUCT to python

All python versions are just python in NVD like this CVE for python 3.4.4: https://nvd.nist.gov/vuln/detail/CVE-2016-5699 Signed-off-by: Mikko Rapeli --- meta/recipes-devtools/python/python.inc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta/recipes-devtools/python/python.inc b/meta

[OE-core] [PATCH 17/23] lttng-ust_2.9.1.bb: set CVE_PRODUCT to ust

It is used in NVD for CVE's like: https://nvd.nist.gov/vuln/detail/CVE-2010-3386 Signed-off-by: Mikko Rapeli --- meta/recipes-kernel/lttng/lttng-ust_2.9.1.bb | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta/recipes-kernel/lttng/lttng-ust_2.9.1.bb b/meta/recipes-kernel/lttng/lttng-ust

[OE-core] [PATCH 18/23] quota_4.03.bb: set CVE_PRODUCT to linux_diskquota

It is used in NVD for CVE's like: https://nvd.nist.gov/vuln/detail/CVE-2012-3417 Signed-off-by: Mikko Rapeli --- meta/recipes-extended/quota/quota_4.03.bb | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta/recipes-extended/quota/quota_4.03.bb b/meta/recipes-extended/quota/quota_4.03.bb

[OE-core] [PATCH 23/23] cve-check.bbclass: use "+git" as separator in PV instead of "git+"

PV is the recipe major version number. cve-check tries to map that to NVD database release versions of the component. If the recipe sources are taken from git, the PV can be automatically modified to include git details, but the syntax is like 233+gitAUTOINC+a1e2ef7ec9. In CVE checks we want to rem

[OE-core] [PATCH 20/23] wpa-supplicant_2.6.bb: set CVE_PRODUCT to wpa_supplicant

It is used in NVD database CVE's like: https://nvd.nist.gov/vuln/detail/CVE-2015-1863 Signed-off-by: Mikko Rapeli --- meta/recipes-connectivity/wpa-supplicant/wpa-supplicant_2.6.bb | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta/recipes-connectivity/wpa-supplicant/wpa-supplicant_2.6.

[OE-core] [PATCH 19/23] sqlite3.inc: set CVE_PRODUCT to sqlite

It is used in NVD for CVE's like: https://nvd.nist.gov/vuln/detail/CVE-2016-6153 Signed-off-by: Mikko Rapeli --- meta/recipes-support/sqlite/sqlite3.inc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta/recipes-support/sqlite/sqlite3.inc b/meta/recipes-support/sqlite/sqlite3.inc index

[OE-core] [PATCH 22/23] kernel.bbclass: set CVE_PRODUCT to linux_kernel if not set by recipe

It is used by NVD database CVE's like: https://nvd.nist.gov/vuln/detail/CVE-2017-7273 Setting this in kernel.bbclass fixes CVE reporting for all users of the class. Signed-off-by: Mikko Rapeli --- meta/classes/kernel.bbclass | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta/classes/ke

[OE-core] [PATCH 21/23] cve-check.bbclass: use weak assignment for default CVE_PRODUCT

This way also bbclasses can override it. For example kernel.bbclass could set CVE_PRODUCT to linux_kernel for all users of the class which compile Linux kernels. Signed-off-by: Mikko Rapeli --- meta/classes/cve-check.bbclass | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/met

Re: [OE-core] [PATCH] ffmpeg: fix pkg-config utilization

On Thu, Jul 20, 2017 at 3:03 PM, Burton, Ross wrote: > > On 20 July 2017 at 13:58, Nicolas Dechesne > wrote: >> >> and it would make this patch a no-op instead. the patch would only >> 'fix' the pkg-config mistmatch. and we can fixup the xcb dependencies >> as a follow up patch instead. i am open

Re: [OE-core] [PATCH] ffmpeg: fix pkg-config utilization

On 20 July 2017 at 14:37, Nicolas Dechesne wrote: > but do we want to make these changes as 1 patch with the pkg-config > fix, or as a follow up patch? I have other patches to fix sdl -> sdl2 > and add ffplay support. > Followup is fine, imho. Ross -- __

Re: [OE-core] [PATCH] ffmpeg: fix pkg-config utilization

On Thu, Jul 20, 2017 at 7:56 AM, Nicolas Dechesne wrote: > in config.log we can see: > WARNING: aarch64-linaro-linux-pkg-config not found, library detection may > fail. > > ffmpeg configure script is not looking for pkg-config at the rigt place since > it > is assuming cross compilation. let's f

Re: [OE-core] [PATCH 0/5] Add openssl 1.1

On 7/19/17 12:37 PM, Alexander Kanavin wrote: > On 07/19/2017 07:55 PM, Andre McCurdy wrote: >>> Openssl 1.1 is an opt-out; it has the same recipe name as openssl 1.0 had, >>> and so >>> all dependencies are compiled with it by default. If there's an API issue, >>> please >>> fix it, or adjust th

Re: [OE-core] [PATCH] ffmpeg: fix pkg-config utilization

On Thu, Jul 20, 2017 at 2:54 PM, Khem Raj wrote: > On Thu, Jul 20, 2017 at 7:56 AM, Nicolas Dechesne > wrote: >> in config.log we can see: >> WARNING: aarch64-linaro-linux-pkg-config not found, library detection may >> fail. >> >> ffmpeg configure script is not looking for pkg-config at the rigt

Re: [OE-core] [PATCH] ffmpeg: fix pkg-config utilization

On 20 July 2017 at 13:54, Khem Raj wrote: > There is a proposal to repace pkgconfig with pkgconf, and I hope it > will create a symlink to provide pkg-config > Yes, it does. Ross -- ___ Openembedded-core mailing list Openembedded-core@lists.openembed

[OE-core] [PATCH v2 3/7] recipetool: create: ensure meaningful error for malformed tarballs

If you pointed recipetool at a URL that should be a tarball e.g. https://tls.mbed.org/download/start/mbedtls-2.4.2-apache.tgz but instead it returns an HTML page, we try to unpack it, gzip complains but the operation doesn't seem to fail - instead we just get back an empty source tree. Change the c

[OE-core] [PATCH v2 2/7] devtool: extract: refactor kern-tools-native handling

When extracting linux-yocto kernel source, we don't need to dance around shutting down and starting up tinfoil anymore, we can just execute the tasks as needed when needed using tinfoil's new build_targets() function. This allows us to tidy up the code structure a bit. Signed-off-by: Paul Eggleton

[OE-core] [PATCH v2 5/7] recipetool: create: reimplement fetching with normal fetch/unpack tasks

Now that we have the ability to run the tasks in a more standard context through tinfoil, change recipetool's fetching code to use that to fetch files using it. This has the major advantage that any dependencies of do_fetch and do_unpack (e.g. for subversion or npm) will be handled automatically. T

[OE-core] [PATCH v2 0/7] recipetool fetching fixes

Some improvements to recipetool create (and hence devtool add) around handling dependencies during fetching, which required extensive reworking of the code in order to use normal task execution instead of calling the fetcher directly. This also fixes bug 11710 which blocked devtool add / recipetool

[OE-core] [PATCH v2 1/7] classes/staging: change fixme debug message from note to debug

These messages were added for debugging during the recipe specific sysroot work. They may still be useful but they don't need to be notes - if they are they show up in recipetool / devtool output when fetching source. (From OE-Core rev: a0e93d5c5dcf59d1898a3db727a5ab2d75e3d20e) Signed-off-by: Pau

[OE-core] [PATCH v2 4/7] recipetool: create: eliminate second fetch for packages

When dealing with package files (.rpm, .ipk etc.) we need to unpack them ourselves to get the metadata, which is thrown away when the fetcher unpacks them. However, since we've already fetched the file once, I'm not sure as to why I thought I needed to fetch it again - we can just get the local pat

[OE-core] [PATCH v2 7/7] recipetool: create: refactor code for ensuring npm is available

Across devtool and recipetool we had an ugly set of code for ensuring that we can call an npm binary, and much of that ugliness was a result of not being able to run build tasks when tinfoil was active - if recipetool found that npm was required and we didn't know beforehand (e.g. we're fetching fr

[OE-core] [PATCH v2 6/7] classes/base: set do_unpack dependencies for rpm files

If we're unpacking any rpm (not just .src.rpm) then we'll need to call rpm2cpio.sh. As of OE-Core rev a7da1aade118d1ccf1b286f82556cd9f706bd2a4 that script no longer uses file-native, but there is a chance that the rpm file will be compressed internally using xz (for example, rpms from Fedora) and t

Re: [OE-core] [PATCH] ffmpeg: fix pkg-config utilization

On Thu, Jul 20, 2017 at 4:30 PM, Burton, Ross wrote: > > On 20 July 2017 at 13:54, Khem Raj wrote: >> >> There is a proposal to repace pkgconfig with pkgconf, and I hope it >> will create a symlink to provide pkg-config > > > Yes, it does. ok.. sorry, i had missed the pkgconf discussion.. i will

[OE-core] [PATCH v2] ffmpeg: fix pkg-config utilization

in config.log we can see: WARNING: aarch64-linaro-linux-pkg-config not found, library detection may fail. ffmpeg configure script is not looking for pkg-config at the rigt place since it is assuming cross compilation. let's force its value in the recipe. This patches 'fixes' library detection, so

Re: [OE-core] [PATCH 2/6] cryptodev: 1.8 -> 1.9

On 18 July 2017 at 19:54, Denys Dmytriyenko wrote: > Should this kind of behavior be addressed by BSP Guidelines and the Yocto > Project Compatible 2.0 requirements? > Not sure what it would say other than "don't jump the gun"... Ross -- ___ Openembe

Re: [OE-core] [PATCH] mesa: Upgrade to 17.1.5 release

On 17 July 2017 at 19:40, Otavio Salvador wrote: > This is a stable bugfix release. Following upstream bugs were fixed: > > Bug 100242 - radeon buffer allocation failure during startup of Factorio > Bug 101657 - strtod.c:32:10: fatal error: xlocale.h: No such file or > directory > Bug 101666 - bi

Re: [OE-core] [PATCH] gcc-7.inc: add new warning "Wnot-cross-compiler"

On Wed, Jul 19, 2017 at 6:35 PM, Khem Raj wrote: > On Wed, Jul 19, 2017 at 7:26 PM, Andre McCurdy > wrote: > > On Wed, Jul 19, 2017 at 2:57 PM, Bystricky, Juro > > wrote: > >>> precisely, the problem is that some host compiler may silently ignore > >>> unknown warnings and some host may not be

Re: [OE-core] [PATCH] gcc-7.inc: add new warning "Wnot-cross-compiler"

On Thu, Jul 20, 2017 at 12:38 PM, Brian Avery wrote: > > > On Wed, Jul 19, 2017 at 6:35 PM, Khem Raj wrote: >> >> On Wed, Jul 19, 2017 at 7:26 PM, Andre McCurdy >> wrote: >> > On Wed, Jul 19, 2017 at 2:57 PM, Bystricky, Juro >> > wrote: >> >>> precisely, the problem is that some host compiler m

Re: [OE-core] [PATCH] gcc-7.inc: add new warning "Wnot-cross-compiler"

On 20 July 2017 at 19:51, Khem Raj wrote: > it does cause harm, by making the behaviour inconsistent and highly > dependent > upon build host. > It *stops* behaviour being dependent on the build host, surely. The problem is that some recipes use the host compiler when they're not meant to be an

Re: [OE-core] [PATCH] mesa: Upgrade to 17.1.5 release

On 20 July 2017 at 16:37, Burton, Ross wrote: > This fails to build on ppc: > > | checking for libdrm >= 2.4.75 libdrm_intel >= 2.4.75... no > Same on arm and mips now. Basically everything that isn't x86, so I'm wondering what the difference between your build environment and the autobuilder i

Re: [OE-core] [PATCH] gcc-7.inc: add new warning "Wnot-cross-compiler"

On Thu, Jul 20, 2017 at 12:18 PM, Burton, Ross wrote: > > On 20 July 2017 at 19:51, Khem Raj wrote: >> >> it does cause harm, by making the behaviour inconsistent and highly >> dependent >> upon build host. > > It *stops* behaviour being dependent on the build host, surely. The problem > is that

Re: [OE-core] [PATCH] gcc-7.inc: add new warning "Wnot-cross-compiler"

On Thu, Jul 20, 2017 at 3:18 PM, Burton, Ross wrote: > > On 20 July 2017 at 19:51, Khem Raj wrote: >> >> it does cause harm, by making the behaviour inconsistent and highly >> dependent >> upon build host. > > > It *stops* behaviour being dependent on the build host, surely. The problem > is tha

Re: [OE-core] [PATCH] gcc-7.inc: add new warning "Wnot-cross-compiler"

On Thu, Jul 20, 2017 at 3:40 PM, Andre McCurdy wrote: > On Thu, Jul 20, 2017 at 12:18 PM, Burton, Ross wrote: >> >> On 20 July 2017 at 19:51, Khem Raj wrote: >>> >>> it does cause harm, by making the behaviour inconsistent and highly >>> dependent >>> upon build host. >> >> It *stops* behaviour

Re: [OE-core] [PATCH] mesa: Upgrade to 17.1.5 release

On Thu, Jul 20, 2017 at 3:22 PM, Burton, Ross wrote: > > On 20 July 2017 at 16:37, Burton, Ross wrote: >> >> This fails to build on ppc: >> >> | checking for libdrm >= 2.4.75 libdrm_intel >= 2.4.75... no > > > Same on arm and mips now. Basically everything that isn't x86, so I'm > wondering what

Re: [OE-core] [PATCH] mesa: Upgrade to 17.1.5 release

On Thu, Jul 20, 2017 at 4:46 PM, Khem Raj wrote: > On Thu, Jul 20, 2017 at 3:22 PM, Burton, Ross wrote: >> >> On 20 July 2017 at 16:37, Burton, Ross wrote: >>> >>> This fails to build on ppc: >>> >>> | checking for libdrm >= 2.4.75 libdrm_intel >= 2.4.75... no >> >> >> Same on arm and mips now.

Re: [OE-core] [PATCH] mesa: Upgrade to 17.1.5 release

On Thu, Jul 20, 2017 at 9:56 PM, Otavio Salvador wrote: > On Thu, Jul 20, 2017 at 4:46 PM, Khem Raj wrote: >> On Thu, Jul 20, 2017 at 3:22 PM, Burton, Ross wrote: >>> >>> On 20 July 2017 at 16:37, Burton, Ross wrote: This fails to build on ppc: | checking for libdrm >= 2.4.7

Re: [OE-core] [PATCH] mesa: Upgrade to 17.1.5 release

On 20 July 2017 at 21:14, Nicolas Dechesne wrote: > It built fine for me (OE-core/nodistro + meta-qcom) with and without > pkg-config installed on the host. > Yeah it's not that, mesa builds fine for intel-corei7 on my machine, but fails with qemuppc. libdrm isn't generating a libdrm_intel if I

Re: [OE-core] [PATCH] mesa: Upgrade to 17.1.5 release

On Thu, Jul 20, 2017 at 5:25 PM, Burton, Ross wrote: > > On 20 July 2017 at 21:14, Nicolas Dechesne > wrote: >> >> It built fine for me (OE-core/nodistro + meta-qcom) with and without >> pkg-config installed on the host. > > > Yeah it's not that, mesa builds fine for intel-corei7 on my machine, b

[OE-core] [PATCH] ffmpeg: add PACKAGECONFIG for sdl2

Enabling sdl2 will bring ffplay applications, which can be handy when working with ffmpeg. Signed-off-by: Nicolas Dechesne --- meta/recipes-multimedia/ffmpeg/ffmpeg_3.3.2.bb | 1 + 1 file changed, 1 insertion(+) diff --git a/meta/recipes-multimedia/ffmpeg/ffmpeg_3.3.2.bb b/meta/recipes-multime

Re: [OE-core] [PATCH 2/2] bc: upgrade 1.06 to 1.07.1

On 05/19/2017 02:17 PM, Jose Lamego wrote: > > On 05/19/2017 10:25 AM, Burton, Ross wrote: >> On 18 May 2017 at 23:28, Jose Lamego > > wrote: >> >> bc recipe must be upgraded to latest version in upstream. >> >> bc license changed from "GPLv2+ & LGPLv

Re: [OE-core] [PATCH] mesa: Upgrade to 17.1.5 release

On 20 July 2017 at 21:36, Otavio Salvador wrote: > My understanding was that mesa was going to include those headers and > stop requiring libdrm-intel. I don't recall if it made into 17.1 or it > is master development. > Ok, this isn't related to the upgrade, I reverted it and 17.1.4 does the sa

[OE-core] [PATCH 1/2] image-vm: Convert vmdk/vdi/qcow2/hdddirect images to IMAGE_CMD

The support for writing vmdk/vdi/qcow2 images has not been converted to make use of the IMAGE_CMD infrastructure and instead relies on custom logic for adding tasks in the right place. Convert these images to making use of IMAGE_CMD. This mainly involves re-listing some of the depends to the new

[OE-core] [PATCH 2/2] image-vm: Change default ROOT_VM to use PARTUUID

From: Matt Porter Support for finding the root partition via PARTUUID is a portable method to determine the system root device as it does not depend on device ordering and also abstracts the diference between IDE devices and SCSI/SATA/etc type devices. Signed-off-by: Matt Porter Signed-off-by:

[OE-core] [oe-core][PATCH 1/1] linux-yocto: only suggest default kernel type

The distro should set a default kernel type (?=) which could be overriden by local.conf (=) or extensions (templates). The kernel itself should only use "??=" to provide a value which allows builds to succeed. Signed-off-by: Joe Slater --- meta/recipes-kernel/linux/linux-yocto.inc | 3 ++- 1 fi

[OE-core] [PATCH 0/1] bison: reduce local pending patches

The following changes since commit 57f606b12b339c82e6981d7ac32450c00d787085: libgcrypt: upgrade to 1.7.8 (2017-07-19 15:13:40 +0100) are available in the git repository at: https://github.com/DengkeDu/openembedded-core.git dengke/bison-reduce-local-pending-patches https://github.com//tree

[OE-core] [PATCH 1/1] bison: reduce local pending patches

Signed-off-by: Dengke Du --- .../bison/bison/0001-src-local.mk-fix-parallel-issue.patch | 9 + 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/meta/recipes-devtools/bison/bison/0001-src-local.mk-fix-parallel-issue.patch b/meta/recipes-devtools/bison/bison/0001-src-lo

[OE-core] [PATCH] subversion: Upgrade 1.9.5-> 1.9.6

Signed-off-by: Richard Purdie --- .../subversion/subversion_1.9.5.bb | 55 -- .../subversion/subversion_1.9.6.bb | 55 ++ 2 files changed, 55 insertions(+), 55 deletions(-) delete mode 100644 meta/recipes-devtools/subversion

[OE-core] [PATCH] ovmf-shell-image.bb: simplify dependencies

The image consists only of the EFI system partition, therefore we can avoid depending on the default wic tools. Signed-off-by: Patrick Ohly --- meta/recipes-core/ovmf/ovmf-shell-image.bb | 7 +-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/meta/recipes-core/ovmf/ovmf-shell-

[OE-core] ✗ patchtest: failure for subversion: Upgrade 1.9.5-> 1.9.6

== Series Details == Series: subversion: Upgrade 1.9.5-> 1.9.6 Revision: 1 URL : https://patchwork.openembedded.org/series/7850/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been executed on th

Re: [OE-core] [PATCH 0/1] bind: 9.10..3-P3 -> 9.10.5-P3

On 2017年07月19日 21:05, Alexander Kanavin wrote: On 07/19/2017 12:08 AM, Khem Raj wrote: The policy in oe-core master is to update to latest stable upstream releases, so please provide an update to 9.11.x. If you want to keep 9.10.x, you can do that, but please provide a more specific reason.