Ok then next thing you want to check is where the reported stripped file is located and even if it does not work then perhaps look into removing these files if they are not needed

The ones I've added in the INSANE_SKIP ls -lah /home/alex/Projects/yocto/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/node-red-node-serialport/1.0.1-r0/packages-split total 32K drwxr-xr-x

<tagliapietra.alessandro@...> wrote: what package folders do you see under packages-split/ folder in your build area for this recipe ?

Thank you for helping! The package is node-red-node-serialport, it doesn't seem to create child packages for the dependencies, the nodejs deps only reside in the package node-modules folder. The

The prebuilds are for other architectures. so perhaps you can rm them in a do_install_append() or if they are really needed you perhaps would also need INSANE_SKIP_<name of package> = "arch"

Alessandro Tagliapietra <tagliapietra.alessandro@...> escreveu no dia segunda, 11/04/2022 à(s) 17:13: Hi Alessandro, This is because the package that you are building is already compiled and there

This will be valiant effort but my advice is don't go alone if you want to undertake this SOC sdks have lot of nitty gritty issues that will pop up along the way and unless you have someone from SOC

I've created an npm package recipe for node-red-node-serialport using devtool add "npm://registry.npmjs.org;package=node-red-node-serialport;version=1.0.1" which generated this recipe. The problem is

This is my first time working with them so I am learning a lot but never encountered anything like it. Trying to look into what it would require to move to a newer version it appears as if they have

It's a contracting issue. You need to specify in writing that the vendor cannot provide ancient Yocto. Otherwise they won't bother. Alex

Yes I know. Not sure why QC is stuck on Thud. Even newer releases from QC for the target that we are working on is stuck at Thud. Mans Den fre 8 apr. 2022 kl 18:59 skrev Alexander Kanavin

Many layers append BBFILE_COLLECTIONS and therefore have 'core <layer>' During update.py, this means we are likely not handling the collection we expect: WARNING:

ERROR: Variable BB_ENV_EXTRAWHITE has been renamed to BB_ENV_PASSTHROUGH_ADDITIONS ERROR: Variable BB_ENV_EXTRAWHITE from the shell environment has been renamed to BB_ENV_PASSTHROUGH_ADDITIONS ERROR:

Add the newish Inactive-Upstream upstream status. Add 0046_alter_patch_status.py migration. Signed-off-by: Tim Orling <tim.orling@...> layerindex/migrations: update patch

The url pattern was not including the trailing / [YOCTO #14445] Signed-off-by: Tim Orling <tim.orling@...> --- layerindex/urls.py | 2 +- 1 file changed, 1 insertion(+), 1

Various fixes to address errors and warnings when running update.py The following changes since commit 796d2455bb862ed4c71eadfa9fcf4c002752c2f3: templates/*: staticfiles -> static (2022-01-13

The build patches are now included in the upstream, the local binary checkes can be disabled with --disable-ptool-checks, the boostrap doesn't need to be called if the release .tar.gz is

Calling autoreconf outside git repo causes the version number to be null. This patch makes the version number fixed. Since Yocto now uses OpenSSL 3.0, the file packaging need to be

The version number is correctly assigned only when the release .tar.gz is used. Signed-off-by: Petr Gotthard <petr.gotthard@...> --- .../tpm2-abrmd/{tpm2-abrmd_2.4.0.bb =>

This deletes the patches that were unused for a long time, updates the tpm2-tss package and introduces a fix to the version number problem that got introduced with the 3.2.0 version. Signed-off-by: