This issue is understood, documented and resolved so I closed the defect with a short explanation. ../Randy

Sundeep and/or Naveen please take a look. Peter, Please open a Yocto bug and document the steps to reproduce the error. ../Randy

As a first pass, collect all the tmp/buildstats logs using 'cp -a', to enable review and graphing of all builds. The goal is to understand the trends in the /proc/pressure/{cpu|io} data that is now ga

Done (for unassigned and a few for other people ) Done: moved issues that seems less urgent to M3 to reduce "paperwork". ../Randy

Trevor was looking into this as well so I've CCed him. ../Randy

#yocto

Done. ../Randy

Done. I closed 3 prelink issues as obsolete: 1.Prelink: doesn't work on ppc64 https://bugzilla.yoctoproject.org/show_bug.cgi?id=1331 2. Investigate if -mtls-dialect=gnu2 support within the prelinker b

Add Denis since he may have missed Sundeep's email. The 4096 comes from PATH_MAX: linux/limits.h. #define PATH_MAX 4096 /* # chars in a path name including nul */ but that does seem a tad on the long

Hi, If you can come up with a reasonably simple reproducer and it fails on a supported branch: https://wiki.yoctoproject.org/wiki/Releases then we'd appreciate if if you could report the bug in the YP

Hi Paul, Try adding: VIRTUAL-RUNTIME_base-utils-syslog = "syslog" as shown on: https://git.yoctoproject.org/poky/tree/meta-poky/conf/local.conf.sample.extended#n371 I would expect that since you have

That is, can you not package each moduleA as moduleA and moduleA-private using Yocto's packaging mechanism with the *3.h files being in the private packages? I don't work with the SDK very much so I c

#sdk

Hi Praveen, I'm not aware of anyone else doing that. For libraries/recipes, you could just omit certain packages from the eSDK but you don't seem to want to do that. What is your goal in filtering hea

#sdk

Jon, I've looked over all the changes and agree with Ross on his one suggestion and that the rest of the changes are fine. The new terms are equally or in some cases more clear so hopefully that will

Hi, Yes. Likely you just need to do: $ MACHINE=qemux86-64 bitbake your-image with the right configuration and then run it in docker. See below. There are at least three options depending on what your

Oops, I just noticed that this was posted to the linux-yocto not the yocto list. I'm BCCing linux-yocto and redirecting the discussion to the yocto list where it's more appropriate. See: https://www.y

Thanks Stephan. Hongxu, did you miss this? ../Randy

I think it's an oversight that doesn't affect many people. The rm_work code for WORKDIR is: http://cgit.openembedded.org/openembedded-core/tree/meta/classes/rm_work.bbclass#n97 cd ${WORKDIR} for dir i

Hi, Welcome to the Yocto community. It's hard to say without more information. Can you tell us what layers and versions from the Yocto Project you are using? Can you share or describe the local change

YP AB Intermittent failures meeting =================================== https://windriver.zoom.us/j/3696693975 Attendees: Richard, Trevor, Randy, Saul, AlexB Summary: ======== ------------------------

Hi Luca, I think you either need the right key/string: $ oe-pkgdata-util find-path /bin/ls.coreutils coreutils: /bin/ls.coreutils or to use a wildcard and quotes: $ oe-pkgdata-util find-path "/bin/ls*

#yocto