Date   

Re: 答复: QA completion for completed autobuilder build (yocto-2.7.4.rc2)

Li, Xiaoming
 

Hi,Sangeeta

Are your test case and test steps open source ?
If yes, where can I get it ? Thanks a lot.

Best
Li

-----邮件原件-----
发件人: yocto@lists.yoctoproject.org [mailto:yocto@lists.yoctoproject.org] 代
表 Sangeeta Jain
发送时间: 2020年6月1日 15:26
收件人: yocto@lists.yoctoproject.org
抄送: otavio@ossystems.com.br; yi.zhao@windriver.com; Sangal, Apoorv
<apoorv.sangal@intel.com>; Chan, Aaron Chun Yew
<aaron.chun.yew.chan@intel.com>; richard.purdie@linuxfoundation.org;
akuster808@gmail.com; sjolley.yp.pm@gmail.com; Tummalapalli, Vineela
<vineela.tummalapalli@intel.com>
主题: [yocto] QA completion for completed autobuilder build (yocto-2.7.4.rc2)

Hello all,

This is the full report for yocto-2.7.4.rc2:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=inte
l-yocto-testresults

======= Summary ========
No high milestone defects.
No new defects are found in this cycle.

Note: Few failures are observed. These are setup issues, not real yocto issue.

Thanks,
Sangeeta


Re: Eclipse GDB setup issues; can't determine cause for SIGSEGV

Bryan Evenson
 

All,

-----Original Message-----
From: yocto@lists.yoctoproject.org <yocto@lists.yoctoproject.org> On
Behalf Of Bryan Evenson via lists.yoctoproject.org
Sent: Monday, June 1, 2020 11:16 AM
To: yocto@lists.yoctoproject.org
Subject: [yocto] Eclipse GDB setup issues; can't determine cause for SIGSEGV

All,

I have a AT91SAM9G25 system that has been idle for a couple years (running
morty, yocto version 2.2.1) and I am working on updating to the latest Yocto
production branch. Before I get there, I'm trying to confirm the old setup
and I'm having problems with remote debugging. I know there have been
changes since yocto version 2.7 for debugging support, so I want to make
sure I can get the old setup to work first prior to changing everything. I'm
looking for assistance in tracking down my debug issues.

My stable production image is based off of core-image-minimal, with a few
additional packages for our proprietary applications (proprietary applications
are written in C). I also have a development image, based off of our
production image, with the following additions:

IMAGE_FEATURES += "package-management dev-pkgs eclipse-debug allow-
empty-password empty-root-password"

IMAGE_INSTALL += " \
#same additional packages as production image \
#"-dbg" version of proprietary applications \
gdbserver \
"
# Strip python from the image to reduce the image size
PACKAGE_EXCLUDE = "python"

I have the Eclipse Yocto plugin installed and it is setup to use the SDK that I
have built based on the development image. I've confirmed that I can start a
debug session on one of our proprietary applications. I can set breakpoints
and run the debugger. However, the debugger always stops at the first call
to uuid_compare with a SIGSEGV. The last line in the call stack states
"<symbol is not available> 0x00000000". From my understanding, the stack
pointer is getting set to NULL when uuid_compare is getting called. If I stop
the debugger and just run the application on the hardware, the application
runs without errors. I have confirmed with syslog messages that I do not
have the same NULL stack pointer issue when I run the application outside of
the debugger.

Any suggestions on where to start looking? I don't see any obvious possible
causes and I don't know where to start looking for the problem.
On a whim, I changed in my code:
if(uuid_compare(uuid1, uuid2) == 0)

To:
If(memcmp(uuid1, uuid2, 16) == 0)

After this change the problematic line of code worked just fine. The debugger worked fine until I got to the next spot in my code that called uuid_compare. At the next call to uuid_compare I got the same SIGSEGV error I had before. Something is clearly a problem with calling uuid_compare. However, I'm using several other functions from the uuid library (uuid_is_null, uuid_parse, uuid_unparse for a few) and none of them are causing problems. I don't think it's a problem with the input parameters because I'm passing the same UUIDs to memcomp as I did to uuid_compare. Has anyone ever seen only one function from a library cause problems like this?

Thanks,
Bryan


Re: Can I build Yocto Arm Image without QEMU?

Mark Van De Vyver <mark@...>
 

On Mon, Jun 1, 2020 at 2:36 AM Sergei Nikulov <sergey.nikulov@...> wrote:


вс, 31 мая 2020 г., 14:15 Олег Гаврильченко via lists.yoctoproject.org <reffum=bk.ru@...>:
Hello!
Sorry for my English. My first language is Russian.
I have a question about build yocto image. Can I build image without build any QEMU packages? And how can I do it?

Yes, you can.
Check MACHINE variable in documentation.

HTH:


You should set it to specific HW you're using.

I do not neet QEMU, I run Linux only in hardware.
Thank you for answers.
 
 



M+ & H bugs with Milestone Movements WW22

Stephen Jolley
 

All,

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

Priority

Bug ID

Short Description

Changer

Owner

Was

Became

Medium+

8805

Detect and warn people naming functions something_remove_something

richard.purdie@...

unassigned@...

3.99

3.2

 

10061

Ctrl+C during BB_HASHCHECK_FUNCTION execution does not interrupt processing nicely

richard.purdie@...

unassigned@...

3.99

3.2

 

10096

Allow PREFERRED_VERSION miss to be fatal

richard.purdie@...

unassigned@...

3.99

3.2

 

13905

[QA 3.0.3 RC2] failure in ptest: strace.printstrn-umoven.gen and strace.printpath-umovestr.gen

randy.macleod@...

anuj.mittal@...

3.0.3

3.0.4

 

13906

[QA 3.0.3 RC2] failure in ptest: valgrind.helgrind/tests/tc19_shadowmem

randy.macleod@...

anuj.mittal@...

3.0.3

3.0.4

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

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

 


Enhancements/Bugs closed WW22!

Stephen Jolley
 

All,

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

Who

Count

richard.purdie@...

3

michael@...

3

randy.macleod@...

2

timothy.t.orling@...

1

steve@...

1

Martin.Jansa@...

1

Grand Total

11

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

 


Current high bug count owners for Yocto Project 3.2

Stephen Jolley
 

All,

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

Who

Count

richard.purdie@...

30

david.reyna@...

19

bluelightning@...

17

bruce.ashfield@...

12

akuster808@...

11

kai.kang@...

10

ross@...

9

Qi.Chen@...

9

mark.morton@...

8

JPEWhacker@...

8

randy.macleod@...

7

trevor.gamblin@...

7

changqing.li@...

6

timothy.t.orling@...

6

michael@...

5

pbarker@...

4

rpjday@...

4

mingli.yu@...

4

yi.zhao@...

3

jon.mason@...

3

kexin.hao@...

3

hongxu.jia@...

3

raj.khem@...

3

jaewon@...

2

seebs@...

2

mostthingsweb@...

2

dl9pf@...

2

alejandro@...

2

akuster@...

2

chee.yang.lee@...

2

anuj.mittal@...

2

kergoth@...

2

jpuhlman@...

2

mark.hatle@...

2

ycnakajsph@...

2

alex.kanavin@...

2

liu.ming50@...

1

denis@...

1

limon.anibal@...

1

maxime.roussinbelanger@...

1

zhe.he@...

1

naveen.kumar.saini@...

1

jackie.huang@...

1

jason.wessel@...

1

joe.slater@...

1

sakib.sajal@...

1

matthew.zeng@...

1

kai.ruhnau@...

1

yang.wang@...

1

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

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

 


Reminder: Yocto Project Technical Team Meeting @ Monthly from 8am on the first Tuesday (PDT)

Stephen Jolley
 

All,

 

Just a reminder we will hold the monthly Yocto Project Technical Meeting at 8am PST tomorrow. (6/2) 

 

Yocto Project Technical Team Meeting: We encourage people attending the meeting to logon and announce themselves on the Yocto Project IRC chancel during the meeting (optional):

Yocto IRC: http://webchat.freenode.net/?channels=#yocto

 

Wiki: https://www.yoctoproject.org/public-virtual-meetings/

 

When            Monthly from 8am to 8:30am on the first Tuesday Pacific Time

Where           Zoom Meeting: https://zoom.us/j/990892712

 

We are tracking the minutes at: https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9dDH4/edit?pli=1 Please request access if you want to assist in editing them.  The world should have view access.

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

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

 


Eclipse GDB setup issues; can't determine cause for SIGSEGV

Bryan Evenson
 

All,

I have a AT91SAM9G25 system that has been idle for a couple years (running morty, yocto version 2.2.1) and I am working on updating to the latest Yocto production branch. Before I get there, I'm trying to confirm the old setup and I'm having problems with remote debugging. I know there have been changes since yocto version 2.7 for debugging support, so I want to make sure I can get the old setup to work first prior to changing everything. I'm looking for assistance in tracking down my debug issues.

My stable production image is based off of core-image-minimal, with a few additional packages for our proprietary applications (proprietary applications are written in C). I also have a development image, based off of our production image, with the following additions:

IMAGE_FEATURES += "package-management dev-pkgs eclipse-debug allow-empty-password empty-root-password"

IMAGE_INSTALL += " \
#same additional packages as production image \
#"-dbg" version of proprietary applications \
gdbserver \
"
# Strip python from the image to reduce the image size
PACKAGE_EXCLUDE = "python"

I have the Eclipse Yocto plugin installed and it is setup to use the SDK that I have built based on the development image. I've confirmed that I can start a debug session on one of our proprietary applications. I can set breakpoints and run the debugger. However, the debugger always stops at the first call to uuid_compare with a SIGSEGV. The last line in the call stack states "<symbol is not available> 0x00000000". From my understanding, the stack pointer is getting set to NULL when uuid_compare is getting called. If I stop the debugger and just run the application on the hardware, the application runs without errors. I have confirmed with syslog messages that I do not have the same NULL stack pointer issue when I run the application outside of the debugger.

Any suggestions on where to start looking? I don't see any obvious possible causes and I don't know where to start looking for the problem.

Thanks,
Bryan


Re: QA completion for completed autobuilder build (yocto-2.7.4.rc2)

Armin Kuster
 

On 6/1/20 12:25 AM, Jain, Sangeeta wrote:
Hello all,

This is the full report for yocto-2.7.4.rc2:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
Thank you.

- Armin

======= Summary ========
No high milestone defects.
No new defects are found in this cycle.

Note: Few failures are observed. These are setup issues, not real yocto issue.

Thanks,
Sangeeta


#yocto #raspberrypi SND_BCM2835 doesn't load if vc4-kms-v3d-overlay set #yocto #raspberrypi

Bastien0530 <bastien.gallet-pesenti@...>
 

Hi,
I was struggling for days about playing a simple wav file with aplay on a raspberry 3b+ jack 3.5mm output.

I had built-in snd_bcm2835 and all the required modules and when booting the raspberry, I couldn't play any song :
------------------------------------------------------------------

root@raspberrypi3:~# aplay /usr/share/sounds/alsa/Noise.wav
aplay: main:828: audio open error: No such file or directory
------------------------------------------------------------------

Also, there was only VC4 HDMI playback devices :
------------------------------------------------------------------
root@raspberrypi3:~# aplay -l
**** List of PLAYBACK Hardware Devices ****
card 1: vc4hdmi [vc4-hdmi], device 0: MAI PCM vc4-hdmi-hifi-0 [MAI PCM vc4-hdmi-hifi-0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
------------------------------------------------------------------

And can't find SND_BCM2835 with the command "lsmod | grep snd_bcm2835".

However, I finally figured out that this error was brought by the vc4-kms-v3d-overlay. (Thanks to this topic : https://github.com/raspberrypi/linux/issues/3181).
If I comment the "dtoverlay=vc4-kms-v3d" line in config.txt, then all is fine and I can see the SND_BCM2835 as Alsa playback device :
------------------------------------------------------------------
root@raspberrypi3:~# aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA]
  Subdevices: 7/7
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3
  Subdevice #4: subdevice #4
  Subdevice #5: subdevice #5
  Subdevice #6: subdevice #6
card 0: ALSA [bcm2835 ALSA], device 1: bcm2835 IEC958/HDMI [bcm2835 IEC958/HDMI]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: ALSA [bcm2835 ALSA], device 2: bcm2835 IEC958/HDMI1 [bcm2835 IEC958/HDMI1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
------------------------------------------------------------------

So, I would like to know if there is any recipe or image config to disable vc4-kms-v3d-overlay?

As it is set in the meta-raspberry/conf/machine/include/rpi-base.inc, I cannot make any bbappend recipe to modify this behavior.

What would be the better solution?

Best regards,
Bastien


QA completion for completed autobuilder build (yocto-2.7.4.rc2)

Sangeeta Jain
 

Hello all,

This is the full report for yocto-2.7.4.rc2:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults

======= Summary ========
No high milestone defects.
No new defects are found in this cycle.

Note: Few failures are observed. These are setup issues, not real yocto issue.

Thanks,
Sangeeta


Re: Yocto dunfell - strange error when building npm package without dependence

Jean-Marie Lemetayer
 

Hi Edson,

You're right. I have seen seen this too. I have already created a bug
to track this issue:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=13901

For now, as a workaround, you can just delete the npmsw:// line in
the generated recipe (and the shrinkwrap file).

Best Regards,
Jean-Marie


On Sat, May 30, 2020 at 4:07 PM Edson Seabra
<edson.seabra@zpesystems.com> wrote:

Hi, all

I used recipetool to create the recipe for NPM packages

If the npm package has dependence(s) it works great.

But if not, the error below happens.

I just add a fake dependence in npm-shrinkwrap.json then it works

# cat google-protobuf/npm-shrinkwrap.json
{
"name": "google-protobuf",
"version": "3.3.0",
"lockfileVersion": 1,
"requires": true,
"dependencies": {
"nan": {
"version": "2.14.1",
"resolved": "https://registry.npmjs.org/nan/-/nan-2.14.1.tgz",
"integrity": "sha512-isWHgVjnFjh2x2yuJ/tj3JbwoHu3UC2dX5G/88Cm24yB6YopVgxvBObDY7n5xW6ExmFhJpSEQqFPvq9zaXc8Jw=="
}
}
}

Another way to make it work is to replace the npmsw with file in SRC_URI

======== nan.bb =======
SRC_URI = " \
npm://registry.npmjs.org;package=nan;version=${PV} \
file://npm-shrinkwrap.json;subdir=npm \
"
S = "${WORKDIR}/npm"

inherit npm

======= google-protobuf.bb ==========

SRC_URI = " \
npm://registry.npmjs.org/;package=google-protobuf;version=${PV} \
npmsw://${THISDIR}/${BPN}/npm-shrinkwrap.json \
"

S = "${WORKDIR}/npm"

inherit npm

====== error ======

ERROR: google-protobuf-3.3.0-r0 do_fetch: Failure expanding variable TUNE_FEATURES_tune-core2-64, expression was ${TUNE_FEATURES_tune-x86-64} core2 which triggered exception RecursionError: maximum recursion depth exceeded while calling a Python object
ERROR: Logfile of failure stored in: /home/edson/ng-trunk/nodegrid/tmp/work/core2-64-poky-linux/google-protobuf/3.3.0-r0/temp/log.do_fetch.33980
Log data follows:
| DEBUG: Executing python function extend_recipe_sysroot
| NOTE: Direct dependencies are ['virtual:native:/home/edson/ng-trunk/meta-extended/meta-oe/recipes-oe/node/nodejs_12.14.1.bb:do_populate_sysroot']
| NOTE: Installed into sysroot: ['nodejs-native', 'pkgconfig-native', 'zlib-native', 'brotli-native', 'openssl-native', 'xz-native', 'quilt-native', 'python3-native', 'icu-native', 'c-ares-native', 'libuv-native', 'gnu-config-native', 'libtool-native', 'automake-native', 'autoconf-native', 'ninja-native', 'cmake-native', 'gettext-minimal-native', 'readline-native', 'libffi-native', 'bzip2-native', 'sqlite3-native', 'libtirpc-native', 'util-linux-native', 'gdbm-native', 'libnsl2-native', 'unzip-native', 'texinfo-dummy-native', 'm4-native', 're2c-native', 'expat-native', 'ncurses-native', 'curl-native', 'libpcre2-native', 'libcap-ng-native']
| NOTE: Skipping as already exists in sysroot: []
| DEBUG: sed -e 's:^[^/]*/:/home/edson/ng-trunk/nodegrid/tmp/work/core2-64-poky-linux/google-protobuf/3.3.0-r0/recipe-sysroot-native/:g' /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/nodejs-native/fixmepath /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/pkgconfig-native/fixmepath /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/openssl-native/fixmepath /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/quilt-native/fixmepath /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/python3-native/fixmepath /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/icu-native/fixmepath /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/gnu-config-native/fixmepath /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/libtool-native/fixmepath /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/automake-native/fixmepath /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/autoconf-native/fixmepath /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/ncurses-native/fixmepath /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/curl-native/fixmepath /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/libpcre2-native/fixmepath | xargs sed -i -e 's:FIXMESTAGINGDIRTARGET:/home/edson/ng-trunk/nodegrid/tmp/work/core2-64-poky-linux/google-protobuf/3.3.0-r0/recipe-sysroot:g; s:FIXMESTAGINGDIRHOST:/home/edson/ng-trunk/nodegrid/tmp/work/core2-64-poky-linux/google-protobuf/3.3.0-r0/recipe-sysroot-native:g' -e 's:FIXME_PSEUDO_SYSROOT:/home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/pseudo-native:g' -e 's:FIXME_HOSTTOOLS_DIR:/home/edson/ng-trunk/nodegrid/tmp/hosttools:g' -e 's:FIXME_PKGDATA_DIR:/home/edson/ng-trunk/nodegrid/tmp/pkgdata/genericx86-64:g' -e 's:FIXME_PSEUDO_LOCALSTATEDIR:/home/edson/ng-trunk/nodegrid/tmp/work/core2-64-poky-linux/google-protobuf/3.3.0-r0/pseudo/:g' -e 's:FIXME_LOGFIFO:/home/edson/ng-trunk/nodegrid/tmp/work/core2-64-poky-linux/google-protobuf/3.3.0-r0/temp/fifo.33980:g'
| DEBUG: Python function extend_recipe_sysroot finished
| DEBUG: Executing python function do_fetch
| DEBUG: Executing python function base_do_fetch
| DEBUG: Python function base_do_fetch finished
| DEBUG: Python function do_fetch finished
| ERROR: Failure expanding variable TUNE_FEATURES_tune-core2-64, expression was ${TUNE_FEATURES_tune-x86-64} core2 which triggered exception RecursionError: maximum recursion depth exceeded while calling a Python object
ERROR: Task (/home/edson/ng-trunk/meta-extended/meta-oe/recipes-npm/google-protobuf/google-protobuf_3.3.0.bb:do_fetch) failed with exit code '1'
NOTE: Tasks Summary: Attempted 3501 tasks of which 3500 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
/home/edson/ng-trunk/meta-extended/meta-oe/recipes-npm/google-protobuf/google-protobuf_3.3.0.bb:do_fetch
Summary: There were 2 WARNING messages shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.

Thanks in advance.

Edson Seabra

Principal Engineer

M +1 510 579 0843

E edson.seabra@zpesystems.com


46757 Fremont Blvd., Fremont, CA 94538
zpesystems.com | Request a Nodegrid Demo


Re: Can I build Yocto Arm Image without QEMU?

Alexander Kanavin
 

Qemu is also used to run target binaries during build (when there is a need to generate some data files that can only be produced by running those binaries). If you see a build of qemu-native, it will not end up in the target image.

What is your use case specifically?

Alex


On Sun, 31 May 2020 at 19:52, Олег Гаврильченко via lists.yoctoproject.org <reffum=bk.ru@...> wrote:
May I ask you to clarify, how can I do that? 
I build Yocto image for XILINX ZYNQ7 board and set MACHINE = zybo-zynq7. And then run "bitbake core-image-minimal". QEMU is downloaded, compiled and installed.


Re: Can I build Yocto Arm Image without QEMU?

Олег Гаврильченко <reffum@...>
 

May I ask you to clarify, how can I do that? 
I build Yocto image for XILINX ZYNQ7 board and set MACHINE = zybo-zynq7. And then run "bitbake core-image-minimal". QEMU is downloaded, compiled and installed.


Re: Can I build Yocto Arm Image without QEMU?

Sergei Nikulov
 



вс, 31 мая 2020 г., 14:15 Олег Гаврильченко via lists.yoctoproject.org <reffum=bk.ru@...>:
Hello!
Sorry for my English. My first language is Russian.
I have a question about build yocto image. Can I build image without build any QEMU packages? And how can I do it?

Yes, you can.
Check MACHINE variable in documentation.
You should set it to specific HW you're using.

I do not neet QEMU, I run Linux only in hardware.
Thank you for answers.
 
 


Can I build Yocto Arm Image without QEMU?

reffum@...
 

Hello!
Sorry for my English. My first language is Russian.
I have a question about build yocto image. Can I build image without build any QEMU packages? And how can I do it?
I do not neet QEMU, I run Linux only in hardware.
Thank you for answers.
 
 


Re: python3, pyscard, setuptools ModuleNotFound. Why?

Tim Orling
 



On Sat, May 30, 2020 at 5:14 AM Mauro Ziliani <mauro@...> wrote:
Hi all.

I'd like to include pyscard from pypi in my bsp.

I'm using zeus and python3.


The recipe for pyscard is placed in recipes-devtools/python of my layer

The recipe name s python3-pyscard_1.9.9.bb

This is the recipe


# PYScard
#
#
LICENSE="LGPL-2.1"
LIC_FILES_CHKSUM = "file://LICENSE;md5=d0227c3c90dc0a9eae8b0a64acd8c6e1"

PYPI_PACKAGE="pyscard"

You don't need this as this is the default value. 

inherit pypi setuptools3

SRC_URI[md5sum] = "a8e94032ca8dec22a6c559a7afd41998"
SRC_URI[sha256sum] =
"e6bde541990183858740793806b1c7f4e798670519ae4c96145f35d5d7944c20"


DEPENDS = " \
     swig \
This has to be swig-native. When in doubt, DEPENDS should be the -native version.

After this, you will be missing <winscard.h>, which comes from pcsc-lite recipe in meta-oe, but it didn't readily build even with RDEPENDS_${PN} += "python3-core pcsc-lite" (or pcsc-lite in DEPENDS for that matter).

You'll probably have to figure out how to tell swig where to look for the file.
 
"

Why bitbake tell this error?

Sstate summary: Wanted 5 Found 0 Missed 5 Current 168 (0% match, 97%
complete)
NOTE: Executing Tasks
NOTE: Setscene tasks completed
NOTE: Running task 678 of 773
(/home/mauro/yocto/zeus/sources/meta-custom/recipes-devtools/python/python3-pyscard_1.9.9.bb:do_configure)
NOTE: recipe python3-pyscard-1.9.9-r0: task do_configure: Started
ERROR: python3-pyscard-1.9.9-r0 do_configure: Execution of
'/home/mauro/yocto/zeus/qt10-build/tmp-glibc/work/core2-32-oe-linux/python3-pyscard/1.9.9-r0/temp/run.do_configure.1232'
failed with exit code 1:
Traceback (most recent call last):
   File "setup.py", line 31, in <module>
     from setuptools import setup, Extension
ModuleNotFoundError: No module named 'setuptools'
WARNING: exit code 1 from a shell command.

ERROR: Logfile of failure stored in:
/home/mauro/yocto/zeus/qt10-build/tmp-glibc/work/core2-32-oe-linux/python3-pyscard/1.9.9-r0/temp/log.do_configure.1232
Log data follows:
| DEBUG: Executing shell function do_configure
| Traceback (most recent call last):
|   File "setup.py", line 31, in <module>
|     from setuptools import setup, Extension
| ModuleNotFoundError: No module named 'setuptools'
| WARNING: exit code 1 from a shell command.
| ERROR: Execution of
'/home/mauro/yocto/zeus/qt10-build/tmp-glibc/work/core2-32-oe-linux/python3-pyscard/1.9.9-r0/temp/run.do_configure.1232'
failed with exit code 1:
| Traceback (most recent call last):
|   File "setup.py", line 31, in <module>
|     from setuptools import setup, Extension
| ModuleNotFoundError: No module named 'setuptools'
| WARNING: exit code 1 from a shell command.
|
NOTE: recipe python3-pyscard-1.9.9-r0: task do_configure: Failed
ERROR: Task
(/home/mauro/yocto/zeus/sources/meta-custom/recipes-devtools/python/python3-pyscard_1.9.9.bb:do_configure)
failed with exit code '1'
NOTE: Tasks Summary: Attempted 765 tasks of which 764 didn't need to be
rerun and 1 failed.

Summary: 1 task failed:
/home/mauro/yocto/zeus/sources/meta-custom/recipes-devtools/python/python3-pyscard_1.9.9.bb:do_configure
Summary: There was 1 ERROR message shown, returning a non-zero exit code.


Thanks all

MZ



Yocto dunfell - strange error when building npm package without dependence

Edson Seabra
 

Hi, all

I used recipetool to create the recipe for NPM packages

If the npm package has dependence(s) it works great.

But if not, the error below happens.

I just add a fake dependence in npm-shrinkwrap.json  then it works

# cat google-protobuf/npm-shrinkwrap.json
{
  "name": "google-protobuf",
  "version": "3.3.0",
  "lockfileVersion": 1,
  "requires": true,
  "dependencies": {
    "nan": {
      "version": "2.14.1",
      "resolved": "https://registry.npmjs.org/nan/-/nan-2.14.1.tgz",
      "integrity": "sha512-isWHgVjnFjh2x2yuJ/tj3JbwoHu3UC2dX5G/88Cm24yB6YopVgxvBObDY7n5xW6ExmFhJpSEQqFPvq9zaXc8Jw=="
    }
  }
}

Another way to make it work is to replace the npmsw with file in SRC_URI

======== nan.bb =======
SRC_URI = " \
    npm://registry.npmjs.org;package=nan;version=${PV} \
    file://npm-shrinkwrap.json;subdir=npm \
    "
S = "${WORKDIR}/npm"

inherit npm

======= google-protobuf.bb ==========

 SRC_URI = " \
    npm://registry.npmjs.org/;package=google-protobuf;version=${PV} \
    npmsw://${THISDIR}/${BPN}/npm-shrinkwrap.json \
    "

S = "${WORKDIR}/npm"

inherit npm

====== error ======

ERROR: google-protobuf-3.3.0-r0 do_fetch: Failure expanding variable TUNE_FEATURES_tune-core2-64, expression was ${TUNE_FEATURES_tune-x86-64} core2 which triggered exception RecursionError: maximum recursion depth exceeded while calling a Python object
ERROR: Logfile of failure stored in: /home/edson/ng-trunk/nodegrid/tmp/work/core2-64-poky-linux/google-protobuf/3.3.0-r0/temp/log.do_fetch.33980
Log data follows:
| DEBUG: Executing python function extend_recipe_sysroot
| NOTE: Direct dependencies are ['virtual:native:/home/edson/ng-trunk/meta-extended/meta-oe/recipes-oe/node/nodejs_12.14.1.bb:do_populate_sysroot']
| NOTE: Installed into sysroot: ['nodejs-native', 'pkgconfig-native', 'zlib-native', 'brotli-native', 'openssl-native', 'xz-native', 'quilt-native', 'python3-native', 'icu-native', 'c-ares-native', 'libuv-native', 'gnu-config-native', 'libtool-native', 'automake-native', 'autoconf-native', 'ninja-native', 'cmake-native', 'gettext-minimal-native', 'readline-native', 'libffi-native', 'bzip2-native', 'sqlite3-native', 'libtirpc-native', 'util-linux-native', 'gdbm-native', 'libnsl2-native', 'unzip-native', 'texinfo-dummy-native', 'm4-native', 're2c-native', 'expat-native', 'ncurses-native', 'curl-native', 'libpcre2-native', 'libcap-ng-native']
| NOTE: Skipping as already exists in sysroot: []
| DEBUG: sed -e 's:^[^/]*/:/home/edson/ng-trunk/nodegrid/tmp/work/core2-64-poky-linux/google-protobuf/3.3.0-r0/recipe-sysroot-native/:g' /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/nodejs-native/fixmepath /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/pkgconfig-native/fixmepath /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/openssl-native/fixmepath /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/quilt-native/fixmepath /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/python3-native/fixmepath /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/icu-native/fixmepath /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/gnu-config-native/fixmepath /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/libtool-native/fixmepath /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/automake-native/fixmepath /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/autoconf-native/fixmepath /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/ncurses-native/fixmepath /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/curl-native/fixmepath /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/libpcre2-native/fixmepath | xargs sed -i -e 's:FIXMESTAGINGDIRTARGET:/home/edson/ng-trunk/nodegrid/tmp/work/core2-64-poky-linux/google-protobuf/3.3.0-r0/recipe-sysroot:g; s:FIXMESTAGINGDIRHOST:/home/edson/ng-trunk/nodegrid/tmp/work/core2-64-poky-linux/google-protobuf/3.3.0-r0/recipe-sysroot-native:g' -e 's:FIXME_PSEUDO_SYSROOT:/home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/pseudo-native:g' -e 's:FIXME_HOSTTOOLS_DIR:/home/edson/ng-trunk/nodegrid/tmp/hosttools:g' -e 's:FIXME_PKGDATA_DIR:/home/edson/ng-trunk/nodegrid/tmp/pkgdata/genericx86-64:g' -e 's:FIXME_PSEUDO_LOCALSTATEDIR:/home/edson/ng-trunk/nodegrid/tmp/work/core2-64-poky-linux/google-protobuf/3.3.0-r0/pseudo/:g' -e 's:FIXME_LOGFIFO:/home/edson/ng-trunk/nodegrid/tmp/work/core2-64-poky-linux/google-protobuf/3.3.0-r0/temp/fifo.33980:g'
| DEBUG: Python function extend_recipe_sysroot finished
| DEBUG: Executing python function do_fetch
| DEBUG: Executing python function base_do_fetch
| DEBUG: Python function base_do_fetch finished
| DEBUG: Python function do_fetch finished
| ERROR: Failure expanding variable TUNE_FEATURES_tune-core2-64, expression was ${TUNE_FEATURES_tune-x86-64} core2 which triggered exception RecursionError: maximum recursion depth exceeded while calling a Python object
ERROR: Task (/home/edson/ng-trunk/meta-extended/meta-oe/recipes-npm/google-protobuf/google-protobuf_3.3.0.bb:do_fetch) failed with exit code '1'
NOTE: Tasks Summary: Attempted 3501 tasks of which 3500 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
  /home/edson/ng-trunk/meta-extended/meta-oe/recipes-npm/google-protobuf/google-protobuf_3.3.0.bb:do_fetch
Summary: There were 2 WARNING messages shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.

Thanks in advance.

Edson Seabra

Principal Engineer

M +1 510 579 0843

1506169147061_OutlookEmoji-1505330244060_ZPELogo_Email.png1e6c5898-d340-4c90-8c28-e559c26bc7d1.png
46757 Fremont Blvd., Fremont, CA 94538
zpesystems.com | Request a Nodegrid Demo


python3, pyscard, setuptools ModuleNotFound. Why?

Mauro Ziliani
 

Hi all.

I'd like to include pyscard from pypi in my bsp.

I'm using zeus and python3.


The recipe for pyscard is placed in recipes-devtools/python of my layer

The recipe name s python3-pyscard_1.9.9.bb

This is the recipe


# PYScard
#
#
LICENSE="LGPL-2.1"
LIC_FILES_CHKSUM = "file://LICENSE;md5=d0227c3c90dc0a9eae8b0a64acd8c6e1"

PYPI_PACKAGE="pyscard"


inherit pypi setuptools3

SRC_URI[md5sum] = "a8e94032ca8dec22a6c559a7afd41998"
SRC_URI[sha256sum] = "e6bde541990183858740793806b1c7f4e798670519ae4c96145f35d5d7944c20"


DEPENDS = " \
    swig \
"

Why bitbake tell this error?

Sstate summary: Wanted 5 Found 0 Missed 5 Current 168 (0% match, 97% complete)
NOTE: Executing Tasks
NOTE: Setscene tasks completed
NOTE: Running task 678 of 773 (/home/mauro/yocto/zeus/sources/meta-custom/recipes-devtools/python/python3-pyscard_1.9.9.bb:do_configure)
NOTE: recipe python3-pyscard-1.9.9-r0: task do_configure: Started
ERROR: python3-pyscard-1.9.9-r0 do_configure: Execution of '/home/mauro/yocto/zeus/qt10-build/tmp-glibc/work/core2-32-oe-linux/python3-pyscard/1.9.9-r0/temp/run.do_configure.1232' failed with exit code 1:
Traceback (most recent call last):
  File "setup.py", line 31, in <module>
    from setuptools import setup, Extension
ModuleNotFoundError: No module named 'setuptools'
WARNING: exit code 1 from a shell command.

ERROR: Logfile of failure stored in: /home/mauro/yocto/zeus/qt10-build/tmp-glibc/work/core2-32-oe-linux/python3-pyscard/1.9.9-r0/temp/log.do_configure.1232
Log data follows:
| DEBUG: Executing shell function do_configure
| Traceback (most recent call last):
|   File "setup.py", line 31, in <module>
|     from setuptools import setup, Extension
| ModuleNotFoundError: No module named 'setuptools'
| WARNING: exit code 1 from a shell command.
| ERROR: Execution of '/home/mauro/yocto/zeus/qt10-build/tmp-glibc/work/core2-32-oe-linux/python3-pyscard/1.9.9-r0/temp/run.do_configure.1232' failed with exit code 1:
| Traceback (most recent call last):
|   File "setup.py", line 31, in <module>
|     from setuptools import setup, Extension
| ModuleNotFoundError: No module named 'setuptools'
| WARNING: exit code 1 from a shell command.
|
NOTE: recipe python3-pyscard-1.9.9-r0: task do_configure: Failed
ERROR: Task (/home/mauro/yocto/zeus/sources/meta-custom/recipes-devtools/python/python3-pyscard_1.9.9.bb:do_configure) failed with exit code '1'
NOTE: Tasks Summary: Attempted 765 tasks of which 764 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
/home/mauro/yocto/zeus/sources/meta-custom/recipes-devtools/python/python3-pyscard_1.9.9.bb:do_configure
Summary: There was 1 ERROR message shown, returning a non-zero exit code.


Thanks all

MZ

3581 - 3600 of 53122