Re: [yocto] How to select defconfig for kernel build with yocto/bitbake

[Dr. Markus Eich]

I have tried the different task separately.

do_fetch works, no recursive link created
do_kernel_checkout works, no recursive link created
do_kernel_configme works, no recursive link created
do_compile works, no recursive link created
do_compile_kernelmodules works, no recursive link created
do_install works, no recursive link created

do_package : Here it crashes. Th package subfolder is created and here 
it creates the recursive link within the subfolder.


What does do_package do in detail? How can I further analyze the error.

/Markus




On 10.07.2014 17:46, Bruce Ashfield wrote:

On 14-07-10 07:11 AM, Dr. Markus Eich wrote:

Thank you Bruce, that did the trick. But I am facing a new problem while
using bitbake for the build process.

I have checked to build the odroid kernel with a standard crosscompiler
tool chain and it works without any problems.

When I do the same with the bitbake toolchain (bitbake virtual/kernel),
it somehow creates a recursive link in the folder

package/usr/src/kernel/drivers/gpu/arm/mali400/ump/arch/arch-release ->
arch-release

This causes a crash in the build system.

Compilation runs fine though. This error seems to be within do_package.
I have removed the link, but somehow it is created automatically.

Any ideas?


Nothing off the top of my head. That link would be created by the kernel
build, and not by bitbake or the oe-core kernel build classes.

I'd start by looking at the kernel's makefiles and seeing where the
link is being created.

Do specific tasks work ? i.e. is that happening during unpack/patch, or
during compilation.

Bruce



/Markus



On 09.07.2014 14:44, Bruce Ashfield wrote:

On 14-07-09 05:38 AM, Dr. Markus Eich wrote:

Dear all,

I work on the process to compile odroid xu kernel with yocto/bitbake

In the kernel sources (from hardkernel) I have the corresponding
defconfig file, i.e. in the git folder
/arch/arm/configs/odroidxu_ubuntu_defconfig.

How can I tell bitbake in my recipe to use 
"odroidxu_ubuntu_defconfig"?


To trigger the oe-core kernel processing to use the defconfig, you need
to put that defconfig in your SRC_URI.

Which means you should grab a copy of that from the kernel tree, and
in the same directory structure as your kernel recipe.

See meta-skeleton/recipes-kernel/linux/linux-yocto-custom.bb for an
example.

Cheers,

Bruce




My recipe looks as follow:

===
require recipes-kernel/linux/linux-yocto.inc

KERNEL_IMAGETYPE = "uImage"

COMPATIBLE_MACHINE = "odroid-xu"

LINUX_VERSION = "3.4.91"
LINUX_VERSION_EXTENSION = "-custom"

FILESEXTRAPATHS_prepend := "${THISDIR}/linux-hardkernel-3.4:"

S = "${WORKDIR}/git"

# from where to fetch the kernel
KERNEL_REPO_OWNER ??= "hardkernel"
KERNEL_REPO_URI ??= "git://github.com/${KERNEL_REPO_OWNER}/linux.git"
KBRANCH = "odroidxu-3.4.y"

SRCREV = "${AUTOREV}"

KV = "3.4.91"
PV = "${KV}+gitr${SRCPV}"
LOCALVERSION ?= ""


SRC_URI = " \
   ${KERNEL_REPO_URI};nocheckout=1;branch=${KBRANCH} \
"

PACKAGES =+ "kernel-headers"
FILES_kernel-headers = "${exec_prefix}/src/linux*"
===

Cheers,

Markus












--
Dr.-Ing. Markus Eich

 Senior Researcher
 Marine Inspection Robotics
 Space Robotics
 
 Besuchsadresse der Nebengeschäftstelle:

 DFKI GmbH
 Robotics Innovation Center
 Robert-Hooke-Straße 5
 28359 Bremen, Germany
 
 Postadresse der Hauptgeschäftsstelle Standort Bremen:

 DFKI GmbH
 Robotics Innovation Center
 Robert-Hooke-Straße 1
 28359 Bremen, Germany

 Tel.: +49 421 178 45-4105
 Zentrale: +49 421 178 45-0
 Fax:  +49 421 178 45-4150 (Faxe bitte namentlich kennzeichnen)
 E-Mail:   markus.e...@dfki.de

 Weitere Informationen: http://www.dfki.de/robotik
 ---
 Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH
 Firmensitz: Trippstadter Straße 122, D-67663 Kaiserslautern
 Geschaeftsfuehrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster
 (Vorsitzender) Dr. Walter Olthoff
 Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes
 Amtsgericht Kaiserslautern, HRB 2313
 Sitz der Gesellschaft: Kaiserslautern (HRB 2313)
 USt-Id.Nr.:DE 148646973
 Steuernummer:  19/673/0060/3
 ---

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Oracle Java for ARM?

[Vladimir Redzhepov]

Hi

We’ve just added support for Oracle Java Embedded SE for ARM into 
meta-oracle-java. You can see our patch here
https://lists.yoctoproject.org/pipermail/yocto/2014-June/020223.html\
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Joe Nicholson
Sent: Wednesday, July 09, 2014 7:11 PM
To: Yocto
Subject: [yocto] Oracle Java for ARM?


Hi Guys

What's the best way of bringing in Oracle's Java JRE for ARM?

The meta-oracle-java layer looks Intel only at the moment :-(

Cheers!

Joe



-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Oracle Java for ARM?

[Vladimir Redzhepov]

I’ve inserted broken link. That’s right
https://lists.yoctoproject.org/pipermail/yocto/2014-June/020223.html

From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Vladimir Redzhepov
Sent: Friday, July 11, 2014 12:57 PM
To: j...@joenicholson.co.uk; Yocto
Subject: Re: [yocto] Oracle Java for ARM?

Hi

We’ve just added support for Oracle Java Embedded SE for ARM into 
meta-oracle-java. You can see our patch here
https://lists.yoctoproject.org/pipermail/yocto/2014-June/020223.html\

From: yocto-boun...@yoctoproject.org 
[mailto:yocto-boun...@yoctoproject.org] On Behalf Of Joe Nicholson
Sent: Wednesday, July 09, 2014 7:11 PM
To: Yocto
Subject: [yocto] Oracle Java for ARM?


Hi Guys

What's the best way of bringing in Oracle's Java JRE for ARM?

The meta-oracle-java layer looks Intel only at the moment :-(

Cheers!

Joe



-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Oracle Java for ARM?

[Joe Nicholson]

 

Brilliant! Thanks a lot Vladimir. 

On 2014-07-11 11:46, Vladimir Redzhepov wrote: 

> I've inserted broken link. That's right 
> 
> https://lists.yoctoproject.org/pipermail/yocto/2014-June/020223.html 
> 
> FROM: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] 
> ON BEHALF OF Vladimir Redzhepov
> SENT: Friday, July 11, 2014 12:57 PM
> TO: j...@joenicholson.co.uk; Yocto
> SUBJECT: Re: [yocto] Oracle Java for ARM? 
> 
> Hi 
> 
> We've just added support for Oracle Java Embedded SE for ARM into 
> meta-oracle-java. You can see our patch here 
> 
> https://lists.yoctoproject.org/pipermail/yocto/2014-June/020223.html [1] 
> 
> FROM: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] 
> ON BEHALF OF Joe Nicholson
> SENT: Wednesday, July 09, 2014 7:11 PM
> TO: Yocto
> SUBJECT: [yocto] Oracle Java for ARM? 
> 
> Hi Guys 
> 
> What's the best way of bringing in Oracle's Java JRE for ARM? 
> 
> The meta-oracle-java layer looks Intel only at the moment :-( 
> 
> Cheers! 
> 
> Joe

 

Links:
--
[1]
https://lists.yoctoproject.org/pipermail/yocto/2014-June/020223.html/
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-freescale] unable to get checksum SRC_URI file could not be found

[Daiane Angolini]

On Thu, Jul 10, 2014 at 2:16 AM, jags gediya  wrote:
> I am building yocto for freescale imx6sl evolution kit. For checking
> in source code on svn , i have deleted all .git and .gitignore from
> the meta directories. Then i have checkout the source code, and tried
> to build that. While building i am getting the warning
>
> Unable to get checksum for rfkill SRC_URI entry

is it an ERROR or an WARNING?

I know there is some warning regarding SRC_URI checksum from time to
time from master

> dont.call.git.rev-parse.on.parent.dir.patch: file could not be found
>
> What can be the reason of it?

Do you have more log messages to share?


> Will it create any problem?

it it´s warning, I don´t think so



Daiane
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH] oeqa/controllers/beaglebonetarget.py: fix deploy when kernel file is a broken link

[Corneliu Stoicescu]

Sometimes the uncompressed rootfs image contains boot/uImage but if it's a 
symlink, it seems broken from the master image's point of view.
Because [ -e /mnt/testrootfs/boot/uImage ] will return 1, it will proceed to 
copy the backup kernel file over it but cp ~/test-kernel 
/mnt/testrootfs/boot/uImage will also fail with:
cp: not writing through dangling symlink

Adding a new check here, if the boot/uImage is a link, leave it as is.

Signed-off-by: Corneliu Stoicescu 
---
 meta-yocto-bsp/lib/oeqa/controllers/beaglebonetarget.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta-yocto-bsp/lib/oeqa/controllers/beaglebonetarget.py 
b/meta-yocto-bsp/lib/oeqa/controllers/beaglebonetarget.py
index b2e9050..0f1aeb3 100644
--- a/meta-yocto-bsp/lib/oeqa/controllers/beaglebonetarget.py
+++ b/meta-yocto-bsp/lib/oeqa/controllers/beaglebonetarget.py
@@ -45,7 +45,7 @@ class BeagleBoneTarget(MasterImageHardwareTarget):
 'mount -L testrootfs /mnt/testrootfs',
 'rm -rf /mnt/testrootfs/*',
 'tar xvf ~/test-rootfs.%s -C /mnt/testrootfs' % 
self.image_fstype,
-'[ -e /mnt/testrootfs/boot/uImage ] || cp ~/test-kernel 
/mnt/testrootfs/boot/uImage',
+'[ -e /mnt/testrootfs/boot/uImage ] || [ -L 
/mnt/testrootfs/boot/uImage ] || cp ~/test-kernel /mnt/testrootfs/boot/uImage',
 ]
 
 for _, dtbfn in self.dtbs.iteritems():
-- 
1.8.3.2

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-freescale] yocto build taking too long time

[Daiane Angolini]

On Thu, Jul 10, 2014 at 6:10 AM, jags gediya  wrote:
> When i run command bitbake core-image-minimalm my build stops at
> NOTE: Preparing runqueue
> and after taking too long time it continues again.
> Is build checks anything at that point?


I have no idea what you´re talking about.

I can only say, yes, yocto takes forever, and this is the "normal" behavior.

In my core i5, core-image-minimal takes something like 30 minutes to
build from scratch


Daiane
>
> Thanks,
> Jags Gediya
> --
> ___
> meta-freescale mailing list
> meta-freesc...@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] How to select defconfig for kernel build with yocto/bitbake

[Bruce Ashfield]

On 14-07-11 04:55 AM, Dr. Markus Eich wrote:

I have tried the different task separately.

do_fetch works, no recursive link created
do_kernel_checkout works, no recursive link created
do_kernel_configme works, no recursive link created
do_compile works, no recursive link created
do_compile_kernelmodules works, no recursive link created
do_install works, no recursive link created


There's no recursive link, but is the arch-release link
created, but pointing somewhere else ?



do_package : Here it crashes. Th package subfolder is created and here
it creates the recursive link within the subfolder.

What does do_package do in detail? How can I further analyze the error.


Interesting. There's nothing custom in the kernel for packaging, and
nothing that I can think would be creating that symlink.

No good ideas at the moment, outside of pinpointing exactly where the
link is created, and when it transitions to a recursive one .. and
I'd do that by instrumentation.

Bruce



/Markus




On 10.07.2014 17:46, Bruce Ashfield wrote:

On 14-07-10 07:11 AM, Dr. Markus Eich wrote:

Thank you Bruce, that did the trick. But I am facing a new problem while
using bitbake for the build process.

I have checked to build the odroid kernel with a standard crosscompiler
tool chain and it works without any problems.

When I do the same with the bitbake toolchain (bitbake virtual/kernel),
it somehow creates a recursive link in the folder

package/usr/src/kernel/drivers/gpu/arm/mali400/ump/arch/arch-release ->
arch-release

This causes a crash in the build system.

Compilation runs fine though. This error seems to be within do_package.
I have removed the link, but somehow it is created automatically.

Any ideas?


Nothing off the top of my head. That link would be created by the kernel
build, and not by bitbake or the oe-core kernel build classes.

I'd start by looking at the kernel's makefiles and seeing where the
link is being created.

Do specific tasks work ? i.e. is that happening during unpack/patch, or
during compilation.

Bruce



/Markus



On 09.07.2014 14:44, Bruce Ashfield wrote:

On 14-07-09 05:38 AM, Dr. Markus Eich wrote:

Dear all,

I work on the process to compile odroid xu kernel with yocto/bitbake

In the kernel sources (from hardkernel) I have the corresponding
defconfig file, i.e. in the git folder
/arch/arm/configs/odroidxu_ubuntu_defconfig.

How can I tell bitbake in my recipe to use
"odroidxu_ubuntu_defconfig"?


To trigger the oe-core kernel processing to use the defconfig, you need
to put that defconfig in your SRC_URI.

Which means you should grab a copy of that from the kernel tree, and
in the same directory structure as your kernel recipe.

See meta-skeleton/recipes-kernel/linux/linux-yocto-custom.bb for an
example.

Cheers,

Bruce




My recipe looks as follow:

===
require recipes-kernel/linux/linux-yocto.inc

KERNEL_IMAGETYPE = "uImage"

COMPATIBLE_MACHINE = "odroid-xu"

LINUX_VERSION = "3.4.91"
LINUX_VERSION_EXTENSION = "-custom"

FILESEXTRAPATHS_prepend := "${THISDIR}/linux-hardkernel-3.4:"

S = "${WORKDIR}/git"

# from where to fetch the kernel
KERNEL_REPO_OWNER ??= "hardkernel"
KERNEL_REPO_URI ??= "git://github.com/${KERNEL_REPO_OWNER}/linux.git"
KBRANCH = "odroidxu-3.4.y"

SRCREV = "${AUTOREV}"

KV = "3.4.91"
PV = "${KV}+gitr${SRCPV}"
LOCALVERSION ?= ""


SRC_URI = " \
   ${KERNEL_REPO_URI};nocheckout=1;branch=${KBRANCH} \
"

PACKAGES =+ "kernel-headers"
FILES_kernel-headers = "${exec_prefix}/src/linux*"
===

Cheers,

Markus














--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-freescale] yocto build taking too long time

[Trevor Woerner]

On 07/11/14 09:46, Daiane Angolini wrote:
> In my core i5, core-image-minimal takes something like 30 minutes to
> build from scratch

And that's probably assuming all your sources are already downloaded to
your build machine! The amount of time it takes to complete a fresh
build on a machine with no previously-downloaded sources will be
constrained by that machine's Internet connection speed.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Is it possible to prevent a package from updating the shared state cache?

[Patrick Doyle]

For anybody (such as myself) who might stumble across this thread later…

I just wanted to build a recipe without tainting my sstate cache.  (I
wanted to build from a different bzr repository and didn't want to
"contaminate" my sstate cache, or even worse, confuse it with a
different version of revsion 1234 from the other repository).  So I
went with:

Run the cleansstate task
Bitbake my one particular recipe
Copy the generated output for the particular test I wanted to run to
the particular test system on which I wanted to run it.
Run the cleansstate task again to clean up after myself.

I'm open to suggestions for better ways to accomplish this.

--wpd


On Thu, Jul 10, 2014 at 3:00 PM, Patrick Doyle  wrote:
> Suppose I always wanted Yocto to process a particular recipe local to
> a project and never to consult the shared state for that recipe.  Is
> there some way to mark a recipe to do this?
>
> --wpd
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Is it possible to prevent a package from updating the shared state cache?

[Burton, Ross]

On 11 July 2014 17:00, Patrick Doyle  wrote:
> (I
> wanted to build from a different bzr repository and didn't want to
> "contaminate" my sstate cache, or even worse, confuse it with a
> different version of revsion 1234 from the other repository)

Ouch, I'd forgotten that bzr revisions were not unique.  Is there a
way of making revisions globally unique, and should we switch the
packages to use those instead of local revisions?

Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Is it possible to prevent a package from updating the shared state cache?

[Patrick Doyle]

On Fri, Jul 11, 2014 at 3:19 PM, Burton, Ross  wrote:
> On 11 July 2014 17:00, Patrick Doyle  wrote:
>> (I
>> wanted to build from a different bzr repository and didn't want to
>> "contaminate" my sstate cache, or even worse, confuse it with a
>> different version of revsion 1234 from the other repository)
>
> Ouch, I'd forgotten that bzr revisions were not unique.  Is there a
> way of making revisions globally unique, and should we switch the
> packages to use those instead of local revisions?

Ahhh… Bazaar does use globally unique identifiers internally
(according to http://doc.bazaar.canonical.com/developers/overview.html).
I didn't think about that when I asked my question.  I just assumed
that the sstate cache was based on revno rather than guid.

I would expect that the guid should be available via bzrlib, if you
use that for the sstate cache.  It is also available (I have now
learned) via "bzr version-info" for a given branch.

--wpd
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] CyaSSL library now available for use in Yocto Project

[Leah]

CyaSSL lightweight SSL library is now available for use in Yocto Project
images! Check out our layer which we built and tested using the
Minnowboard:
http://yassl.com/yaSSL/Blog/Entries/2014/7/11_meta-wolfssl_Layer_for_Yocto_and_OpenEmbedded.html


-- 

Leah Thompson
www.wolfssl.com
l...@wolfssl.com
406-570-1389
Skype: lchristina26
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [ANNOUNCEMENT] Intel(R) meta-intel 1.0 BSPs for Yocto Project "daisy" 1.6.1 Released

[Flanagan, Elizabeth]

All,

The meta-intel 1.0 layer for the Yocto Projects 1.6.1 "daisy" release
and board support packages are now available for download.

meta-intel
--
repo: git://git.yoctoproject.org/meta-intel
branch: daisy
tag: 1.0-daisy-1.6.1
hash: 50d1afd52a612dbf9a190bf869c37253864886cc
download: 
http://downloads.yoctoproject.org/releases/yocto/yocto-1.6.1/meta-intel-1.0-daisy-1.6.1.tar.bz
md5sum: 32c6a5293cc499e190a8cc6c0235126b


BSP downloads
---

Intel® Common Core BSP (intel-core2-32 and intel-corei7-64):
https://www.yoctoproject.org/download/intel%C2%AE-common-core-bsp-intel-core2-32-and-intel-corei7-64

Intel® Atom™ E640T Processor with Intel EG20T Controller Hub
Development Kit (Queens Bay) with IEMGD or Open Source Graphics (Fish
River Island 2):
https://www.yoctoproject.org/download/intel%C2%AE-atom%E2%84%A2-e640t-processor-intel-eg20t-controller-hub-development-kit-queens-bay-iemgd-or

Intel® Xeon® C5500/C3500 Series Processors With Intel 3420 PCH Chipset
(Jasper Forest):
https://www.yoctoproject.org/download/intel%C2%AE-xeon%C2%AE-c5500c3500-series-processors-intel-3420-pch-chipset-jasper-forest-1

Next Unit of Computing Kit DC3217IYE (nuc):
https://www.yoctoproject.org/download/next-unit-computing-kit-dc3217iye-nuc-1

Intel® 2nd Generation Core™ Platforms: Core i3, i5, i7 (Sandy Bridge):
https://www.yoctoproject.org/download/intel%C2%AE-2nd-generation-core%E2%84%A2-platforms-core-i3-i5-i7-sandy-bridge-1

Intel® Xeon® processor E5-2600 and E5-2400 families with Intel®
C604/C602-J Chipset (Romley-EP/EN Platform):
https://www.yoctoproject.org/download/intel%C2%AE-xeon%C2%AE-processor-e5-2600-and-e5-2400-families-intel%C2%AE-c604c602-j-chipset-romley-epen

Intel® Atom® Processor E3800 with Open Source Graphics (Valley Island):
https://www.yoctoproject.org/download/intel%C2%AE-atom%C2%AE-processor-e3800-open-source-graphics-valley-island-0

Intel® Atom™ Z5xx Processor With Intel US15W Controller Hub (eMenlow):
https://www.yoctoproject.org/download/intel%C2%AE-atom%E2%84%A2-z5xx-processor-intel-us15w-controller-hub-emenlow-1

Intel® Xeon® Processor E5-2600 and E5-2400 Series with Intel®
Communications Chipset 89xx Series (Crystal Forest/Highland Forest)
https://www.yoctoproject.org/download/intel%C2%AE-xeon%C2%AE-processor-e5-2600-and-e5-2400-series-intel%C2%AE-communications-chipset-89xx-seri-0

Intel® Atom™ E6xx Processor With Intel EG20T Controller Hub
Development Kit (Crown Bay):
https://www.yoctoproject.org/download/intel%C2%AE-atom%E2%84%A2-e6xx-processor-intel-eg20t-controller-hub-development-kit-crown-bay-1

Intel® Atom® Processor C2000 (Mohon Peak):
https://www.yoctoproject.org/download/intel%C2%AE-atom%C2%AE-processor-c2000-mohon-peak-0

-- 
Elizabeth Flanagan
Intel Corp.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] CyaSSL library now available for use in Yocto Project

[Khem Raj]

On Fri, Jul 11, 2014 at 2:47 PM, Leah  wrote:
> CyaSSL lightweight SSL library is now available for use in Yocto Project
> images! Check out our layer which we built and tested using the Minnowboard:
> http://yassl.com/yaSSL/Blog/Entries/2014/7/11_meta-wolfssl_Layer_for_Yocto_and_OpenEmbedded.html
>

thanks. It seems you need to submit this layer for indexing in
http://layers.openembedded.org/
currently it has git://github.com/cconlon/meta-yassl.git  listed which
seems to be old version ?

>
> --
>
> Leah Thompson
> www.wolfssl.com
> l...@wolfssl.com
> 406-570-1389
> Skype: lchristina26
>
>
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto