Date   

Next Zeus Dot release in May

Armin Kuster
 

Our next bot release is coming up so this is a call for patches. Please have them on the list by this Friday.


Planned upcoming dot releases:

  • YP 3.0.3 build date 2020/5/4
  • YP 3.0.3 release date 2020/5/15


Re: Certificate expired, https://git.yoctoproject.org/

Michael Halstead
 

The misconfiguration blocking certificate renewal is repaired and valid certs are available now.


On Tue, Apr 28, 2020 at 2:26 AM Andrei Gherzan <andrei@...> wrote:
Hi,

On 28 April 2020 09:54:41 BST, Stefano Babic <sbabic@...> wrote:
>Hi,
>
>certificate is expired - someone having the same issue ?

It did expire, indeed.

git.yoctoproject.org uses an invalid security certificate. The certificate expired on 28 April 2020, 07:51:54 GMT+1. The current time is 28 April 2020, 10:21. Error code: SEC_ERROR_EXPIRED_CERTIFICATE
--
Andrei Gherzan
gpg: rsa4096/D4D94F67AD0E9640 | t: @agherzan



--
Michael Halstead
Linux Foundation / Yocto Project
Systems Operations Engineer


Yocto Project Status WW17'20

Stephen Jolley
 

Current Dev Position: YP 3.2 M1

Next Deadline: YP 3.2 M1 build date 2020/6/16

 

Next Team Meetings:

 

Key Status/Updates:

  • YP 3.1 was released, thanks to everyone who contributed!
  • The stable maintainer for the 3.1 LTS release is Steve Sakoman
  • YP 3.1 (dunfell) has been announced as an LTS release: https://www.yoctoproject.org/yocto-project-long-term-support-announced/
  • Patches have started merging again into master. We’ve already had some challenging issues to debug with them on the autobuilder where the root cause turned out to be an underlying QA test code issue exposed by test ordering issues.
  • Master branch development will open up later this week, there are already some patches queued and tested in master-next
  • The multilib discussion on the openembedded-architecture list has continued with the potential of new bitbake support to better enable class extensions (which enable native and nativesdk variants as well as multilib).
  • We’ve identified some issues with the new buildtools-extended-tarball so we’ll be making a new version of that and porting fixes to the stable branch.
  • We are aware of some issues with bug trend metrics this week due to server transitions and are working to resolve those.

 

YP 3.2 Milestone Dates:

  • YP 3.2 M1 build date 2020/6/16
  • YP 3.2 M1 Release date 2020/6/26
  • YP 3.2 M2 build date 2020/7/27
  • YP 3.2 M2 Release date 2020/8/7
  • YP 3.2 M3 build date 2020/8/31
  • YP 3.2 M3 Release date 2020/9/11
  • YP 3.2 M4 build date 2020/10/5
  • YP 3.2 M4 Release date 2020/10/30

 

Planned upcoming dot releases:

  • YP 3.0.3 build date 2020/5/4
  • YP 3.0.3 release date 2020/5/15
  • YP 2.7.4 build date 2020/5/18
  • YP 2.7.4 release date 2020/5/29
  • YP 3.1.1 build date 2020/6/29
  • YP 3.1.1 release date 2020/7/10
  • YP 3.0.4 build date 2020/8/10
  • YP 3.0.4 release date 2020/8/21
  • YP 3.1.2 build date 2020/9/14
  • YP 3.1.2 release date 2020/9/25

 

Tracking Metrics:

 

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.pm@...

 


Re: Certificate expired, https://git.yoctoproject.org/

Andrei Gherzan
 

Hi,

On 28 April 2020 09:54:41 BST, Stefano Babic <sbabic@...> wrote:
Hi,

certificate is expired - someone having the same issue ?
It did expire, indeed.

git.yoctoproject.org uses an invalid security certificate. The certificate expired on 28 April 2020, 07:51:54 GMT+1. The current time is 28 April 2020, 10:21. Error code: SEC_ERROR_EXPIRED_CERTIFICATE
--
Andrei Gherzan
gpg: rsa4096/D4D94F67AD0E9640 | t: @agherzan


Certificate expired, https://git.yoctoproject.org/

Stefano Babic
 

Hi,

certificate is expired - someone having the same issue ?

Regards,
Stefano

--
=====================================================================
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic@...
=====================================================================


Re: Which recipe for Linux tools to run u-boot command inside Linux?

Yann Dirson
 

Hello,

It depends on the yocto version.  Since dunfell they are in libubootenv-bin, before that they were in u-boot-fw-utils.

Le mar. 28 avr. 2020 à 10:04, JH <jupiter.hce@...> a écrit :
Hi,

I was told you can run u-boot command inside of Linux, which recipe
can be used in Yocto for install that package?

Thank you.

Kind regards,

- jh


--
"A man can fail many times, but he isn't a failure until he begins to
blame somebody else."
-- John Burroughs



--
Yann Dirson <yann@...>
Blade / Shadow -- http://shadow.tech


Which recipe for Linux tools to run u-boot command inside Linux?

JH
 

Hi,

I was told you can run u-boot command inside of Linux, which recipe
can be used in Yocto for install that package?

Thank you.

Kind regards,

- jh


--
"A man can fail many times, but he isn't a failure until he begins to
blame somebody else."
-- John Burroughs


Enabling logging for python script in poky layer

raxeshkumar.oriya@ncr.com
 

Hi,

 

I want to see all the logs which are thrown by a python script present in yocto poky layer for my debugging. How do I do that?

 

Python script location – “poky/scripts/lib/wic/plugins/source/bootimg-pcbios.py

 

What I tried and didn’t work out?

  • bitbake core-image-minimal -v -DDD
  • Added logging.basicConfig(level=logging.DEBUG, filename='bbhashserv.log', filemode='w') line to bootimg-pcbios.py

 

Any lead on this would be really appreciated.

 

Regards,

Raxesh Oriya

Senior Software Engineer

NCR Corporation

 


Re: Unable to build core-image-full-cmdline on openSUSE Leap 15.1: dnf can't find _curses module in do_rootfs task

Alexander Kanavin
 


On Mon, 27 Apr 2020 at 19:51, <bpeter@...> wrote:
I'm experiencing the same problem with yocto zeus on both OpenSuse Leap 15.0 and 15.1. Were you able to find a resolution for this issue?

I've been investigating and found problems with some of the libraries built for python3-native. They're missing some dependencies:

/home/brendan/workspaces/imx-linux-zeus/build_fsl-imx-xwayland/tmp/sysroots-components/x86_64/python3-native/usr/lib/python3.7/lib-dynload/_curses.cpython-37m-x86_64-linux-gnu_failed.so
/home/brendan/workspaces/imx-linux-zeus/build_fsl-imx-xwayland/tmp/sysroots-components/x86_64/python3-native/usr/lib/python3.7/lib-dynload/_curses_panel.cpython-37m-x86_64-linux-gnu_failed.so

readelf -d | grep NEEDED
 0x0000000000000001 (NEEDED)             Shared library: [libpanelw.so.5]
 0x0000000000000001 (NEEDED)             Shared library: [libncursesw.so.5]
 0x0000000000000001 (NEEDED)             Shared library: [libtinfo.so.5]
 0x0000000000000001 (NEEDED)             Shared library: [libpython3.7m.so.1.0]
 0x0000000000000001 (NEEDED)             Shared library: [libpthread.so.0]
 0x0000000000000001 (NEEDED)             Shared library: [libc.so.6]


Re: Unable to build core-image-full-cmdline on openSUSE Leap 15.1: dnf can't find _curses module in do_rootfs task

bpeter@...
 

I'm experiencing the same problem with yocto zeus on both OpenSuse Leap 15.0 and 15.1. Were you able to find a resolution for this issue?

I've been investigating and found problems with some of the libraries built for python3-native. They're missing some dependencies:

/home/brendan/workspaces/imx-linux-zeus/build_fsl-imx-xwayland/tmp/sysroots-components/x86_64/python3-native/usr/lib/python3.7/lib-dynload/_curses.cpython-37m-x86_64-linux-gnu_failed.so
/home/brendan/workspaces/imx-linux-zeus/build_fsl-imx-xwayland/tmp/sysroots-components/x86_64/python3-native/usr/lib/python3.7/lib-dynload/_curses_panel.cpython-37m-x86_64-linux-gnu_failed.so

readelf -d | grep NEEDED
 0x0000000000000001 (NEEDED)             Shared library: [libpanelw.so.5]
 0x0000000000000001 (NEEDED)             Shared library: [libncursesw.so.5]
 0x0000000000000001 (NEEDED)             Shared library: [libtinfo.so.5]
 0x0000000000000001 (NEEDED)             Shared library: [libpython3.7m.so.1.0]
 0x0000000000000001 (NEEDED)             Shared library: [libpthread.so.0]
 0x0000000000000001 (NEEDED)             Shared library: [libc.so.6]


M+ & H bugs with Milestone Movements WW17

Stephen Jolley
 

All,

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

Priority

Bug ID

Short Description

Changer

Owner

Was

Became

Medium+

5389

bitbake/lib/bb/fetch2: filename too long

randy.macleod@...

unassigned@...

3.2

3.2 M1

 

7600

syslinux: port extX support patches to syslinux community

randy.macleod@...

unassigned@...

3.99

3.2 M1

 

11138

Extensible SDK: recipe-specific sysroots broke user additions to the SDK's shared sysroot

richard.purdie@...

unassigned@...

Future

3.99

 

11351

go-native: do_compile failed when len(tmp) = 410

randy.macleod@...

unassigned@...

3.2

3.2 M1

 

12347

llvm-native: do_configure failed when len(TMPDIR) == 410

randy.macleod@...

unassigned@...

3.2

3.2 M1

 

12362

webkitgtk: do_compile failed when len(TMPDIR) == 410

randy.macleod@...

unassigned@...

3.2

3.2 M1

 

12374

do_rootfs failed when len(TMPDIR) == 410

randy.macleod@...

unassigned@...

3.99

3.2 M1

 

13581

Line wrapping over prompt in BASH

randy.macleod@...

jason.wessel@...

3.2 M1

3.2 M2

 

13616

sql error on recipes using multiple git repos

richard.purdie@...

akuster@...

3.2 M1

3.0.3

 

13690

runqemu with slirp, forwarded host ports are not available on host

timothy.t.orling@...

timothy.t.orling@...

3.1 M4

3.2 M1

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Enhancements/Bugs closed WW17!

Stephen Jolley
 

All,

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

Who

Count

randy.macleod@...

4

richard.purdie@...

2

Grand Total

6

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Current Top developers on Yocto Project 3.2

Stephen Jolley
 

All,

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

Who

Count

richard.purdie@...

28

david.reyna@...

18

bluelightning@...

17

akuster808@...

16

bruce.ashfield@...

11

mark.morton@...

10

Qi.Chen@...

9

kai.kang@...

9

randy.macleod@...

8

ross@...

7

trevor.gamblin@...

6

michael@...

6

timothy.t.orling@...

6

changqing.li@...

6

jon.mason@...

5

JPEWhacker@...

5

alejandro@...

4

pbarker@...

4

alex.kanavin@...

4

mingli.yu@...

4

raj.khem@...

3

yi.zhao@...

3

akuster@...

3

hongxu.jia@...

3

jpuhlman@...

2

matthew.zeng@...

2

ycnakajsph@...

2

seebs@...

2

rpjday@...

2

jaewon@...

2

mark.hatle@...

2

yang.wang@...

2

mostthingsweb@...

2

kergoth@...

2

kexin.hao@...

2

limon.anibal@...

2

chee.yang.lee@...

2

amber.n.elliot@...

1

nicolas.dechesne@...

1

apoorv.sangal@...

1

Martin.Jansa@...

1

mshah@...

1

bunk@...

1

naveen.kumar.saini@...

1

liu.ming50@...

1

dl9pf@...

1

kai.ruhnau@...

1

denis@...

1

maxime.roussinbelanger@...

1

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Yocto Project Newcomer & Unassigned Bugs - Help Needed

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

 

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 337 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.1”, “3.2, "3.99" and "Future", the more pressing/urgent issues being in "3.1" and then “3.2”.

 

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.pm@...) 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.pm@...

 


[meta-rockchip][PATCH] arm-trusted-firmware: Upgrade 2.2 -> 2.3

Joshua Watt
 

Upgrades arm-trusted-firmware to the latest version, which fixes a bug
where the RK3399 would hang during a warm reboot

Signed-off-by: Joshua Watt <JPEWhacker@...>
---
...hip-Prevent-macro-expansion-in-paths.patch | 94 -------------------
...are_2.2.bb => arm-trusted-firmware_2.3.bb} | 3 +-
2 files changed, 1 insertion(+), 96 deletions(-)
delete mode 100644 recipes-bsp/arm-trusted-firmware/arm-trusted-firmware/0001-rockchip-Prevent-macro-expansion-in-paths.patch
rename recipes-bsp/arm-trusted-firmware/{arm-trusted-firmware_2.2.bb => arm-trusted-firmware_2.3.bb} (89%)

diff --git a/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware/0001-rockchip-Prevent-macro-expansion-in-paths.patch b/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware/0001-rockchip-Prevent-macro-expansion-in-paths.patch
deleted file mode 100644
index 755b618..0000000
--- a/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware/0001-rockchip-Prevent-macro-expansion-in-paths.patch
+++ /dev/null
@@ -1,94 +0,0 @@
-From 39a97dce61aca9f618e28e26c6e441c8976f3172 Mon Sep 17 00:00:00 2001
-From: Joshua Watt <JPEWhacker@...>
-Date: Fri, 13 Dec 2019 13:44:55 -0600
-Subject: [PATCH] rockchip: Prevent macro expansion in paths
-
-Instead of stringizing the paths to binary files, add them as string
-defines on the command line (e.g. -DFOO=\"BAR\" instead of -DFOO=BAR).
-This prevents macros from being expanded inside the string value itself.
-For example, -DFOO=/path/with-linux-in-it would have been expanded to
-"/path/with-1-in-it" because `linux=1` is one of the standard GCC
-defines.
-
-Upstream-Status: Accepted [https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/2813]
-Change-Id: I7b65df3c9930faed4f1aff75ad726982ae3671e6
-Signed-off-by: Joshua Watt <JPEWhacker@...>
----
- plat/rockchip/rk3399/drivers/dp/cdn_dp.c | 2 +-
- plat/rockchip/rk3399/drivers/pmu/pmu_fw.c | 24 +++++++++++------------
- plat/rockchip/rk3399/platform.mk | 6 +++---
- 3 files changed, 15 insertions(+), 17 deletions(-)
-
-diff --git a/plat/rockchip/rk3399/drivers/dp/cdn_dp.c b/plat/rockchip/rk3399/drivers/dp/cdn_dp.c
-index aa71fdea..a8773f4f 100644
---- a/plat/rockchip/rk3399/drivers/dp/cdn_dp.c
-+++ b/plat/rockchip/rk3399/drivers/dp/cdn_dp.c
-@@ -18,7 +18,7 @@ __asm__(
- ".global hdcp_handler\n"
- ".balign 4\n"
- "hdcp_handler:\n"
-- ".incbin \"" __XSTRING(HDCPFW) "\"\n"
-+ ".incbin \"" HDCPFW "\"\n"
- ".type hdcp_handler, %function\n"
- ".size hdcp_handler, .- hdcp_handler\n"
- ".popsection\n"
-diff --git a/plat/rockchip/rk3399/drivers/pmu/pmu_fw.c b/plat/rockchip/rk3399/drivers/pmu/pmu_fw.c
-index a09ad21e..25596b18 100644
---- a/plat/rockchip/rk3399/drivers/pmu/pmu_fw.c
-+++ b/plat/rockchip/rk3399/drivers/pmu/pmu_fw.c
-@@ -5,20 +5,18 @@
- */
-
- /* convoluted way to make sure that the define is pasted just the right way */
--#define _INCBIN(file, sym, sec) \
-+#define INCBIN(file, sym, sec) \
- __asm__( \
-- ".section " #sec "\n" \
-- ".global " #sym "\n" \
-- ".type " #sym ", %object\n" \
-+ ".section " sec "\n" \
-+ ".global " sym "\n" \
-+ ".type " sym ", %object\n" \
- ".align 4\n" \
-- #sym ":\n" \
-- ".incbin \"" #file "\"\n" \
-- ".size " #sym ", .-" #sym "\n" \
-- ".global " #sym "_end\n" \
-- #sym "_end:\n" \
-+ sym ":\n" \
-+ ".incbin \"" file "\"\n" \
-+ ".size " sym ", .-" sym "\n" \
-+ ".global " sym "_end\n" \
-+ sym "_end:\n" \
- )
-
--#define INCBIN(file, sym, sec) _INCBIN(file, sym, sec)
--
--INCBIN(RK3399M0FW, rk3399m0_bin, ".sram.incbin");
--INCBIN(RK3399M0PMUFW, rk3399m0pmu_bin, ".pmusram.incbin");
-+INCBIN(RK3399M0FW, "rk3399m0_bin", ".sram.incbin");
-+INCBIN(RK3399M0PMUFW, "rk3399m0pmu_bin", ".pmusram.incbin");
-diff --git a/plat/rockchip/rk3399/platform.mk b/plat/rockchip/rk3399/platform.mk
-index cfc48e8f..643c24f5 100644
---- a/plat/rockchip/rk3399/platform.mk
-+++ b/plat/rockchip/rk3399/platform.mk
-@@ -82,13 +82,13 @@ PLAT_M0 := ${PLAT}m0
- BUILD_M0 := ${BUILD_PLAT}/m0
-
- RK3399M0FW=${BUILD_M0}/${PLAT_M0}.bin
--$(eval $(call add_define,RK3399M0FW))
-+$(eval $(call add_define_val,RK3399M0FW,\"$(RK3399M0FW)\"))
-
- RK3399M0PMUFW=${BUILD_M0}/${PLAT_M0}pmu.bin
--$(eval $(call add_define,RK3399M0PMUFW))
-+$(eval $(call add_define_val,RK3399M0PMUFW,\"$(RK3399M0PMUFW)\"))
-
- HDCPFW=${RK_PLAT_SOC}/drivers/dp/hdcp.bin
--$(eval $(call add_define,HDCPFW))
-+$(eval $(call add_define_val,HDCPFW,\"$(HDCPFW)\"))
-
- # CCACHE_EXTRAFILES is needed because ccache doesn't handle .incbin
- export CCACHE_EXTRAFILES
---
-2.23.0
-
diff --git a/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_2.2.bb b/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_2.3.bb
similarity index 89%
rename from recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_2.2.bb
rename to recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_2.3.bb
index abaf0f3..8d36d66 100644
--- a/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_2.2.bb
+++ b/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_2.3.bb
@@ -14,9 +14,8 @@ PROVIDES = "virtual/atf"

BRANCH = "master"
SRC_URI = "git://git.trustedfirmware.org/TF-A/trusted-firmware-a.git;protocol=http;branch=${BRANCH} \
- file://0001-rockchip-Prevent-macro-expansion-in-paths.patch \
"
-SRCREV = "a04808c16cfc126d9fe572ae7c4b5a3d39de5796"
+SRCREV = "8ff55a9e14a23d7c7f89f52465bcc6307850aa33"

S = "${WORKDIR}/git"
B = "${WORKDIR}/build"
--
2.17.1


Re: Building Qt5 toolchain for windows

Samuli Piippo
 

Hi,

Our changes for supporting mingw builds for Qt5 nativesdk tools are still part of the meta-boot2qt layer (https://code.qt.io/cgit/yocto/meta-boot2qt.git/), which is used in the Qt for Device Creation product. Some of these changes could be moved over to meta-qt5. CMake support is still partial and will only work with the Qt Creator integration.

-samuli



From: d.fourdrigniez@... <d.fourdrigniez@...>
Sent: 22 April 2020 18:38
To: 'Joshua Watt' <jpewhacker@...>
Cc: Samuli Piippo <samuli.piippo@...>; yocto@... <yocto@...>
Subject: RE: [Yocto] Building Qt5 toolchain for windows
 

Hello Joshua,

 

Thank you for your reply,

 

Just for information, I put the following parameters in local.conf

 

MACHINE ?= “qemuarm”

 

SDKMACHINE = “i686-mingw32”

 

IMAGE_INSTALL_append = “ gcc g++ binutils libgcc-dev libstdc++ libstdc++-dev libstdc++-staticdev qtbase qtcharts qtconnectivity qtdeclarative qtenginio qtgraphicaleffects qtlocation qtmultimedia qtscript qtsensors qtserialport qtsystems qttools qttranslations qtvirtualkeyboard qtwebsockets qtxmlpatterns openssh-sftp-server gdb gdbserver”

 

And here is the error I get when I run the command: bitbake meta-toolchain-qt5

 

| In file included from /home/david/yocto/poky/build/tmp/work/i686-nativesdk-mingw32-pokysdk-mingw32/nativesdk-qtbase/5.13.2+gitAUTOINC+a7a24784ee-r0/recipe-sysroot/opt/poky/3.0.2/sysroots/i686-pokysdk-mingw32/usr/include/winbase.h:18,

|                  from /home/david/yocto/poky/build/tmp/work/i686-nativesdk-mingw32-pokysdk-mingw32/nativesdk-qtbase/5.13.2+gitAUTOINC+a7a24784ee-r0/recipe-sysroot/opt/poky/3.0.2/sysroots/i686-pokysdk-mingw32/usr/include/windows.h:70,

|                  from /home/david/yocto/poky/build/tmp/work/i686-nativesdk-mingw32-pokysdk-mingw32/nativesdk-qtbase/5.13.2+gitAUTOINC+a7a24784ee-r0/git/qmake/library/ioutils.cpp:35:

| /home/david/yocto/poky/build/tmp/work/i686-nativesdk-mingw32-pokysdk-mingw32/nativesdk-qtbase/5.13.2+gitAUTOINC+a7a24784ee-r0/recipe-sysroot/opt/poky/3.0.2/sysroots/i686-pokysdk-mingw32/usr/include/fileapi.h:53:48: note:   initializing argument 1 of 'void* CreateFileA(LPCSTR, DWORD, DWORD, LPSECURITY_ATTRIBUTES, DWORD, DWORD, HANDLE)'

|    53 |   WINBASEAPI HANDLE WINAPI CreateFileA (LPCSTR lpFileName, DWORD dwDesiredAccess, DWORD dwShareMode, LPSECURITY_ATTRIBUTES lpSecurityAttributes, DWORD dwCreationDisposition, DWORD dwFlagsAndAttributes, HANDLE hTemplateFile);

|       |                                         ~~~~~~~^~~~~~~~~~

| Makefile:212: recipe for target 'ioutils.o' failed

| make: *** [ioutils.o] Error 1

| WARNING: exit code 2 from a shell command.

|

ERROR: Task (/home/david/yocto/poky/meta-qt5/recipes-qt/qt5/nativesdk-qtbase_git.bb:do_configure) failed with exit code '1'

NOTE: Tasks Summary: Attempted 3299 tasks of which 3161 didn't need to be rerun and 1 failed.

 

Summary: 1 task failed:

  /home/david/yocto/poky/meta-qt5/recipes-qt/qt5/nativesdk-qtbase_git.bb:do_configure

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

 

Best regards,

 

David FOURDRIGNIEZ
Mobile +33 6 27 94 03 25

Email d.fourdrigniez@...

 

From: Joshua Watt <jpewhacker@...>
Sent: mardi 21 avril 2020 13:20
To: d.fourdrigniez@...
Cc: Samuli Piippo <samuli.piippo@...>; yocto@...
Subject: Re: [Yocto] Building Qt5 toolchain for windows

 

 

On 4/21/20 1:00 PM, d.fourdrigniez@... wrote:

Hello,

 

I’m working on a project and I need to build a Qt5 toolchain for Windows,

I’m using meta-qt5 and meta-mingw and my build machine is an ubuntu 18.04

However I keep having errors when i execute « bitbake meta-toolchain-qt5 », very much like the one in below forum thread 

https://www.yoctoproject.org/pipermail/yocto/2019-March/044512.html

 

Am I doing something wrong ? Could you help sending me some ideas on how I could accomplish what I want ?

 

I don't actually know a whole lot about cmake/qt5, so I'm not sure what would need to be done (other than what I've already stated in the message above). Samuli Piippo (cc'd) recently did some work to get cmake to build for MinGW, so he might have some insight.

 

Thanks,

 

Best regards,

David Fourdrigniez.


dpkg doesn't work

nus1998 <nus1998@...>
 

Hi All,

I'm running imx-linux-zeus 5.4.3_1.0.0 on i.MX6 sabresd board but I think this issue might be HW independent.

I set PACKAGE_CLASSES ?= 'package_deb' in my local.conf file and the deb packages are generated in each package. however, in rootfs, all the /usr/bin/dpkg* are 0 bytes except dpkg-deb and dpkg-split, thus I can't use dpkg or apt-get to install deb package. doesn't anybody know how to set it up to install deb package on target board?

B.R.
Nus


zeus KCFLAGS

Damien LEFEVRE
 

Hi,

I'm trying to build the core-image-minimal on zeus branch, device Tegra Xavier. The compiler has to be GCC 7.* due to some NVidia pre-built binaries. So I back ported it from Thud if I recall.

The kernel compilation fails with this error:
| cc1: error: -Werror=address-of-packed-member: no option -Waddress-of-packed-member
| cc1: error: -Werror=missing-attributes: no option -Wmissing-attributes

How to I make the compiler treat these error as warnings?

I've tried adding all these to the kernel recipe:
export KCFLAGS = " -Wno-error=address-of-packed-member -Wno-error=missing-attributes "
export KCPPFLAGS = " -Wno-error=address-of-packed-member -Wno-error=missing-attributes "

TARGET_CFLAGS += " -Wno-error=address-of-packed-member -Wno-error=missing-attributes "
TARGET_CPPFLAGS += " -Wno-error=address-of-packed-member -Wno-error=missing-attributes "

KBUILD_CFLAGS += " -Wno-error=address-of-packed-member -Wno-error=missing-attributes "

None of them seems to be applied.

Anything special changed on Zeus? Note I didn't have any issue building the kernel on Warrior.

Thanks
-Damien


Re: Web interface for Yocto & OE mailing lists defaults to Reply to Sender

Nicolas Dechesne
 

hi Paul,

On Sat, Apr 25, 2020 at 12:54 PM Paul Barker <pbarker@...> wrote:
Michael,

I've just been discussing on IRC with Bartłomiej who used the groups.io web
interface to reply to an email on the list. It defaulted to sending a private
reply off the list. If I try to do the same "Reply to Sender" is the default
for me as well: https://imgur.com/1RGH9Aw

Looking at the AGL lists on groups.io they have "Reply to Group" as the
default. Perhaps this is a configuration issue? Could you take when you get
chance?

Right. It's a per list configuration item. I have changed for yocto list for now, and set it to 'reply to group'. we will take care of all lists (and on lists.openembedded.org as well). Thanks for spotting this.


Thanks,

--
Paul Barker
Konsulko Group


Kernel panic of "not syncing" occurs when booting on qemu with extracted code by devtool #yocto #devtool #qemu

Hao Qian
 

Hi,

I'm trying to add some drivers to linux kernel and confirm it with qemu.

I clone the poky repository, build and boot as below steps:
----------------------------------------------------------------------------
1. clone poky (poky only)
$ git clone git://git.yoctoproject.org/poky
2. initialize build folder by oe-init-build-env
$ source poky/oe-init-build-env ./build
3. extract linux repository (but do no modifications)
$ devtool modify virtual/kernel
4. build with default configurations
$ bitbake core-image-minimal
5. boot on qemux86-64
$ runqemu nographic
----------------------------------------------------------------------------
and I can boot linux without any panic at this time.


However, when I try to re-build and boot again, I got a panic at boot time 100%.
What I did are listed below:
----------------------------------------------------------------------------
6. re-build with clean
$ bitbake virtual/kernel -c clean && bitbake core-image-minimal -c
clean && bitbake core-image-minimal
(I also tried replacing "-c clean" with "-c cleanall", adding "rm
-rf tmp/ cache/ sstate/", but got same panic error)
7. boot on qemux86-64
$ runqemu nographic
(also tried "runqemu qemux86-64 nographic")
----------------------------------------------------------------------------

The log of panic is:
============= panic log ===============
[ 2.177811] rtc_cmos 00:00: setting system clock to
2020-04-03T22:35:00 UTC (1585953300)
[ 2.186697] md: Waiting for all devices to be available before autodetect
[ 2.186838] md: If you don't use raid, use raid=noautodetect
[ 2.189483] md: Autodetecting RAID arrays.
[ 2.189595] md: autorun ...
[ 2.189665] md: ... autorun DONE.
[ 2.190837] VFS: Cannot open root device "vda" or
unknown-block(0,0): error -6
[ 2.190993] Please append a correct "root=" boot option; here are
the available partitions:
[ 2.191290] 0b00 1048575 sr0
[ 2.191310] driver: sr
[ 2.191485] VFS: Unable to mount root fs on unknown-block(0,0)
[ 2.191606] User configuration error - no valid root filesystem found
[ 2.191797] Kernel panic - not syncing: Invalid configuration from
end user prevents continuing
[ 2.192134] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.2.32 #1
[ 2.192279] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996),
BIOS rel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org 04/01/2014
[ 2.192613] Call Trace:
[ 2.193218] dump_stack+0x6d/0x9a
[ 2.193337] panic+0x101/0x2d7
[ 2.193445] mount_block_root+0x2cf/0x2f2
[ 2.193538] mount_root+0x7d/0x80
[ 2.193612] prepare_namespace+0x13f/0x177
[ 2.193701] kernel_init_freeable+0x236/0x25a
[ 2.193798] ? rest_init+0xb0/0xb0
[ 2.193872] kernel_init+0xe/0x100
[ 2.193946] ret_from_fork+0x35/0x40
[ 2.194488] Kernel Offset: 0x2e00000 from 0xffffffff81000000
(relocation range: 0xffffffff80000000-0xffffffffbfffffff)
[ 2.194918] ---[ end Kernel panic - not syncing: Invalid
configuration from end user prevents continuing ]---
======================================

P.S. panic will not happen if I didn't extract linux repository
with "devtool modify" command.


I've tried to search answers on yocto-mailing-list, stackoverflow, nxp
community and other websites, but can not find any solution for this
problem.

Could anyone please help to fix this problem, or just offers some advices?

Best regards,
Qian

8141 - 8160 of 57398