date:20210524

Re: [yocto] ERROR: ParseError at .../bbb-yocto-gatesgarth/meta-bbb/images/console-image.bb:4: Could not include required file images/basic-dev-image.bb

2021-05-24 Thread Zoran

> IIRC, dhcp-server has been replaced by kea, check on that side maybe.
> Read the migration notes, pretty sure the kea thing is listed there.

Done. All fixed according to Quentin's recommendations.

https://github.com/ZoranStojsavljevic/bbb-yocto/blob/master/yocto-setup.sh#L114
https://github.com/ZoranStojsavljevic/bbb-yocto/blob/master/bbb-releases/bbb-gatesgarth/local.conf#L18
https://github.com/ZoranStojsavljevic/bbb-yocto/blob/master/bbb-releases/bbb-gatesgarth/local.conf_kernel#L26

Added to README.md .
https://github.com/ZoranStojsavljevic/bbb-yocto/blob/master/README.md

Thank you,
Zoran
___

On Mon, May 24, 2021 at 9:27 PM Quentin Schulz  wrote:
>
>
>
> On May 24, 2021 2:13:57 PM UTC, Zoran  wrote:
> >Or, maybe, now the DHCP is included in the releases by default?
> >
> >Thank you,
> >Zoran
> >___
> >
> >On Mon, May 24, 2021 at 4:09 PM Zoran Stojsavljevic
> > wrote:
> >>
> >> Hello Quentin,
> >>
> >> Thank you for finding the bug. It was in front of my eyes (I print all
> >> the layers at the end of setup, but I missed to compare bb-layers from
> >> dunfell with bb-layers from gatesgarth).
> >>
> >> I should do better. With regards to testing thinking. ;-)
> >> ___
> >>
> >> Now, there are other bugs (I should say, new features introduced).
> >>
> >> Loading cache: 100%
> >> ||
> >> Time: 0:00:00
> >> Loaded 3533 entries from dependency cache.
> >> Parsing recipes: 100%
> >> |##|
> >> Time: 0:00:00
> >> Parsing of 2311 .bb files complete (2309 cached, 2 parsed). 3535
> >> targets, 121 skipped, 1 masked, 0 errors.
> >> NOTE: Resolving any missing task queue dependencies
> >> ERROR: Nothing RPROVIDES 'dhcp-libs' (but
> >> /home/vuser/projects_yocto/bbb-yocto-gatesgarth/poky/meta/recipes-core/images/core-image-minimal.bb
> >> RDEPENDS on or otherwise requires it)
> >> NOTE: Runtime target 'dhcp-libs' is unbuildable, removing...
> >> Missing or unbuildable dependency chain was: ['dhcp-libs']
> >> ERROR: Nothing RPROVIDES 'dhcp-server' (but
> >> /home/vuser/projects_yocto/bbb-yocto-gatesgarth/poky/meta/recipes-core/images/core-image-minimal.bb
> >> RDEPENDS on or otherwise requires it)
> >> NOTE: Runtime target 'dhcp-server' is unbuildable, removing...
> >> Missing or unbuildable dependency chain was: ['dhcp-server']
> >> ERROR: Nothing RPROVIDES 'dhcp-server-config' (but
> >> /home/vuser/projects_yocto/bbb-yocto-gatesgarth/poky/meta/recipes-core/images/core-image-minimal.bb
> >> RDEPENDS on or otherwise requires it)
> >> NOTE: Runtime target 'dhcp-server-config' is unbuildable, removing...
> >> Missing or unbuildable dependency chain was: ['dhcp-server-config']
> >> ERROR: Nothing RPROVIDES 'dhcp-client' (but
> >> /home/vuser/projects_yocto/bbb-yocto-gatesgarth/poky/meta/recipes-core/images/core-image-minimal.bb
> >> RDEPENDS on or otherwise requires it)
> >> NOTE: Runtime target 'dhcp-client' is unbuildable, removing...
> >> Missing or unbuildable dependency chain was: ['dhcp-client']
> >> ERROR: Nothing RPROVIDES 'dhcp-relay' (but
> >> /home/vuser/projects_yocto/bbb-yocto-gatesgarth/poky/meta/recipes-core/images/core-image-minimal.bb
> >> RDEPENDS on or otherwise requires it)
> >> NOTE: Runtime target 'dhcp-relay' is unbuildable, removing...
> >> Missing or unbuildable dependency chain was: ['dhcp-relay']
> >> ERROR: Nothing RPROVIDES 'dhcp-omshell' (but
> >> /home/vuser/projects_yocto/bbb-yocto-gatesgarth/poky/meta/recipes-core/images/core-image-minimal.bb
> >> RDEPENDS on or otherwise requires it)
> >> NOTE: Runtime target 'dhcp-omshell' is unbuildable, removing...
> >> Missing or unbuildable dependency chain was: ['dhcp-omshell']
> >>
> >> Seems that this line in local.conf got severely changed, or most
> >> likely the DHCP package version/handling got changed:
> >>
> >> CORE_IMAGE_EXTRA_INSTALL_append = "openssh dhcp-libs dhcp-server
> >> dhcp-server-config dhcp-client dhcp-relay dhcp-omshell cmake
> >> libsocketcan nfs-utils rt-tests strace procps
> >> packagegroup-core-buildessential "
> >>
> >> The question is: what should I include in the
> >> CORE_IMAGE_EXTRA_INSTALL_append for the DHCP package for gatesgarth
> >> and later releases???
> >>
>
> If I remember correctly, dhcp-server has been replaced by kea, check on that 
> side maybe. Read the migration notes, pretty sure the kea thing is listed 
> there.
>
> Cheers,
> Quentin
>
> >> Thank you,
> >> Zoran
> >> ___
> >>
> >> On Mon, May 24, 2021 at 2:24 PM Quentin Schulz  wrote:
> >> >
> >> > Hi Zoran,
> >> >
> >> > On May 24, 2021 8:27:58 AM UTC, Zoran  
> >> > wrote:
> >> > >Hello again to YOCTO Folks,
> >> > >
> >> > >Here is another blunder I ran into while fixing a yocto-setup.sh script:
> >> > >https://github.com/ZoranStojsavljevic/bbb-yocto/blob/master/yocto-setup.sh
> >> > >
> >> > >While executing $  . ./yocto-setup.sh dunfell,

[yocto] M+ & H bugs with Milestone Movements WW21

2021-05-24 Thread Stephen Jolley

All,

YP M+ or high bugs which moved to a new milestone in WW21 are listed below: 


Priority

Bug ID

Short Description

Changer

Owner

Was

Became


Medium+

  13190

RRS cannot handle multiple recipes with same PN

randy.macl...@windriver.com

bluelightn...@bluelightning.org

3.3 M3

3.4 M1


 

  13550

username/password specified to gitsm:// does not get propagated to submodules

randy.macl...@windriver.com

tony.tascio...@windriver.com

3.3 M3

3.4 M2


 

  13566

Write tests for multiconfig files in layers and document

randy.macl...@windriver.com

mostthings...@gmail.com

3.3 M3

3.4 M2


 

  13808

do_task[noexec] = "" marks task noexec, which is inconsistent with docs

randy.macl...@windriver.com

mostthings...@gmail.com

3.3 M3

3.4 M2


 

  13903

npmsw fetcher fails if multiple recipes have common npm packages

randy.macl...@windriver.com

jeanmarie.lemeta...@gmail.com

3.3 M3

3.4 M2


 

  13954

Invalid layerindex data causing backtrace in `bitbake-layers layerindex-fetch`

randy.macl...@windriver.com

bluelightn...@bluelightning.org

3.3 M3

3.4 M2


 

  14040

recipetool: creating binary recipe from upstream git repo without explicit PV 
causes circular reference in SRC_URI

randy.macl...@windriver.com

mostthings...@gmail.com

3.3 M3

3.4 M3

Thanks, 

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com  

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#53635): https://lists.yoctoproject.org/g/yocto/message/53635
Mute This Topic: https://lists.yoctoproject.org/mt/83068178/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Enhancements/Bugs closed WW21!

2021-05-24 Thread Stephen Jolley

All,

The below were the owners of enhancements or bugs closed during the last
week!


Who

Count


randy.macl...@windriver.com

7


richard.pur...@linuxfoundation.org

3


mhalst...@linuxfoundation.org

1


alexandre.bell...@bootlin.com

1


chee.yang@intel.com

1


Grand Total

13

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#53634): https://lists.yoctoproject.org/g/yocto/message/53634
Mute This Topic: https://lists.yoctoproject.org/mt/83068157/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Current high bug count owners for Yocto Project 3.4

2021-05-24 Thread Stephen Jolley

All,

Below is the list as of top 50 bug owners as of the end of WW21 of who have
open medium or higher bugs and enhancements against YP 3.4.   There are 110
possible work days left until the final release candidates for YP 3.4 needs
to be released.


Who

Count


r...@burtonini.com

31


richard.pur...@linuxfoundation.org

29


david.re...@windriver.com

22


bruce.ashfi...@gmail.com

20


michael.opdenac...@bootlin.com

19


trevor.gamb...@windriver.com

12


bluelightn...@bluelightning.org

12


timothy.t.orl...@intel.com

11


akuster...@gmail.com

11


jpewhac...@gmail.com

11


randy.macl...@windriver.com

10


sakib.sa...@windriver.com

9


kai.k...@windriver.com

8


hongxu@windriver.com

7


qi.c...@windriver.com

6


mingli...@windriver.com

6


chee.yang@intel.com

5


raj.k...@gmail.com

5


tony.tascio...@windriver.com

4


yi.z...@windriver.com

4


alexandre.bell...@bootlin.com

3


mostthings...@gmail.com

3


jon.ma...@arm.com

2


nicolas.deche...@linaro.org

2


jae...@xilinx.com

2


ydir...@free.fr

2


ms...@mvista.com

2


pokyli...@reliableembeddedsystems.com

2


alejan...@enedino.org

2


yf...@uwaterloo.ca

2


liezhi.y...@windriver.com

1


stacygaikov...@gmail.com

1


dl...@gmx.de

1


open.sou...@oleksandr-kravchuk.com

1


yoctoproj...@cookiesoft.de

1


mark.ha...@windriver.com

1


kexin@windriver.com

1


kerg...@gmail.com

1


shac...@vdoo.com

1


martin.ja...@gmail.com

1


mister...@web.de

1


diego.sue...@arm.com

1


john.kaldas.e...@gmail.com

1


nathan.du...@arm.com

1


devendra.tew...@gmail.com

1


naveen.kumar.sa...@intel.com

1


prabin...@arm.com

1


saul.w...@windriver.com

1


mhalst...@linuxfoundation.org

1


jeanmarie.lemeta...@gmail.com

1


thomas.per...@bootlin.com

1

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#53633): https://lists.yoctoproject.org/g/yocto/message/53633
Mute This Topic: https://lists.yoctoproject.org/mt/83068068/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

2021-05-24 Thread Stephen Jolley

All,

 

The triage team is starting to try and collect up and classify bugs which a
newcomer to the project would be able to work on in a way which means people
can find them. They're being listed on the triage page under the appropriate
heading:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs  Also please
review:
https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded and
how to create a bugzilla account at:

https://bugzilla.yoctoproject.org/createaccount.cgi

The idea is these bugs should be straight forward for a person to help work
on who doesn't have deep experience with the project.  If anyone can help,
please take ownership of the bug and send patches!  If anyone needs
help/advice there are people on irc who can likely do so, or some of the
more experienced contributors will likely be happy to help too.

 

Also, the triage team meets weekly and does its best to handle the bugs
reported into the Bugzilla. The number of people attending that meeting has
fallen, as have the number of people available to help fix bugs. One of the
things we hear users report is they don't know how to help. We (the triage
team) are therefore going to start reporting out the currently 354
unassigned or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.  Bugs are split into two types, "true bugs" where things don't
work as they should and "enhancements" which are features we'd want to add
to the system.  There are also roughly four different "priority" classes
right now, "3.2", "3.3, "3.99" and "Future", the more pressing/urgent issues
being in "3.2" and then "3.3".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me (sjolley.yp...@gmail.com
 ) an e-mail with the bug number you would
like and I will assign it to you (please make sure you have a Bugzilla
account).  The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage_Archive#Unassigned_or_Newcomer
_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#53632): https://lists.yoctoproject.org/g/yocto/message/53632
Mute This Topic: https://lists.yoctoproject.org/mt/83068028/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto-announce] [ANNOUNCEMENT] Yocto Project 3.3.1 (hardknott-25.0.1) is Released

2021-05-24 Thread Vineela


Generating announcement for point release 3.3.1.

We are pleased to announce the Yocto Project 3.3.1 (hardknott-25.0.1) Release 
is now available for download.

http://downloads.yoctoproject.org/releases/yocto/yocto-3.3.1/poky-hardknott-25.0.1.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-3.3.1/poky-hardknott-25.0.1.tar.bz2

A gpg signed version of these release notes is available at:

http://downloads.yoctoproject.org/releases/yocto/yocto-3.3.1/RELEASENOTES

Full Test Report:

http://downloads.yoctoproject.org/releases/yocto/yocto-3.3.1/testreport.txt

Thank you for everyone's contributions to this release.


Vineela Tummalapalli

Yocto Project Build and Release

vineela.tummalapa...@intel.com

--
yocto-3.3.1 Release Notes
--

--
Repositories/Downloads
--

Repository Name: poky
Repository Location: https://git.yoctoproject.org/git/poky
Branch: hardknott
Tag: yocto-3.3.1
Git Revision: 05a8aad57ce250b124db16705acec557819905ae
Release Artefact: poky-hardknott-25.0.1
sha: 409b92d819f0c6e928b37bcc7cc4e80e5f27aa94748dcb479e325a4559c391c2
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-3.3.1/poky-hardknott-25.0.1.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-3.3.1/poky-hardknott-25.0.1.tar.bz2

Repository Name: openembedded-core
Repository Location: https://git.openembedded.org/openembedded-core
Branch: hardknott
Tag: 2021-04.1-hardknott
Git Revision: efce6334bf122a64f63d46c1c04e3dbffe298c51
Release Artefact: oecore-hardknott-25.0.1
sha: d53cdc060784ee7c86853b3b8120d6b3d0b445098cfcd27c939f303f9075262f
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-3.3.1/oecore-hardknott-25.0.1.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-3.3.1/oecore-hardknott-25.0.1.tar.bz2

Repository Name: meta-mingw
Repository Location: https://git.yoctoproject.org/git/meta-mingw
Branch: hardknott
Tag: yocto-3.3.1
Git Revision: 422b96cb2b6116442be1f40dfb5bd77447d1219e
Release Artefact: meta-mingw-hardknott-25.0.1
sha: 89bce008a93d4717bca4069c1fd0004d88bf39e8a8098eb1e8376bc7521a600f
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-3.3.1/meta-mingw-hardknott-25.0.1.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-3.3.1/meta-mingw-hardknott-25.0.1.tar.bz2

Repository Name: meta-gplv2
Repository Location: https://git.yoctoproject.org/git/meta-gplv2
Branch: hardknott
Tag: yocto-3.3.1
Git Revision: 9e119f333cc8f53bd3cf64326f826dbc6ce3db0f
Release Artefact: meta-gplv2-hardknott-25.0.1
sha: 988a222f13a9a87adf723cb86bd7db2648b3303e15bb3bac2d73e89f3faa547f
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-3.3.1/meta-gplv2-hardknott-25.0.1.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-3.3.1/meta-gplv2-hardknott-25.0.1.tar.bz2

Repository Name: bitbake
Repository Location: https://git.openembedded.org/bitbake
Branch: 1.50
Tag: 2021-04.1-hardknott
Git Revision: b67476d4758915db7a5d9f58bc903ae7501a1774
Release Artefact: bitbake-hardknott-25.0.1
sha: 3203a3c80f7ac749b1436b67b25733dbbe09b7ce9b32715a9f2fcd6bc24ec718
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-3.3.1/bitbake-hardknott-25.0.1.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-3.3.1/bitbake-hardknott-25.0.1.tar.bz2

Repository Name: yocto-docs
Repository Location: https://git.yoctoproject.org/git/yocto-docs
Branch: hardknott
Tag: yocto-3.3.1
Git Revision:eb19a2b5687f11c22c7fc26d3efabbf65adb572e

---
Contributors
--
Alejandro Enedino Hernandez Samaniego
Alexander Kanavin
Anders Wallin
Anthony Bagwell
Anuj Mittal
Bruce Ashfield
Changqing Li
Chen Qi
Christophe Chapuis
Daniel Ammann
Douglas Royds
Gavin Li
He Zhe
hongxu
Jonas Höppner
Jon Mason
Jose Quaresma
Joshua Watt
Kai Kang
Kevin Hao
Khairul Rohaizzat Jamaluddin
Khem Raj
Konrad Weihmann
Michael Opdenacker
Mikko Rapeli
Mingli Yu
Nicolas Dechesne
Niels Avonds
Paul Eggleton
Peter Budny
Peter Kjellerstedt
Quentin Schulz
Randy MacLeod
Reto Schneider
Richard Purdie
Romain Naour
Ross Burton
Sakib Sajal
Sangeeta Jain
Saul Wold
Stefan Ghinea
Stephen Jolley
Trevor Gamblin
Ulrich Ölmann
Vinícius Ossanes Aquino
wangmy
Wes Lindauer
Yanfei Xu
Yann Dirson
Yi Fan Yu
Yi Zhao
zhengruoqin

---
Known Issues
---
An intermittent systemtap issue occurred on arm during testing.

---
Security Fixes
---
db: update CVE_PRODUCT
qemu: fix CVE-2021-3392
qemu: fix CVE-2021-20263
qemu: fix CVE-2020-27821
xserver-xorg: fix CVE-2021-3472
rsync: fix CVE-2020-14387
glib-2.0: fix CVE-2021-28153
qemu: fix CVE-2021-20257
qemu: fix CVE-2021-3416
qemu: fix CVE-2021-3409
qemu: fix CVE-2021-20221
qemu: fix CVE-2020-29443
qemu: fix CVE-2021-20181
gdk-pixbuf: fix CVE-2021-20240
cairo: fix CVE-2020-35492
wpa-supplicant: fix CVE-2021-30004
busybox: fix CVE-2021-28831
qemu: Fix CVE-2020-35517


---
Fixes

[yocto] [ANNOUNCEMENT] Yocto Project 3.3.1 (hardknott-25.0.1) is Released

2021-05-24 Thread Vineela


Generating announcement for point release 3.3.1.

We are pleased to announce the Yocto Project 3.3.1 (hardknott-25.0.1) Release 
is now available for download.

http://downloads.yoctoproject.org/releases/yocto/yocto-3.3.1/poky-hardknott-25.0.1.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-3.3.1/poky-hardknott-25.0.1.tar.bz2

A gpg signed version of these release notes is available at:

http://downloads.yoctoproject.org/releases/yocto/yocto-3.3.1/RELEASENOTES

Full Test Report:

http://downloads.yoctoproject.org/releases/yocto/yocto-3.3.1/testreport.txt

Thank you for everyone's contributions to this release.


Vineela Tummalapalli

Yocto Project Build and Release

vineela.tummalapa...@intel.com

--
yocto-3.3.1 Release Notes
--

--
Repositories/Downloads
--

Repository Name: poky
Repository Location: https://git.yoctoproject.org/git/poky
Branch: hardknott
Tag: yocto-3.3.1
Git Revision: 05a8aad57ce250b124db16705acec557819905ae
Release Artefact: poky-hardknott-25.0.1
sha: 409b92d819f0c6e928b37bcc7cc4e80e5f27aa94748dcb479e325a4559c391c2
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-3.3.1/poky-hardknott-25.0.1.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-3.3.1/poky-hardknott-25.0.1.tar.bz2

Repository Name: openembedded-core
Repository Location: https://git.openembedded.org/openembedded-core
Branch: hardknott
Tag: 2021-04.1-hardknott
Git Revision: efce6334bf122a64f63d46c1c04e3dbffe298c51
Release Artefact: oecore-hardknott-25.0.1
sha: d53cdc060784ee7c86853b3b8120d6b3d0b445098cfcd27c939f303f9075262f
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-3.3.1/oecore-hardknott-25.0.1.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-3.3.1/oecore-hardknott-25.0.1.tar.bz2

Repository Name: meta-mingw
Repository Location: https://git.yoctoproject.org/git/meta-mingw
Branch: hardknott
Tag: yocto-3.3.1
Git Revision: 422b96cb2b6116442be1f40dfb5bd77447d1219e
Release Artefact: meta-mingw-hardknott-25.0.1
sha: 89bce008a93d4717bca4069c1fd0004d88bf39e8a8098eb1e8376bc7521a600f
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-3.3.1/meta-mingw-hardknott-25.0.1.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-3.3.1/meta-mingw-hardknott-25.0.1.tar.bz2

Repository Name: meta-gplv2
Repository Location: https://git.yoctoproject.org/git/meta-gplv2
Branch: hardknott
Tag: yocto-3.3.1
Git Revision: 9e119f333cc8f53bd3cf64326f826dbc6ce3db0f
Release Artefact: meta-gplv2-hardknott-25.0.1
sha: 988a222f13a9a87adf723cb86bd7db2648b3303e15bb3bac2d73e89f3faa547f
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-3.3.1/meta-gplv2-hardknott-25.0.1.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-3.3.1/meta-gplv2-hardknott-25.0.1.tar.bz2

Repository Name: bitbake
Repository Location: https://git.openembedded.org/bitbake
Branch: 1.50
Tag: 2021-04.1-hardknott
Git Revision: b67476d4758915db7a5d9f58bc903ae7501a1774
Release Artefact: bitbake-hardknott-25.0.1
sha: 3203a3c80f7ac749b1436b67b25733dbbe09b7ce9b32715a9f2fcd6bc24ec718
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-3.3.1/bitbake-hardknott-25.0.1.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-3.3.1/bitbake-hardknott-25.0.1.tar.bz2

Repository Name: yocto-docs
Repository Location: https://git.yoctoproject.org/git/yocto-docs
Branch: hardknott
Tag: yocto-3.3.1
Git Revision:eb19a2b5687f11c22c7fc26d3efabbf65adb572e

---
Contributors
--
Alejandro Enedino Hernandez Samaniego
Alexander Kanavin
Anders Wallin
Anthony Bagwell
Anuj Mittal
Bruce Ashfield
Changqing Li
Chen Qi
Christophe Chapuis
Daniel Ammann
Douglas Royds
Gavin Li
He Zhe
hongxu
Jonas Höppner
Jon Mason
Jose Quaresma
Joshua Watt
Kai Kang
Kevin Hao
Khairul Rohaizzat Jamaluddin
Khem Raj
Konrad Weihmann
Michael Opdenacker
Mikko Rapeli
Mingli Yu
Nicolas Dechesne
Niels Avonds
Paul Eggleton
Peter Budny
Peter Kjellerstedt
Quentin Schulz
Randy MacLeod
Reto Schneider
Richard Purdie
Romain Naour
Ross Burton
Sakib Sajal
Sangeeta Jain
Saul Wold
Stefan Ghinea
Stephen Jolley
Trevor Gamblin
Ulrich Ölmann
Vinícius Ossanes Aquino
wangmy
Wes Lindauer
Yanfei Xu
Yann Dirson
Yi Fan Yu
Yi Zhao
zhengruoqin

---
Known Issues
---
An intermittent systemtap issue occurred on arm during testing.

---
Security Fixes
---
db: update CVE_PRODUCT
qemu: fix CVE-2021-3392
qemu: fix CVE-2021-20263
qemu: fix CVE-2020-27821
xserver-xorg: fix CVE-2021-3472
rsync: fix CVE-2020-14387
glib-2.0: fix CVE-2021-28153
qemu: fix CVE-2021-20257
qemu: fix CVE-2021-3416
qemu: fix CVE-2021-3409
qemu: fix CVE-2021-20221
qemu: fix CVE-2020-29443
qemu: fix CVE-2021-20181
gdk-pixbuf: fix CVE-2021-20240
cairo: fix CVE-2020-35492
wpa-supplicant: fix CVE-2021-30004
busybox: fix CVE-2021-28831
qemu: Fix CVE-2020-35517


---
Fixes

Re: [yocto] ERROR: ParseError at .../bbb-yocto-gatesgarth/meta-bbb/images/console-image.bb:4: Could not include required file images/basic-dev-image.bb

2021-05-24 Thread Quentin Schulz



On May 24, 2021 2:13:57 PM UTC, Zoran  wrote:
>Or, maybe, now the DHCP is included in the releases by default?
>
>Thank you,
>Zoran
>___
>
>On Mon, May 24, 2021 at 4:09 PM Zoran Stojsavljevic
> wrote:
>>
>> Hello Quentin,
>>
>> Thank you for finding the bug. It was in front of my eyes (I print all
>> the layers at the end of setup, but I missed to compare bb-layers from
>> dunfell with bb-layers from gatesgarth).
>>
>> I should do better. With regards to testing thinking. ;-)
>> ___
>>
>> Now, there are other bugs (I should say, new features introduced).
>>
>> Loading cache: 100%
>> ||
>> Time: 0:00:00
>> Loaded 3533 entries from dependency cache.
>> Parsing recipes: 100%
>> |##|
>> Time: 0:00:00
>> Parsing of 2311 .bb files complete (2309 cached, 2 parsed). 3535
>> targets, 121 skipped, 1 masked, 0 errors.
>> NOTE: Resolving any missing task queue dependencies
>> ERROR: Nothing RPROVIDES 'dhcp-libs' (but
>> /home/vuser/projects_yocto/bbb-yocto-gatesgarth/poky/meta/recipes-core/images/core-image-minimal.bb
>> RDEPENDS on or otherwise requires it)
>> NOTE: Runtime target 'dhcp-libs' is unbuildable, removing...
>> Missing or unbuildable dependency chain was: ['dhcp-libs']
>> ERROR: Nothing RPROVIDES 'dhcp-server' (but
>> /home/vuser/projects_yocto/bbb-yocto-gatesgarth/poky/meta/recipes-core/images/core-image-minimal.bb
>> RDEPENDS on or otherwise requires it)
>> NOTE: Runtime target 'dhcp-server' is unbuildable, removing...
>> Missing or unbuildable dependency chain was: ['dhcp-server']
>> ERROR: Nothing RPROVIDES 'dhcp-server-config' (but
>> /home/vuser/projects_yocto/bbb-yocto-gatesgarth/poky/meta/recipes-core/images/core-image-minimal.bb
>> RDEPENDS on or otherwise requires it)
>> NOTE: Runtime target 'dhcp-server-config' is unbuildable, removing...
>> Missing or unbuildable dependency chain was: ['dhcp-server-config']
>> ERROR: Nothing RPROVIDES 'dhcp-client' (but
>> /home/vuser/projects_yocto/bbb-yocto-gatesgarth/poky/meta/recipes-core/images/core-image-minimal.bb
>> RDEPENDS on or otherwise requires it)
>> NOTE: Runtime target 'dhcp-client' is unbuildable, removing...
>> Missing or unbuildable dependency chain was: ['dhcp-client']
>> ERROR: Nothing RPROVIDES 'dhcp-relay' (but
>> /home/vuser/projects_yocto/bbb-yocto-gatesgarth/poky/meta/recipes-core/images/core-image-minimal.bb
>> RDEPENDS on or otherwise requires it)
>> NOTE: Runtime target 'dhcp-relay' is unbuildable, removing...
>> Missing or unbuildable dependency chain was: ['dhcp-relay']
>> ERROR: Nothing RPROVIDES 'dhcp-omshell' (but
>> /home/vuser/projects_yocto/bbb-yocto-gatesgarth/poky/meta/recipes-core/images/core-image-minimal.bb
>> RDEPENDS on or otherwise requires it)
>> NOTE: Runtime target 'dhcp-omshell' is unbuildable, removing...
>> Missing or unbuildable dependency chain was: ['dhcp-omshell']
>>
>> Seems that this line in local.conf got severely changed, or most
>> likely the DHCP package version/handling got changed:
>>
>> CORE_IMAGE_EXTRA_INSTALL_append = "openssh dhcp-libs dhcp-server
>> dhcp-server-config dhcp-client dhcp-relay dhcp-omshell cmake
>> libsocketcan nfs-utils rt-tests strace procps
>> packagegroup-core-buildessential "
>>
>> The question is: what should I include in the
>> CORE_IMAGE_EXTRA_INSTALL_append for the DHCP package for gatesgarth
>> and later releases???
>>

If I remember correctly, dhcp-server has been replaced by kea, check on that 
side maybe. Read the migration notes, pretty sure the kea thing is listed there.

Cheers,
Quentin

>> Thank you,
>> Zoran
>> ___
>>
>> On Mon, May 24, 2021 at 2:24 PM Quentin Schulz  wrote:
>> >
>> > Hi Zoran,
>> >
>> > On May 24, 2021 8:27:58 AM UTC, Zoran  
>> > wrote:
>> > >Hello again to YOCTO Folks,
>> > >
>> > >Here is another blunder I ran into while fixing a yocto-setup.sh script:
>> > >https://github.com/ZoranStojsavljevic/bbb-yocto/blob/master/yocto-setup.sh
>> > >
>> > >While executing $  . ./yocto-setup.sh dunfell, everything ran smoothly.
>> > >
>> > >I did the same routine with the $  . ./yocto-setup.sh gatesgarth, and
>> > >approximately after:
>> > >Parsing recipes: 9% |##
>> > >
>> > >The following message pops up!
>> > >Loading cache: 100% |
>> > >| ETA:  --:--:--
>> > >Loaded 0 entries from dependency cache.
>> > >ERROR: ParseError at
>> > >/home/vuser/projects_yocto/bbb-yocto-gatesgarth/meta-bbb/images/console-image.bb:4:
>> > >Could not include required file images/basic-dev-image.bb
>> > >
>> > >Summary: There was 1 WARNING message shown.
>> > >Summary: There was 1 ERROR message shown, returning a non-zero exit code.
>> > >
>> >
>> > The layer is not included. Check in your bblayers.conf. see 
>> >

[linux-yocto][PATCH 2/2][linux-yocto-dev standard/xlnx-soc] spi: spi-zynqmp-gqspi: fix compile error

2021-05-24 Thread quanyang.wang

From: Quanyang Wang 

Add the missing part of the mainline commit 126bdb606fd28
("spi: spi-zynqmp-gqspi: return -ENOMEM if dma_map_single fails").

Signed-off-by: Quanyang Wang 
---
 drivers/spi/spi-zynqmp-gqspi.c | 8 +++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/drivers/spi/spi-zynqmp-gqspi.c b/drivers/spi/spi-zynqmp-gqspi.c
index d22adcec1f02d..d31f6698b7181 100644
--- a/drivers/spi/spi-zynqmp-gqspi.c
+++ b/drivers/spi/spi-zynqmp-gqspi.c
@@ -955,8 +955,14 @@ static void zynqmp_qspi_write_op(struct zynqmp_qspi 
*xqspi, u8 tx_nbits,
 static int zynqmp_qspi_read_op(struct zynqmp_qspi *xqspi, u8 rx_nbits,
u32 genfifoentry)
 {
-   zynqmp_qspi_setuprxdma(xqspi);
+   int ret;
+
+   ret = zynqmp_qspi_setuprxdma(xqspi);
+   if (ret)
+   return ret;
zynqmp_qspi_fillgenfifo(xqspi, rx_nbits, genfifoentry);
+
+   return 0;
 }
 
 /**
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#9916): 
https://lists.yoctoproject.org/g/linux-yocto/message/9916
Mute This Topic: https://lists.yoctoproject.org/mt/83055436/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto] [PATCH][linux-yocto-dev standard/xlnx-soc] [PATCH 0/2] xlnx: fix compile error

2021-05-24 Thread quanyang.wang

From: Quanyang Wang 

Hi Bruce,

Would you please help merge these 2 patches to linux-yocto-dev
standard/xlnx-soc branch?

These 2 patches fix build error when introducing mainline patches.

Thanks,
Quanyang

Quanyang Wang (2):
  drm: xlnx: zynqmp_dp: fix compile error for
ZYNQMP_DP_SCRAMBLING_DISABLE
  spi: spi-zynqmp-gqspi: fix compile error

 drivers/gpu/drm/xlnx/zynqmp_dp.c | 2 +-
 drivers/spi/spi-zynqmp-gqspi.c   | 8 +++-
 2 files changed, 8 insertions(+), 2 deletions(-)

-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#9914): 
https://lists.yoctoproject.org/g/linux-yocto/message/9914
Mute This Topic: https://lists.yoctoproject.org/mt/83055434/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto][PATCH 1/2][linux-yocto-dev standard/xlnx-soc] drm: xlnx: zynqmp_dp: fix compile error for ZYNQMP_DP_SCRAMBLING_DISABLE

2021-05-24 Thread quanyang.wang

From: Quanyang Wang 

The mainline xilinx DP driver is using ZYNQMP_DP_SCRAMBLING_DISABLE but
SDK is using ZYNQMP_DP_TX_SCRAMBLING_DISABLE, this will cause building
error. Fix it by using SDK definition.

Signed-off-by: Quanyang Wang 
---
 drivers/gpu/drm/xlnx/zynqmp_dp.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/gpu/drm/xlnx/zynqmp_dp.c b/drivers/gpu/drm/xlnx/zynqmp_dp.c
index cbfb989ce068c..09fdb48cd03a0 100644
--- a/drivers/gpu/drm/xlnx/zynqmp_dp.c
+++ b/drivers/gpu/drm/xlnx/zynqmp_dp.c
@@ -905,7 +905,7 @@ static int zynqmp_dp_train(struct zynqmp_dp *dp)
if (ret < 0)
return ret;
 
-   zynqmp_dp_write(dp, ZYNQMP_DP_SCRAMBLING_DISABLE, 1);
+   zynqmp_dp_write(dp, ZYNQMP_DP_TX_SCRAMBLING_DISABLE, 1);
memset(dp->train_set, 0, sizeof(dp->train_set));
ret = zynqmp_dp_link_train_cr(dp);
if (ret)
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#9915): 
https://lists.yoctoproject.org/g/linux-yocto/message/9915
Mute This Topic: https://lists.yoctoproject.org/mt/83055435/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] using grpc fails with linker error: file in wrong format

2021-05-24 Thread Khem Raj




On 5/24/21 12:37 AM, Juergen Landwehr wrote:

Hi all,

I am developing a C++ library that is using gRPC.

To be able to use protoc for generating the stubs I added the following 
dependencies:


DEPENDS += "\
   grpc-native \
   protobuf-native \
   ...
   "


and to link my library with cross-compiled libraries:

RDEPENDS += "\
    grpc \
    protobuf \
    ...
    "

However, linking the library fails with the following error:

ld: 
/data/jenkins/workspace/e0_mbient_yocto_mbient_manifests_master_downstream/build/tmp/work/cortexa72-mbient-linux/tokenmaster-client/git-r0/recipe-sysroot-native/usr/lib/libgrpc++.so.1.24.3: 
error adding symbols: file in wrong format


I guess the problem is, that native grpc++ library is used from the 
"recipe-sysroot-native" directory and thus not the cross-compiled version.


What am I doing wrong? How can I tell Yocto to use the cross-compiled 
versions?


this is upto your component's build system, so perhaps you should look 
into that and ensure that its using right options. Second place to look 
is recipe for your package and ensure right vars and options are passed 
to build. you might want to look at sysdig package build system and see 
how they are doing it and perhaps mimic that for your package too.




Thanks,

Jürgen





-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#53629): https://lists.yoctoproject.org/g/yocto/message/53629
Mute This Topic: https://lists.yoctoproject.org/mt/83045841/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] ERROR: ParseError at .../bbb-yocto-gatesgarth/meta-bbb/images/console-image.bb:4: Could not include required file images/basic-dev-image.bb

2021-05-24 Thread Zoran

Or, maybe, now the DHCP is included in the releases by default?

Thank you,
Zoran
___

On Mon, May 24, 2021 at 4:09 PM Zoran Stojsavljevic
 wrote:
>
> Hello Quentin,
>
> Thank you for finding the bug. It was in front of my eyes (I print all
> the layers at the end of setup, but I missed to compare bb-layers from
> dunfell with bb-layers from gatesgarth).
>
> I should do better. With regards to testing thinking. ;-)
> ___
>
> Now, there are other bugs (I should say, new features introduced).
>
> Loading cache: 100%
> ||
> Time: 0:00:00
> Loaded 3533 entries from dependency cache.
> Parsing recipes: 100%
> |##|
> Time: 0:00:00
> Parsing of 2311 .bb files complete (2309 cached, 2 parsed). 3535
> targets, 121 skipped, 1 masked, 0 errors.
> NOTE: Resolving any missing task queue dependencies
> ERROR: Nothing RPROVIDES 'dhcp-libs' (but
> /home/vuser/projects_yocto/bbb-yocto-gatesgarth/poky/meta/recipes-core/images/core-image-minimal.bb
> RDEPENDS on or otherwise requires it)
> NOTE: Runtime target 'dhcp-libs' is unbuildable, removing...
> Missing or unbuildable dependency chain was: ['dhcp-libs']
> ERROR: Nothing RPROVIDES 'dhcp-server' (but
> /home/vuser/projects_yocto/bbb-yocto-gatesgarth/poky/meta/recipes-core/images/core-image-minimal.bb
> RDEPENDS on or otherwise requires it)
> NOTE: Runtime target 'dhcp-server' is unbuildable, removing...
> Missing or unbuildable dependency chain was: ['dhcp-server']
> ERROR: Nothing RPROVIDES 'dhcp-server-config' (but
> /home/vuser/projects_yocto/bbb-yocto-gatesgarth/poky/meta/recipes-core/images/core-image-minimal.bb
> RDEPENDS on or otherwise requires it)
> NOTE: Runtime target 'dhcp-server-config' is unbuildable, removing...
> Missing or unbuildable dependency chain was: ['dhcp-server-config']
> ERROR: Nothing RPROVIDES 'dhcp-client' (but
> /home/vuser/projects_yocto/bbb-yocto-gatesgarth/poky/meta/recipes-core/images/core-image-minimal.bb
> RDEPENDS on or otherwise requires it)
> NOTE: Runtime target 'dhcp-client' is unbuildable, removing...
> Missing or unbuildable dependency chain was: ['dhcp-client']
> ERROR: Nothing RPROVIDES 'dhcp-relay' (but
> /home/vuser/projects_yocto/bbb-yocto-gatesgarth/poky/meta/recipes-core/images/core-image-minimal.bb
> RDEPENDS on or otherwise requires it)
> NOTE: Runtime target 'dhcp-relay' is unbuildable, removing...
> Missing or unbuildable dependency chain was: ['dhcp-relay']
> ERROR: Nothing RPROVIDES 'dhcp-omshell' (but
> /home/vuser/projects_yocto/bbb-yocto-gatesgarth/poky/meta/recipes-core/images/core-image-minimal.bb
> RDEPENDS on or otherwise requires it)
> NOTE: Runtime target 'dhcp-omshell' is unbuildable, removing...
> Missing or unbuildable dependency chain was: ['dhcp-omshell']
>
> Seems that this line in local.conf got severely changed, or most
> likely the DHCP package version/handling got changed:
>
> CORE_IMAGE_EXTRA_INSTALL_append = "openssh dhcp-libs dhcp-server
> dhcp-server-config dhcp-client dhcp-relay dhcp-omshell cmake
> libsocketcan nfs-utils rt-tests strace procps
> packagegroup-core-buildessential "
>
> The question is: what should I include in the
> CORE_IMAGE_EXTRA_INSTALL_append for the DHCP package for gatesgarth
> and later releases???
>
> Thank you,
> Zoran
> ___
>
> On Mon, May 24, 2021 at 2:24 PM Quentin Schulz  wrote:
> >
> > Hi Zoran,
> >
> > On May 24, 2021 8:27:58 AM UTC, Zoran  wrote:
> > >Hello again to YOCTO Folks,
> > >
> > >Here is another blunder I ran into while fixing a yocto-setup.sh script:
> > >https://github.com/ZoranStojsavljevic/bbb-yocto/blob/master/yocto-setup.sh
> > >
> > >While executing $  . ./yocto-setup.sh dunfell, everything ran smoothly.
> > >
> > >I did the same routine with the $  . ./yocto-setup.sh gatesgarth, and
> > >approximately after:
> > >Parsing recipes: 9% |##
> > >
> > >The following message pops up!
> > >Loading cache: 100% |
> > >| ETA:  --:--:--
> > >Loaded 0 entries from dependency cache.
> > >ERROR: ParseError at
> > >/home/vuser/projects_yocto/bbb-yocto-gatesgarth/meta-bbb/images/console-image.bb:4:
> > >Could not include required file images/basic-dev-image.bb
> > >
> > >Summary: There was 1 WARNING message shown.
> > >Summary: There was 1 ERROR message shown, returning a non-zero exit code.
> > >
> >
> > The layer is not included. Check in your bblayers.conf. see 
> > https://github.com/ZoranStojsavljevic/bbb-yocto/blob/a6e8e8ce491705816d02df58fa0ef9378b18ef83/yocto-setup.sh#L114
> >  where you are missing the gatesgarth check.
> >
> > Cheers,
> > Quentin
> >
> >
> > >If you peek into the following github repos:
> > >https://github.com/jumpnow/meta-bbb
> > >https://github.com/jumpnow/meta-jumpnow
> > >
> > >You'll see that in later  images/basic-dev-image.bb does exist, as
> > >well as in the dunfell

Re: [yocto] ERROR: ParseError at .../bbb-yocto-gatesgarth/meta-bbb/images/console-image.bb:4: Could not include required file images/basic-dev-image.bb

2021-05-24 Thread Zoran

Hello Quentin,

Thank you for finding the bug. It was in front of my eyes (I print all
the layers at the end of setup, but I missed to compare bb-layers from
dunfell with bb-layers from gatesgarth).

I should do better. With regards to testing thinking. ;-)
___

Now, there are other bugs (I should say, new features introduced).

Loading cache: 100%
||
Time: 0:00:00
Loaded 3533 entries from dependency cache.
Parsing recipes: 100%
|##|
Time: 0:00:00
Parsing of 2311 .bb files complete (2309 cached, 2 parsed). 3535
targets, 121 skipped, 1 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
ERROR: Nothing RPROVIDES 'dhcp-libs' (but
/home/vuser/projects_yocto/bbb-yocto-gatesgarth/poky/meta/recipes-core/images/core-image-minimal.bb
RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'dhcp-libs' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['dhcp-libs']
ERROR: Nothing RPROVIDES 'dhcp-server' (but
/home/vuser/projects_yocto/bbb-yocto-gatesgarth/poky/meta/recipes-core/images/core-image-minimal.bb
RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'dhcp-server' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['dhcp-server']
ERROR: Nothing RPROVIDES 'dhcp-server-config' (but
/home/vuser/projects_yocto/bbb-yocto-gatesgarth/poky/meta/recipes-core/images/core-image-minimal.bb
RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'dhcp-server-config' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['dhcp-server-config']
ERROR: Nothing RPROVIDES 'dhcp-client' (but
/home/vuser/projects_yocto/bbb-yocto-gatesgarth/poky/meta/recipes-core/images/core-image-minimal.bb
RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'dhcp-client' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['dhcp-client']
ERROR: Nothing RPROVIDES 'dhcp-relay' (but
/home/vuser/projects_yocto/bbb-yocto-gatesgarth/poky/meta/recipes-core/images/core-image-minimal.bb
RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'dhcp-relay' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['dhcp-relay']
ERROR: Nothing RPROVIDES 'dhcp-omshell' (but
/home/vuser/projects_yocto/bbb-yocto-gatesgarth/poky/meta/recipes-core/images/core-image-minimal.bb
RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'dhcp-omshell' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['dhcp-omshell']

Seems that this line in local.conf got severely changed, or most
likely the DHCP package version/handling got changed:

CORE_IMAGE_EXTRA_INSTALL_append = "openssh dhcp-libs dhcp-server
dhcp-server-config dhcp-client dhcp-relay dhcp-omshell cmake
libsocketcan nfs-utils rt-tests strace procps
packagegroup-core-buildessential "

The question is: what should I include in the
CORE_IMAGE_EXTRA_INSTALL_append for the DHCP package for gatesgarth
and later releases???

Thank you,
Zoran
___

On Mon, May 24, 2021 at 2:24 PM Quentin Schulz  wrote:
>
> Hi Zoran,
>
> On May 24, 2021 8:27:58 AM UTC, Zoran  wrote:
> >Hello again to YOCTO Folks,
> >
> >Here is another blunder I ran into while fixing a yocto-setup.sh script:
> >https://github.com/ZoranStojsavljevic/bbb-yocto/blob/master/yocto-setup.sh
> >
> >While executing $  . ./yocto-setup.sh dunfell, everything ran smoothly.
> >
> >I did the same routine with the $  . ./yocto-setup.sh gatesgarth, and
> >approximately after:
> >Parsing recipes: 9% |##
> >
> >The following message pops up!
> >Loading cache: 100% |
> >| ETA:  --:--:--
> >Loaded 0 entries from dependency cache.
> >ERROR: ParseError at
> >/home/vuser/projects_yocto/bbb-yocto-gatesgarth/meta-bbb/images/console-image.bb:4:
> >Could not include required file images/basic-dev-image.bb
> >
> >Summary: There was 1 WARNING message shown.
> >Summary: There was 1 ERROR message shown, returning a non-zero exit code.
> >
>
> The layer is not included. Check in your bblayers.conf. see 
> https://github.com/ZoranStojsavljevic/bbb-yocto/blob/a6e8e8ce491705816d02df58fa0ef9378b18ef83/yocto-setup.sh#L114
>  where you are missing the gatesgarth check.
>
> Cheers,
> Quentin
>
>
> >If you peek into the following github repos:
> >https://github.com/jumpnow/meta-bbb
> >https://github.com/jumpnow/meta-jumpnow
> >
> >You'll see that in later  images/basic-dev-image.bb does exist, as
> >well as in the dunfell branch:
> >https://github.com/jumpnow/meta-jumpnow/blob/zeus/images/basic-dev-image.bb
> >
> >As well as in gatesgarth branch:
> >https://github.com/jumpnow/meta-jumpnow/blob/gatesgarth/images/basic-dev-image.bb
> >
> >What I see upon the logic, something changes in poky/ setup, while
> >transitioning from dunfell to gatesgarth.
> >
> >I also have created an issue

Re: [yocto] Gatesgarth-24.0.4 image-live fails

2021-05-24 Thread Ferry Toth


Wow, that got messed up, let me retry.

Op 24-05-2021 om 14:19 schreef Ferry Toth:
Accidentally I refreshed poky and rebuilt. The image-live (do_bootimg) 
fails when building hddimg with the following:


ERROR: edison-image-1.0-r0 do_bootimg: Error executing a python function 
in exec_python_func() autogenerated:


The stack trace of python calls that resulted in this exception/failure was:
File: 'exec_python_func() autogenerated', lineno: 2, function: 
 0001:
 *** 0002:do_bootimg(d)
 0003:
File: 
'/home/ferry/tmp/edison-intel/my/edison-morty/out/linux64/poky/meta/classes/image-live.bbclass', 
lineno: 258, function: do_bootimg

 0254:    if d.getVar("PCBIOS") == "1":
 0255:    bb.build.exec_func('build_syslinux_cfg', d)
 0256:    if d.getVar("EFI") == "1":
 0257:    bb.build.exec_func('build_efi_cfg', d)
 *** 0258:    bb.build.exec_func('build_hddimg', d)
 0259:    bb.build.exec_func('build_iso', d)
 0260:    bb.build.exec_func('create_symlinks', d)
 0261:}
 0262:do_bootimg[subimages] = "hddimg iso"
File: 
'/home/ferry/tmp/edison-intel/my/edison-morty/out/linux64/poky/bitbake/lib/bb/build.py', 
lineno: 256, function: exec_func

 0252:    with bb.utils.fileslocked(lockfiles):
 0253:    if ispython:
 0254:    exec_func_python(func, d, runfile, cwd=adir)
 0255:    else:
 *** 0256:    exec_func_shell(func, d, runfile, cwd=adir)
 0257:
 0258:    try:
 0259:    curcwd = os.getcwd()
 0260:    except:
File: 
'/home/ferry/tmp/edison-intel/my/edison-morty/out/linux64/poky/bitbake/lib/bb/build.py', 
lineno: 503, function: exec_func_shell

 0499:    with open(fifopath, 'r+b', buffering=0) as fifo:
 0500:    try:
 0501:    bb.debug(2, "Executing shell function %s" % func)
 0502:    with open(os.devnull, 'r+') as stdin, logfile:
 *** 0503:    bb.process.run(cmd, shell=False, stdin=stdin, 
log=logfile, extrafiles=[(fifo,readfifo)])

 0504:    except bb.process.ExecutionError as exe:
 0505:    # Find the backtrace that the shell trap generated
 0506:    backtrace_marker_regex = re.compile(r"WARNING: 
Backtrace \(BB generated script\)")

 0507:    stdout_lines = (exe.stdout or "").split("\n")
File: 
'/home/ferry/tmp/edison-intel/my/edison-morty/out/linux64/poky/bitbake/lib/bb/process.py', 
lineno: 184, function: run

 0180:    if not stderr is None:
 0181:    stderr = stderr.decode("utf-8")
 0182:
 0183:    if pipe.returncode != 0:
 *** 0184:    raise ExecutionError(cmd, pipe.returncode, stdout, 
stderr)

 0185:    return stdout, stderr
Exception: bb.process.ExecutionError: Execution of 
'/home/ferry/tmp/edison-intel/my/edison-morty/out/linux64/build/tmp/work/edison-poky-linux/edison-image/1.0-r0/temp/run.build_hddimg.256530' 
failed with exit code 1:
mkdosfs: unable to create 
/home/ferry/tmp/edison-intel/my/edison-morty/out/linux64/build/tmp/work/edison-poky-linux/edison-image/1.0-r0/deploy-edison-image-image-complete/edison-image-edison-20210524113748.hddimg

mkfs.fat 4.1 (2017-01-24)
WARNING: exit code 1 from a shell command.

The reason is that the directory deploy-edison-image-image-complete 
doesn't exist at the time mkdosfs want to write. However after 
completing the remainder of image live the directory does exists. 
Consequently, running bitbake a second time image-live succeeds.


I've tried various thing including expressly creating the directory 
before mkdosfs, but nothing worked. It seems I don't understand how it 
is supposed to work in the first place.


However, I managed to trace back the issue to this commit 91e4a1c1 
"image-live.bbclass: optional depends when ROOTFS empty".


Reverting this resolves the issue.

Any idea what could be wrong?


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#53626): https://lists.yoctoproject.org/g/yocto/message/53626
Mute This Topic: https://lists.yoctoproject.org/mt/83049280/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] ERROR: ParseError at .../bbb-yocto-gatesgarth/meta-bbb/images/console-image.bb:4: Could not include required file images/basic-dev-image.bb

2021-05-24 Thread Quentin Schulz

Hi Zoran,

On May 24, 2021 8:27:58 AM UTC, Zoran  wrote:
>Hello again to YOCTO Folks,
>
>Here is another blunder I ran into while fixing a yocto-setup.sh script:
>https://github.com/ZoranStojsavljevic/bbb-yocto/blob/master/yocto-setup.sh
>
>While executing $  . ./yocto-setup.sh dunfell, everything ran smoothly.
>
>I did the same routine with the $  . ./yocto-setup.sh gatesgarth, and
>approximately after:
>Parsing recipes: 9% |##
>
>The following message pops up!
>Loading cache: 100% |
>| ETA:  --:--:--
>Loaded 0 entries from dependency cache.
>ERROR: ParseError at
>/home/vuser/projects_yocto/bbb-yocto-gatesgarth/meta-bbb/images/console-image.bb:4:
>Could not include required file images/basic-dev-image.bb
>
>Summary: There was 1 WARNING message shown.
>Summary: There was 1 ERROR message shown, returning a non-zero exit code.
>

The layer is not included. Check in your bblayers.conf. see 
https://github.com/ZoranStojsavljevic/bbb-yocto/blob/a6e8e8ce491705816d02df58fa0ef9378b18ef83/yocto-setup.sh#L114
 where you are missing the gatesgarth check.

Cheers,
Quentin


>If you peek into the following github repos:
>https://github.com/jumpnow/meta-bbb
>https://github.com/jumpnow/meta-jumpnow
>
>You'll see that in later  images/basic-dev-image.bb does exist, as
>well as in the dunfell branch:
>https://github.com/jumpnow/meta-jumpnow/blob/zeus/images/basic-dev-image.bb
>
>As well as in gatesgarth branch:
>https://github.com/jumpnow/meta-jumpnow/blob/gatesgarth/images/basic-dev-image.bb
>
>What I see upon the logic, something changes in poky/ setup, while
>transitioning from dunfell to gatesgarth.
>
>I also have created an issue in bbb-yocto repo:
>https://github.com/ZoranStojsavljevic/bbb-yocto/issues/3
>
>I would appreciate any ideas or hints...  Maybe some changes required
>in local.conf ?
>
>You can all try it yourselves, and see the same!
>
>Thank you,
>Zoran
>___

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#53625): https://lists.yoctoproject.org/g/yocto/message/53625
Mute This Topic: https://lists.yoctoproject.org/mt/83046309/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Gatesgarth-24.0.4 image-live fails

2021-05-24 Thread Ferry Toth

Accidentally I refreshed poky and rebuilt. The image-live (do_bootimg) 
fails when building hddimg with the following:


ERROR: edison-image-1.0-r0 do_bootimg: Error executing a python function 
in exec_python_func() autogenerated: The stack trace of python calls 
that resulted in this exception/failure was: File: 'exec_python_func() 
autogenerated', lineno: 2, function:   0001:  *** 
0002:do_bootimg(d)  0003: File: 
'/home/ferry/tmp/edison-intel/my/edison-morty/out/linux64/poky/meta/classes/image-live.bbclass', 
lineno: 258, function: do_bootimg  0254:    if d.getVar("PCBIOS") == 
"1":  0255:    bb.build.exec_func('build_syslinux_cfg', d)  
0256:    if d.getVar("EFI") == "1":  0257:    
bb.build.exec_func('build_efi_cfg', d)  *** 0258:    
bb.build.exec_func('build_hddimg', d)  0259:    
bb.build.exec_func('build_iso', d)  0260:    
bb.build.exec_func('create_symlinks', d)  0261:}  
0262:do_bootimg[subimages] = "hddimg iso" File: 
'/home/ferry/tmp/edison-intel/my/edison-morty/out/linux64/poky/bitbake/lib/bb/build.py', 
lineno: 256, function: exec_func  0252:    with 
bb.utils.fileslocked(lockfiles):  0253:    if ispython:  
0254:    exec_func_python(func, d, runfile, cwd=adir)  
0255:    else:  *** 0256:    exec_func_shell(func, d, 
runfile, cwd=adir)  0257:  0258:    try:  0259:    
curcwd = os.getcwd()  0260:    except: File: 
'/home/ferry/tmp/edison-intel/my/edison-morty/out/linux64/poky/bitbake/lib/bb/build.py', 
lineno: 503, function: exec_func_shell  0499:    with open(fifopath, 
'r+b', buffering=0) as fifo:  0500:    try:  
0501:    bb.debug(2, "Executing shell function %s" % func)  
0502:    with open(os.devnull, 'r+') as stdin, logfile:  *** 
0503:    bb.process.run(cmd, shell=False, stdin=stdin, 
log=logfile, extrafiles=[(fifo,readfifo)])  0504:    except 
bb.process.ExecutionError as exe:  0505:    # Find the 
backtrace that the shell trap generated  0506:    
backtrace_marker_regex = re.compile(r"WARNING: Backtrace \(BB generated 
script\)")  0507:    stdout_lines = (exe.stdout or 
"").split("\n") File: 
'/home/ferry/tmp/edison-intel/my/edison-morty/out/linux64/poky/bitbake/lib/bb/process.py', 
lineno: 184, function: run  0180:    if not stderr is None:  
0181:    stderr = stderr.decode("utf-8")  0182:  
0183:    if pipe.returncode != 0:  *** 0184:    raise 
ExecutionError(cmd, pipe.returncode, stdout, stderr)  0185:    
return stdout, stderr Exception: bb.process.ExecutionError: Execution of 
'/home/ferry/tmp/edison-intel/my/edison-morty/out/linux64/build/tmp/work/edison-poky-linux/edison-image/1.0-r0/temp/run.build_hddimg.256530' 
failed with exit code 1: mkdosfs: unable to create 
/home/ferry/tmp/edison-intel/my/edison-morty/out/linux64/build/tmp/work/edison-poky-linux/edison-image/1.0-r0/deploy-edison-image-image-complete/edison-image-edison-20210524113748.hddimg 
mkfs.fat 4.1 (2017-01-24) WARNING: exit code 1 from a shell command.


The reason is that the directory deploy-edison-image-image-complete 
doesn't exist at the time mkdosfs want to write. However after 
completing the remainder of image live the directory does exists. 
Consequently, running bitbake a second time image-live succeeds.


I've tried various thing including expressly creating the directory 
before mkdosfs, but nothing worked. It seems I don't understand how it 
is supposed to work in the first place.


However, I managed to trace back the issue to this commit 91e4a1c1 
"image-live.bbclass: optional depends when ROOTFS empty".


Reverting this resolves the issue.

Any idea what could be wrong?


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#53624): https://lists.yoctoproject.org/g/yocto/message/53624
Mute This Topic: https://lists.yoctoproject.org/mt/83049280/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto] [yocto-kernel-cache] [yocto-5.10-rt] [PATCH] Fix warning from do_kernel_configcheck in intel-x86 bsp

2021-05-24 Thread Zhang, Qiang

From: Zqiang 

WARNING: linux-yocto-rt-5.10.x+gitAUTOINC+cd049697e9_ff83ae5580-r0 
do_kernel_configcheck:
[kernel config]: specified values did not make it into the kernel's final 
configuration:

[NOTE]: 'CONFIG_CFG80211' last val (y) and .config val (m) do not match
[INFO]: CONFIG_CFG80211 : m ## .config: 1559 
:configs/v5.10/standard/preempt-rt/
intel-x86/features/mac80211/mac80211.cfg (m)
configs/v5.10/standard/preempt-rt/intel-x86/features/hostapd/hostapd.cfg (y)
[INFO]: raw config text:

config CFG80211
tristate "cfg80211 - wireless configuration API"
select FW_LOADER
select CRC32
select CRYPTO_SHA256 if CFG80211_USE_KERNEL_REGDB_KEYS
depends on (RFKILL || !RFKILL) && WIRELESS && NET
help
  cfg80211 is the Linux wireless LAN (802.11) configuration API.
  Enable this if you have a wireless device.

  For more information refer to documentation on the wireless 
wiki:

  
https://wireless.wiki.kernel.org/en/developers/Documentation/cfg80211

  When built as a module it will be called cfg80211.

Config 'CFG80211' has the following Direct dependencies (CFG80211=y):
RFKILL(=y) || !RFKILL(=y) (=y) && WIRELESS(=y) && NET(=y)
Parent dependencies are:
 CFG80211_USE_KERNEL_REGDB_KEYS [y] WIRELESS [y] RFKILL [y] NET [y]
[NOTE]: 'CONFIG_MAC80211' last val (y) and .config val (m) do not match
[INFO]: CONFIG_MAC80211 : m ## .config: 1574 
:configs/v5.10/standard/preempt-rt/intel-x86/
features/mac80211/mac80211.cfg (m)

configs/v5.10/standard/preempt-rt/intel-x86/features/hostapd/hostapd.cfg (y)
[INFO]: raw config text:

config MAC80211
tristate "Generic IEEE 802.11 Networking Stack (mac80211)"
select CRYPTO
select CRYPTO_LIB_ARC4
select CRYPTO_AES
select CRYPTO_CCM
select CRYPTO_GCM
select CRYPTO_CMAC
select CRC32
depends on CFG80211 && WIRELESS && NET
help
  This option enables the hardware independent IEEE 802.11
  networking stack.

Config 'MAC80211' has the following Direct dependencies (MAC80211=m):
CFG80211(=m) && WIRELESS(=y) && NET(=y)
Parent dependencies are:
 WIRELESS [y] NET [y] CFG80211 [m]
[NOTE]: 'CONFIG_DPTF_PCH_FIVR' last val (m) and .config val (n) do not match
[INFO]: CONFIG_DPTF_PCH_FIVR : n
[INFO]: raw config text:

config DPTF_PCH_FIVR
tristate "PCH FIVR DPTF Participant"
default m
depends on ACPI_DPTF && ACPI
help
  This driver adds support for Dynamic Platform and Thermal 
Framework
  (DPTF) PCH FIVR Participant device support. This driver 
allows to
  switch the PCH FIVR (Fully Integrated Voltage Regulator) 
frequency.
  This participant is responsible for exposing:
freq_mhz_low_clock
freq_mhz_high_clock

  To compile this driver as a module, choose M here:
  the module will be called dptf_pch_fivr.

Config 'DPTF_PCH_FIVR' has the following Direct dependencies 
(DPTF_PCH_FIVR=n):
ACPI_DPTF(=n) && ACPI(=y)
Parent dependencies are:
 ACPI_DPTF [n] ACPI [y]
[INFO]: config 'CONFIG_DPTF_PCH_FIVR' was set, but it wasn't assignable, 
check

Reconfigure the variable value of CFG80211, MAC80211 and ACPI_DPTF
in intel-x86 BSP.

Signed-off-by: Zqiang 
---
 bsp/intel-x86/intel-x86-cfg80211-overrides.cfg | 3 +++
 bsp/intel-x86/intel-x86-dptf-overrides.cfg | 2 ++
 bsp/intel-x86/intel-x86.scc| 2 ++
 3 files changed, 7 insertions(+)
 create mode 100644 bsp/intel-x86/intel-x86-cfg80211-overrides.cfg
 create mode 100644 bsp/intel-x86/intel-x86-dptf-overrides.cfg

diff --git a/bsp/intel-x86/intel-x86-cfg80211-overrides.cfg 
b/bsp/intel-x86/intel-x86-cfg80211-overrides.cfg
new file mode 100644
index ..26957814
--- /dev/null
+++ b/bsp/intel-x86/intel-x86-cfg80211-overrides.cfg
@@ -0,0 +1,3 @@
+# SPDX-License-Identifier: MIT
+CONFIG_CFG80211=y
+CONFIG_MAC80211=y
diff --git a/bsp/intel-x86/intel-x86-dptf-overrides.cfg 
b/bsp/intel-x86/intel-x86-dptf-overrides.cfg
new file mode 100644
index ..2c206883
--- /dev/null
+++ b/bsp/intel-x86/intel-x86-dptf-overrides.cfg
@@ -0,0 +1,2 @@
+# SPDX-License-Identifier: MIT
+CONFIG_ACPI_DPTF=y
diff --git a/bsp/intel-x86/intel-x86.scc b/bsp/intel-x86/intel-x86.scc
index d837c58f..d6b2f931 100644
--- a/bsp/intel-x86/intel-x86.scc
+++ b/bsp/intel-x86/intel-x86.scc
@@ -58,3 +58,5 @@ kconf hardware intel-x86-acpi.cfg
 kconf hardware

[yocto] ERROR: ParseError at .../bbb-yocto-gatesgarth/meta-bbb/images/console-image.bb:4: Could not include required file images/basic-dev-image.bb

2021-05-24 Thread Zoran

Hello again to YOCTO Folks,

Here is another blunder I ran into while fixing a yocto-setup.sh script:
https://github.com/ZoranStojsavljevic/bbb-yocto/blob/master/yocto-setup.sh

While executing $  . ./yocto-setup.sh dunfell, everything ran smoothly.

I did the same routine with the $  . ./yocto-setup.sh gatesgarth, and
approximately after:
Parsing recipes: 9% |##

The following message pops up!
Loading cache: 100% |
| ETA:  --:--:--
Loaded 0 entries from dependency cache.
ERROR: ParseError at
/home/vuser/projects_yocto/bbb-yocto-gatesgarth/meta-bbb/images/console-image.bb:4:
Could not include required file images/basic-dev-image.bb

Summary: There was 1 WARNING message shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.

If you peek into the following github repos:
https://github.com/jumpnow/meta-bbb
https://github.com/jumpnow/meta-jumpnow

You'll see that in later  images/basic-dev-image.bb does exist, as
well as in the dunfell branch:
https://github.com/jumpnow/meta-jumpnow/blob/zeus/images/basic-dev-image.bb

As well as in gatesgarth branch:
https://github.com/jumpnow/meta-jumpnow/blob/gatesgarth/images/basic-dev-image.bb

What I see upon the logic, something changes in poky/ setup, while
transitioning from dunfell to gatesgarth.

I also have created an issue in bbb-yocto repo:
https://github.com/ZoranStojsavljevic/bbb-yocto/issues/3

I would appreciate any ideas or hints...  Maybe some changes required
in local.conf ?

You can all try it yourselves, and see the same!

Thank you,
Zoran
___

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#53623): https://lists.yoctoproject.org/g/yocto/message/53623
Mute This Topic: https://lists.yoctoproject.org/mt/83046309/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] using grpc fails with linker error: file in wrong format

2021-05-24 Thread Juergen Landwehr

Hi all,

I am developing a C++ library that is using gRPC.

To be able to use protoc for generating the stubs I added the following 
dependencies:

DEPENDS += "\
 grpc-native \ 
 protobuf-native \
 ...
 " 
and to link my library with cross-compiled libraries:

RDEPENDS += "\
grpc \
protobuf \
...
"

However, linking the library fails with the following error:

ld: 
/data/jenkins/workspace/e0_mbient_yocto_mbient_manifests_master_downstream/build/tmp/work/cortexa72-mbient-linux/tokenmaster-client/git-r0/recipe-sysroot-native/usr/lib/libgrpc++.so.1.24.3:
 error adding symbols: file in wrong format

I guess the problem is, that native grpc++ library is used from the 
"recipe-sysroot-native" directory and thus not the cross-compiled version.

What am I doing wrong? How can I tell Yocto to use the cross-compiled versions?

Thanks,

Jürgen

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#53622): https://lists.yoctoproject.org/g/yocto/message/53622
Mute This Topic: https://lists.yoctoproject.org/mt/83045841/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] ERROR: ParseError at .../bbb-yocto-gatesgarth/meta-bbb/images/console-image.bb:4: Could not include required file images/basic-dev-image.bb

[yocto] M+ & H bugs with Milestone Movements WW21

[yocto] Enhancements/Bugs closed WW21!

[yocto] Current high bug count owners for Yocto Project 3.4

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

[yocto-announce] [ANNOUNCEMENT] Yocto Project 3.3.1 (hardknott-25.0.1) is Released

[yocto] [ANNOUNCEMENT] Yocto Project 3.3.1 (hardknott-25.0.1) is Released

Re: [yocto] ERROR: ParseError at .../bbb-yocto-gatesgarth/meta-bbb/images/console-image.bb:4: Could not include required file images/basic-dev-image.bb

[linux-yocto][PATCH 2/2][linux-yocto-dev standard/xlnx-soc] spi: spi-zynqmp-gqspi: fix compile error

[linux-yocto] [PATCH][linux-yocto-dev standard/xlnx-soc] [PATCH 0/2] xlnx: fix compile error

[linux-yocto][PATCH 1/2][linux-yocto-dev standard/xlnx-soc] drm: xlnx: zynqmp_dp: fix compile error for ZYNQMP_DP_SCRAMBLING_DISABLE

Re: [yocto] using grpc fails with linker error: file in wrong format

Re: [yocto] ERROR: ParseError at .../bbb-yocto-gatesgarth/meta-bbb/images/console-image.bb:4: Could not include required file images/basic-dev-image.bb

Re: [yocto] ERROR: ParseError at .../bbb-yocto-gatesgarth/meta-bbb/images/console-image.bb:4: Could not include required file images/basic-dev-image.bb

Re: [yocto] Gatesgarth-24.0.4 image-live fails

Re: [yocto] ERROR: ParseError at .../bbb-yocto-gatesgarth/meta-bbb/images/console-image.bb:4: Could not include required file images/basic-dev-image.bb

[yocto] Gatesgarth-24.0.4 image-live fails

[linux-yocto] [yocto-kernel-cache] [yocto-5.10-rt] [PATCH] Fix warning from do_kernel_configcheck in intel-x86 bsp

[yocto] ERROR: ParseError at .../bbb-yocto-gatesgarth/meta-bbb/images/console-image.bb:4: Could not include required file images/basic-dev-image.bb

[yocto] using grpc fails with linker error: file in wrong format

20 matches

Site Navigation

Mail list logo

Footer information