[yocto] Which recipe produce that file?

Hi all. My name's Mauro and I write from Parma, Italy. I'm in trouble because recently I get a collision error. It seems that more than one recipes try to install the same file in the same path in populate_sdk task This is an example -- ERROR: xcb-util-0.4.0-r0

[yocto] [meta-mingw][PATCH] nativesdk-packagegroup-sdk-host: add qemu

Now that we can build qemu for mingw, include it in SDK. Signed-off-by: Juro Bystricky --- recipes-core/packagegroups/nativesdk-packagegroup-sdk-host.bbappend | 1 + 1 file changed, 1 insertion(+) diff --git

[yocto] [meta-mingw][PATCH] qemu_2.11.%.bbappend: fix broken qemu build for mingw

The commit "qemu: Bump to version 2.11.0" in oe-core broke the build of qemu for mingw, due to using "socketpair", which is not supported by mingw. "socketpair" is used in a local patch, not in the qemu upstream code. The original local patch had conditional code to exclude "socketpair" for

[yocto] [meta-mingw][PATCH] diffutils_3.6: build for mingw

Build of diffutils was requested/broken for mingw because of the commit "diffutils: allow native & nativesdk builds" This patch implements neccessary steps needed to build diffutils executables: cmp.exe diff.exe diff3.exe sdiff.exe [YOCTO #12662] Signed-off-by: Juro Bystricky

[yocto] [ANNOUNCEMENT] Milestone 3 for Yocto Project 2.5 (yocto-2.5_M3) now available

We are pleased to announce the third milestone release for Yocto Project 2.5 (yocto-2.5_M3) is available for download now. Download: http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-2.5_M3/ poky f49ee61422c867516db252054e993df29f775136 bitbake

Re: [yocto] Getting the version of Yocto that is being used.

On Thu, Apr 12, 2018 at 01:11:17PM +0100, Richard Collins wrote: > I get the following for DISTRO. > > DISTRO= "yogurt" > DISTRO_VERSION= "BSP-Yocto-RK3288-PD17.1.1" > For further reference by anyone who is reading this in the archive: the supplier is Phytec, and the distro

[linux-yocto] [PATCH 077/268 v3] kernel/irq/manage.c: Fix irq_set_affinity to allow use with buslocks

From: David Mercado Modify irq_set_affinity() to allow usage of bus locks with "slow bus" IRQ controllers. This only affects those BSPs that use bus locks in their IRQ controllers, such as the LSI Axxia GIC. The recommendation for this change originated from Thomax

[linux-yocto] [PATCH 052/268 v3] arch/arm: arm changes to support the axxia BSP

From: Charlie Paul These files were changed to support the LSI axxia 5500 board. Signed-off-by: Charlie Paul Signed-off-by: John Jacques Signed-off-by: Daniel Dragomir ---

[linux-yocto] [PULL REQUEST v3] Intel Axxia updates to linux-yocto-4.12

Hello Bruce! I made the changes you asked and I ran regression testings on 3 INTEL boards (arm64: cortexa57 and cortexa53; arm: cortexa15). I attached to the mailing list only the patches I made changes. I also added a new patch to change all LSI references to INTEL Axxia. If everything is ok,

Re: [yocto] out of tree module dependencies

On 4/10/18 8:57 AM, RUSSELL PETERSON wrote: > I have been debugging this issue and could use some advice. > > The basic issue I see is that do_make_scripts executes and fails. I have > seen different fails but in the end it all comes back to something being > required in recipe-sysroot or

Re: [yocto] How to update OpenCV to 3.3 in Krogoth branch of Yocto in i.MX6

Hello Nishina, Any progress on the issue? Thank you, Zoran ___ On Tue, Apr 10, 2018 at 8:47 AM, Nishina A. Pervin wrote: > Hi, > > > > How can we update OpenCV to 3.3 from 3.1 in Krogoth branch of Yocto for > i.MX6 board > > > > Regards, > > Nishina > >

[yocto] [meta-security][PATCH 3/3] meta-security: remove depened on other security layers

Signed-off-by: Armin Kuster --- conf/layer.conf | 3 --- 1 file changed, 3 deletions(-) diff --git a/conf/layer.conf b/conf/layer.conf index 04605a1..efc426e 100644 --- a/conf/layer.conf +++ b/conf/layer.conf @@ -12,6 +12,3 @@ BBFILE_PRIORITY_security = "6"

[yocto] [meta-security][PATCH 2/3] clamav: update LLVM version to match core

Signed-off-by: Armin Kuster --- recipes-security/clamav/clamav_0.99.3.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/recipes-security/clamav/clamav_0.99.3.bb b/recipes-security/clamav/clamav_0.99.3.bb index dc26277..043fa21 100644 ---

[yocto] [meta-security][PATCH 1/3] sssd: only include when pam in DISTRO_FEATURES

Signed-off-by: Armin Kuster --- recipes-security/sssd/sssd_1.16.0.bb | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/recipes-security/sssd/sssd_1.16.0.bb b/recipes-security/sssd/sssd_1.16.0.bb index e41a38e..ff5b618 100644 ---

Re: [yocto] Getting the version of Yocto that is being used.

On 04/12/2018 03:11 PM, Richard Collins wrote: I get the following for DISTRO. DISTRO            = "yogurt" DISTRO_VERSION    = "BSP-Yocto-RK3288-PD17.1.1" Can't find any reference to yogurt so I assume this is something the supplier of our SOM's has done. Looking on their Wiki it seems to be

Re: [yocto] Yocto Boot Question

I actually resolved my first issue today - the install on SSD from USB thumb drive's .hddimg seemed correct. There're probably user's prompts on the boot console that I didn't pay attention to at first (I used COM1, which wasn't the boot console). I'd tried removing thumb drive, and changed

Re: [yocto] Getting the version of Yocto that is being used.

That is an excellent suggestion, yes. Ross On 12 April 2018 at 13:54, Martin Jansa wrote: > Cannot LAYERSERIES_CORENAMES added in rocko be used for that? > > On Thu, Apr 12, 2018 at 2:47 PM, Burton, Ross wrote: >> >> I think the message here is

Re: [yocto] Getting the version of Yocto that is being used.

Cannot LAYERSERIES_CORENAMES added in rocko be used for that? On Thu, Apr 12, 2018 at 2:47 PM, Burton, Ross wrote: > I think the message here is that we need to embed the oe-core version > in the metadata somewhere... > > On 12 April 2018 at 13:11, Richard Collins >

Re: [yocto] Getting the version of Yocto that is being used.

I think the message here is that we need to embed the oe-core version in the metadata somewhere... On 12 April 2018 at 13:11, Richard Collins wrote: > I get the following for DISTRO. > > DISTRO= "yogurt" > DISTRO_VERSION=

Re: [yocto] Getting the version of Yocto that is being used.

I get the following for DISTRO. DISTRO= "yogurt" DISTRO_VERSION= "BSP-Yocto-RK3288-PD17.1.1" Can't find any reference to yogurt so I assume this is something the supplier of our SOM's has done. Looking on their Wiki it seems to be based on 2.1.2 (Krogoth) Thanks for the help.

Re: [yocto] Getting the version of Yocto that is being used.

On 04/12/2018 12:44 PM, Richard Collins wrote: I've inherited a Yocto project that I know to be an old version. So one of my tasks is to update to the latest version. Before I do this I would like to know what version I have. The only information I can find is the bitbake version, BB_VERSION   

Re: [yocto] Getting the version of Yocto that is being used.

If your project also includes meta-poky then poky.conf will contain a DISTRO_VERSION assignment. However, https://wiki.yoctoproject.org/wiki/Releases indicates that bitbake 1.32 was part of 2.2/morty. Ross On 12 April 2018 at 10:44, Richard Collins wrote: >

[yocto] Getting the version of Yocto that is being used.

I've inherited a Yocto project that I know to be an old version. So one of my tasks is to update to the latest version. Before I do this I would like to know what version I have. The only information I can find is the bitbake version, BB_VERSION= "1.32.0". Many thanks, Richard. --

[yocto] Hello from Me, Richard

Just wanted to introduce myself. I'm working at a startup in the UK and my job is to manage and create the embedded platform that the product will run on. ttfn, Richard. -- ___ yocto mailing list yocto@yoctoproject.org