[yocto] pyqt5 in yocto dunfell version #dunfell #pyqt5

[anthony . marchand]

Hello everyone,

I'm trying the dunfell version of yocto, to migrate from zeus to dunfell. I 
added the layer "meta-qt5", "meta-python2", "meta-openembedded".
The problem I meet follows:
In zeus version, I installed pyqt5 in my rootfs (recipe name is: 
python3-pyqt5). Actually, I tested the command "bitbake python3-pyqt5" for zeus 
version and it works fine. But for dunfell version, the same command raise an 
error.

The source: " 
https://www.riverbankcomputing.com/static/Downloads/PyQt5/5.13.2/PyQt5-5.13.2.tar.gz";
 ( 
https://www.riverbankcomputing.com/static/Downloads/PyQt5/5.13.2/PyQt5-5.13.2.tar.gz
 ) seems to does not exist. I have the error 404. I tested with a wget command 
and it's the same.

Do you have an idea about what's going wrong? Maybe the recipe for PyQt5 
(dunfell version) point to a bad adress.

Thanks for all and best reguards.

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

Re: [yocto] [meta-zephyr][PATCH 5/5] zephyr-flash-pyocd.bbclass: support for flashing via pyocd

[Wojciech Zmuda]

Hi Naveen,

You're right, I'm sorry. I didn't notice the rest of your comments. I'll
take care of it and will push v3 today with the rest of the changes.

Best regards,
Wojciech

On Tue, 8 Dec 2020 at 02:47, Saini, Naveen Kumar <
naveen.kumar.sa...@intel.com> wrote:

> You have missed few of my comments in v2 !
>
> Regards,
> Naveen
>
> -Original Message-
> From: Saini, Naveen Kumar
> Sent: Monday, December 7, 2020 8:06 PM
> To: 'Wojciech Zmuda' ; yocto@lists.yoctoproject.org
> Cc: davide.ri...@huawei.com; zbigniew.bo...@huawei.com;
> jaroslaw.ma...@huawei.com; robert.d...@huawei.com; Wojciech Zmuda <
> wojciech.zm...@huawei.com>
> Subject: RE: [yocto] [meta-zephyr][PATCH 5/5] zephyr-flash-pyocd.bbclass:
> support for flashing via pyocd
>
> Thanks for the patches.  Please find my comments below.
>
> -Original Message-
> From: yocto@lists.yoctoproject.org  On
> Behalf Of Wojciech Zmuda
> Sent: Monday, December 7, 2020 4:15 AM
> To: yocto@lists.yoctoproject.org
> Cc: davide.ri...@huawei.com; zbigniew.bo...@huawei.com;
> jaroslaw.ma...@huawei.com; robert.d...@huawei.com; Wojciech Zmuda <
> wojciech.zm...@huawei.com>
> Subject: [yocto] [meta-zephyr][PATCH 5/5] zephyr-flash-pyocd.bbclass:
> support for flashing via pyocd
>
> Flash boards supported via pyocd:
>
> MACHINE=xxx bitbake yyy -c flash_usb
>
> The only supported board for now is 96Boards Nitrogen. Modify its config
> accordingly.
>
> Modify helloworld and philosopers samples with adidtional .hex output file
> deployment, as this format is required by pyocd.
>
> Describe the feature in README.
>
> Signed-off-by: Wojciech Zmuda 
> ---
>  README.txt| 23 +++
>  classes/zephyr-flash-pyocd.bbclass| 17 ++
>  conf/machine/96b-nitrogen.conf|  1 +
>  .../zephyr-kernel/zephyr-helloworld.bb|  1 +
>  .../zephyr-kernel/zephyr-philosophers.bb  |  1 +
>  5 files changed, 43 insertions(+)
>  create mode 100644 classes/zephyr-flash-pyocd.bbclass
>
> diff --git a/README.txt b/README.txt
> index 6463339..4366764 100644
> --- a/README.txt
> +++ b/README.txt
> @@ -43,6 +43,29 @@ The same sample, for Nios2 image:
>  $ MACHINE=qemu-nios2 bitbake zephyr-philosophers
>  $ runqemu qemu-nios2
>
> +Flashing
> +=
> +
> +You can flash Zephyr samples to boards. Currently, the following
> +MACHINEs are supported:
> + * DFU:
> +  - arduino_101_sss
> +  - arduino_101
> +  - arduino_101_ble
> + * pyocd:
> +  - 96b_nitrogen
> +
> +To flash the example you built with command e.g.
> +
> +$ MACHINE=96b_nitrogen bitbake zephyr-philosophers
> [Naveen Saini] Typo here, MACHINE=96b-nitrogen
> +
> +call similar command with explicit flash_usb command:
> +
> +$ MACHINE=96b_nitrogen bitbake zephyr-philosophers -c flash_usb
> [Naveen Saini]  Same as above
>
> +
> +dfu-util and/or pyocd need to be installed in your system. If you
> +observe permission errors or the flashing process seem to hang, follow
> those instructions:
> +https://github.com/pyocd/pyOCD/tree/master/udev
>
>  Building and Running Zephyr Tests
>  =
> diff --git a/classes/zephyr-flash-pyocd.bbclass
> b/classes/zephyr-flash-pyocd.bbclass
> new file mode 100644
> index 000..aafe9e7
> --- /dev/null
> +++ b/classes/zephyr-flash-pyocd.bbclass
> @@ -0,0 +1,17 @@
> +
> +python do_flash_usb() {
> +from pyocd.core.helpers import ConnectHelper
> +from pyocd.flash.file_programmer import FileProgrammer
> +
> +image = f"{d.getVar('DEPLOY_DIR_IMAGE')}/{d.getVar('PN')}.hex"
> +bb.plain(f"Attempting to flash {image} to board
> + {d.getVar('BOARD')}")
> +
> +with ConnectHelper.session_with_chosen_probe() as session:
> +FileProgrammer(session).program(image)
> +session.board.target.reset()
> +}
> +
> +addtask do_flash_usb
> +
> +do_flash_usb[nostamp] = "1"
> +do_flash_usb[vardepsexclude] = "BB_ORIGENV"
> diff --git a/conf/machine/96b-nitrogen.conf
> b/conf/machine/96b-nitrogen.conf index d1905f2..998db4c 100644
> --- a/conf/machine/96b-nitrogen.conf
> +++ b/conf/machine/96b-nitrogen.conf
> @@ -4,4 +4,5 @@
>  #@DESCRIPTION: Machine configuration for 96Boards Nitrogen Board.
>
>  require conf/machine/include/nrf52832.inc
> +ZEPHYR_INHERIT_CLASSES += "zephyr-flash-pyocd"
>  ARCH_96b-nitrogen = "arm"
> diff --git a/recipes-kernel/zephyr-kernel/zephyr-helloworld.bb
> b/recipes-kernel/zephyr-kernel/zephyr-helloworld.bb
> index 1400e72..9b77975 100644
> --- a/recipes-kernel/zephyr-kernel/zephyr-helloworld.bb
> +++ b/recipes-kernel/zephyr-kernel/zephyr-helloworld.bb
> @@ -8,6 +8,7 @@ OECMAKE_SOURCEPATH = "${ZEPHYR_SRC_DIR}"
>
>  do_deploy () {
>  install -D ${B}/zephyr/${ZEPHYR_MAKE_OUTPUT}.elf
> ${DEPLOYDIR}/${PN}.elf
> +install -D ${B}/zephyr/${ZEPHYR_MAKE_OUTPUT}.hex
> + ${DEPLOYDIR}/${PN}.hex
>  }
> [Naveen Saini]  No *.hex file while building for MACHINE=qemu-x86  Error
> log:  ...build/zephyr/zephyr.hex':

Re: [yocto] perl5 do_install() fails (libperl.so: No such file or directory) #dunfell

[lobl . pavel]

Hi,

debian testing here, dunfell branch. I was able to get rid of the error with 
following patch. Not sure what's the reason though.

--- a/meta/recipes-devtools/perl/perl_5.30.1.bb
+++ b/meta/recipes-devtools/perl/perl_5.30.1.bb
@@ -146,7 +146,7 @@ do_install() {
install lib/ExtUtils/typemap ${D}${libdir}/perl5/${PV}/ExtUtils/

# Fix up shared library
-    rm ${D}/${libdir}/perl5/${PV}/*/CORE/libperl.so
+    rm ${D}/${libdir}/perl5/${PV}/${TARGET_ARCH}-linux/CORE/libperl.so
ln -sf ../../../../libperl.so.${PERL_LIB_VER} $(echo 
${D}/${libdir}/perl5/${PV}/*/CORE)/libperl.so
}

BR,
Pavel

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

[yocto] Yocto Project Status WW49'20

[Stephen Jolley]

Current Dev Position: YP 3.3 M2 development

Next Deadline: 18th January 2021 YP 3.3 M2 build 

 

Next Team Meetings:

*   Bug Triage meeting Thursday Dec. 10th at 7:30am PDT (

https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*   Monthly Project Meeting Tuesday Jan. 5th at 8am PDT (

https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09
 )
*   Weekly Engineering Sync Tuesday Dec. 8th at 8am PDT (

https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09
 )
*   Twitch -  See https://www.twitch.tv/theyoctojester

 

Key Status/Updates:

*   YP 3.2.1 is in QA
*   YP 3.1.4 was released
*   YP 3.3 M1 is due to be built this week once patches currently queued
stabilize
*   YP 3.3 development in master is continuing as patches are reviewed,
tested and merged with a focus on stabilization for M1.
*   After patches due to merge imminently for M1, reproducible builds
have taken a major step forward and we now have a specific exclusions list
of packages which don't build reproducibility. Thanks Alex for the work on
this!
*   Python3-pytest and its dependencies have merged to core due to our
desire for more automated package testing and the fact it's a dependency for
several recipes we need in core. Thanks Tim!
*   CVE statistics have regressed slightly for master as we've changed
the matching algorithms and more CVEs were 'identified' including several
many years old and likely not relevant. We'll work on resolving these over
time but the trend continues to be a significant reduction over time.
*   Intermittent autobuilder issues continue to occur. You can see the
list of failures we're continuing to see by searching for the "AB-INT" tag
in bugzilla:

https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT

 

Ways to contribute:

*   There are bugs identified as possible for newcomers to the project:

https://wiki.yoctoproject.org/wiki/Newcomers
*   There are bugs that are currently unassigned for YP 3.3. See:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.3_Unassigned_Enhan
cements.2FBugs
*   We'd welcome new maintainers for recipes in OE-Core. Please see the
list at:

http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/distro/include/main
tainers.inc and discuss with the existing maintainer, or ask on the OE-Core
mailing list. We will likely move a chunk of these to "Unassigned" soon to
help facilitate this.

 

YP 3.3 Milestone Dates:

*   YP 3.3 M1 build date 2020/12/07
*   YP 3.3 M1 Release date 2020/12/18
*   YP 3.3 M2 build date 2021/01/18
*   YP 3.3 M2 Release date 2021/01/29
*   YP 3.3 M3 build date 2021/03/01
*   YP 3.3 M3 Release date 2021/03/12
*   YP 3.3 M4 build date 2021/04/05
*   YP 3.3 M4 Release date 2021/04/30

 

Planned upcoming dot releases:

*   YP 3.1.4 is released.
*   YP 3.2.1 is in QA.
*   YP 3.2.1 release date 2020/12/4
*   YP 3.1.5 build date 2021/01/11
*   YP 3.1.5 release date 2021/01/22
*   YP 3.2.2 build date 2021/02/08
*   YP 3.2.2 release date 2021/02/19
*   YP 3.1.6 build date 2021/02/22
*   YP 3.1.6 release date 2021/03/05
*   YP 3.1.7 build date 2021/03/22
*   YP 3.1.7 release date 2021/04/02

 

Tracking Metrics:

*   WDD 2547 (last week 2527) (

https://wiki.yoctoproject.org/charts/combo.html)
*   Poky Patch Metrics  

*   Total patches found: 1288 (last week 1283)
*   Patches in the Pending State: 496 (39%) [last week 496 (39%)]

 

The Yocto Project's technical governance is through its Technical Steering
Committee, more information is available at:

 
https://wiki.yoctoproject.org/wiki/TSC

 

The Status reports are now stored on the wiki at:

https://wiki.yoctoproject.org/wiki/Weekly_Status

 

[If anyone has suggestions for other information you'd like to see on this
weekly status update, let us know!]

 

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 (#51693): https://lists.yoctoproject.org/g/yocto/message/51693
Mute This Topic: https://lists.yoctopr

[yocto] Build firmware and gcc cross compiler like gcc-arm-none-eabi (multilib vs multiconfig)

[Stefan Herbrechtsmeier]

Hi,

I wonder what is the best solution (multilib or multiconfig) to build a 
firmware and a gcc cross compiler like the Debian gcc-arm-none-eabi to 
build plugins for the firmware on an other machine.


I have two processors. A Poky based Linux distributions runs on the 
first processor and a RTOS firmware on the second processes. It looks 
like the best solution to build the RTOS firmware is multiconfig and 
separate machine configurations for each processors. But beside the RTOS 
firmware I need some headers, libraries and a gcc cross compiler for the 
RTOS in the Linux image. It is possible to share packages in multiconfig 
and how could I build a gcc cross compiler for an foreign machine.


Best regards
  Stefan

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

[yocto] [meta-cgl][PATCH] pacemaker: upgrade 2.0.3 -> 2.0.5

[Yi Zhao]

Drop backported patches:
0001-Mark-declaration-with-extern.patch
0006-Fix-tools-Fix-definition-of-curses_indented_printf.patch

Rebase patches:
0001-Fix-python3-usage.patch
0001-pacemaker-fix-compile-error-of-musl-libc.patch

Remove /var/log directory in do_install and create /var/log/pacemaker
directory in volatile file.

Signed-off-by: Yi Zhao 
---
 .../recipes-cgl/pacemaker/files/tmpfiles  |  3 +-
 .../recipes-cgl/pacemaker/files/volatiles |  1 +
 .../pacemaker/0001-Fix-python3-usage.patch| 34 --
 .../0001-Mark-declaration-with-extern.patch   | 46 ---
 ...maker-fix-compile-error-of-musl-libc.patch | 39 +++-
 ...definition-of-curses_indented_printf.patch | 30 
 ...{pacemaker_2.0.3.bb => pacemaker_2.0.5.bb} |  5 +-
 7 files changed, 21 insertions(+), 137 deletions(-)
 mode change 100755 => 100644 
meta-cgl-common/recipes-cgl/pacemaker/files/tmpfiles
 mode change 100755 => 100644 
meta-cgl-common/recipes-cgl/pacemaker/files/volatiles
 delete mode 100644 
meta-cgl-common/recipes-cgl/pacemaker/pacemaker/0001-Mark-declaration-with-extern.patch
 delete mode 100644 
meta-cgl-common/recipes-cgl/pacemaker/pacemaker/0006-Fix-tools-Fix-definition-of-curses_indented_printf.patch
 rename meta-cgl-common/recipes-cgl/pacemaker/{pacemaker_2.0.3.bb => 
pacemaker_2.0.5.bb} (96%)

diff --git a/meta-cgl-common/recipes-cgl/pacemaker/files/tmpfiles 
b/meta-cgl-common/recipes-cgl/pacemaker/files/tmpfiles
old mode 100755
new mode 100644
index 979db47..765ee0d
--- a/meta-cgl-common/recipes-cgl/pacemaker/files/tmpfiles
+++ b/meta-cgl-common/recipes-cgl/pacemaker/files/tmpfiles
@@ -3,4 +3,5 @@ d /var/lib/pacemaker/cib 0750 hacluster haclient -
 d /var/lib/pacemaker/cores 0750 hacluster haclient -
 d /var/lib/pacemaker/pengine 0750 hacluster haclient -
 d /var/lib/pacemaker/blackbox 0750 hacluster haclient -
-d /var/run/crm 0750 hacluster haclient -
+d /run/crm 0750 hacluster haclient -
+d /var/log/pacemaker 0750 hacluster haclient -
diff --git a/meta-cgl-common/recipes-cgl/pacemaker/files/volatiles 
b/meta-cgl-common/recipes-cgl/pacemaker/files/volatiles
old mode 100755
new mode 100644
index 1700a69..eca3002
--- a/meta-cgl-common/recipes-cgl/pacemaker/files/volatiles
+++ b/meta-cgl-common/recipes-cgl/pacemaker/files/volatiles
@@ -4,3 +4,4 @@ d hacluster haclient 0750 /var/lib/pacemaker/cores none
 d hacluster haclient 0750 /var/lib/pacemaker/pengine none
 d hacluster haclient 0750 /var/lib/pacemaker/blackbox none
 d hacluster haclient 0750 /var/run/crm none
+d hacluster haclient 0750 /var/log/pacemaker none
diff --git 
a/meta-cgl-common/recipes-cgl/pacemaker/pacemaker/0001-Fix-python3-usage.patch 
b/meta-cgl-common/recipes-cgl/pacemaker/pacemaker/0001-Fix-python3-usage.patch
index 05d7a76..2095227 100644
--- 
a/meta-cgl-common/recipes-cgl/pacemaker/pacemaker/0001-Fix-python3-usage.patch
+++ 
b/meta-cgl-common/recipes-cgl/pacemaker/pacemaker/0001-Fix-python3-usage.patch
@@ -1,4 +1,4 @@
-From fdefa9efc726fe704238d462a3dc207e0282fb9e Mon Sep 17 00:00:00 2001
+From f470884e0b990676685c8740b5c7d6f094267e4f Mon Sep 17 00:00:00 2001
 From: Jeremy Puhlman 
 Date: Sun, 15 Mar 2020 21:09:33 +
 Subject: [PATCH] Fix python3 usage
@@ -18,12 +18,11 @@ Upstream-Status: Pending
  cts/pacemaker-cts-dummyd.in   | 2 +-
  daemons/fenced/fence_legacy.in| 2 +-
  doc/Pacemaker_Development/en-US/Ch-Python.txt | 2 +-
- doc/Pacemaker_Development/pot/Ch-Python.pot   | 2 +-
  tools/pcmk_simtimes.in| 2 +-
- 14 files changed, 14 insertions(+), 14 deletions(-)
+ 13 files changed, 13 insertions(+), 13 deletions(-)
 
 diff --git a/cts/CTSlab.py.in b/cts/CTSlab.py.in
-index f4ae60dc1..55a0d4ecf 100644
+index 4bae93515..f09f71c66 100644
 --- a/cts/CTSlab.py.in
 +++ b/cts/CTSlab.py.in
 @@ -1,4 +1,4 @@
@@ -43,10 +42,10 @@ index 81a5da8c0..bbadf938a 100644
  '''OCF IPaddr/IPaddr2 Resource Agent Test'''
  
 diff --git a/cts/cluster_test.in b/cts/cluster_test.in
-index e0d28509d..f982be05a 100755
+index 38f941d3e..5a289e3fc 100755
 --- a/cts/cluster_test.in
 +++ b/cts/cluster_test.in
-@@ -171,4 +171,4 @@ printf "\nAll set to go for %d iterations!\n" 
"$CTS_numtests"
+@@ -172,4 +172,4 @@ printf "\nAll set to go for %d iterations!\n" 
"$CTS_numtests"
  || echo "+ To use a different configuration, remove ~/.cts and re-run cts 
(or edit it manually)."
  
  echo Now paste the following command into this shell:
@@ -63,7 +62,7 @@ index 592d850b4..9a653a442 100644
  """
  
 diff --git a/cts/cts-fencing.in b/cts/cts-fencing.in
-index 2dca0..8e3fb7203 100644
+index 02438..0270c99ce 100644
 --- a/cts/cts-fencing.in
 +++ b/cts/cts-fencing.in
 @@ -1,4 +1,4 @@
@@ -83,7 +82,7 @@ index 28f4efe7f..b4ed5024f 100644
  
  Reads a specified number of lines from the supplied offset
 diff --git a/cts/cts-scheduler.in b/cts/cts-scheduler.in
-index 8fa16fb69..d4306b02b 100644
+index 23e6a919f..09058ce22 100644
 --- a/cts/cts-scheduler.in
 +++ b/cts/cts-schedule