Hello Khem, >Gesendet: Freitag, 01. November 2019 um 18:23 Uhr >Von: "Khem Raj" <raj.khem@...> >An: JK.Behnke@... >Cc: "Yocto Project" <yocto@...> >Betreff: Re: [yocto] poky thud: qtscript fails to

All, The triage team is starting to try andcollect up and classify bugs which a newcomer to the project would be able towork on in a way which means people can find them. They're being listed on

Andrei and/or Khem, Could you advise an approach that allows to use the ARM errata switches for the aarch64 portion of the build for the target, but which will NOT specify the ARM errata switches for

Helllo, I am looking for some help with meta-java, specifically upgrading to zeus branch and also upgrading openjdk to a more recent release in order to address CVEs. Wondering if there is anyone

This doesn’t work. If I wish to keep the 32-bit app support in my build, I’ll need to devise a way to make sure those ARM errata flags are only applied to the aarch64 portion of the compile/link

To conitnue to be able to use the 32-bit app support, perhaps I must do this: DEFAULTTUNE_virtclass-multilib-lib32 = “armv7a -mno-fix-cortex-a53-843419 -mno-fix-cortex-a53-835769” I’ll give it a

The errata switches are only valid for aarch64, not for armv7a. There is likely some kind of "invalid option" earlier in your build. cu Adrian -- "Is there not promise of rain?" Ling Tan

I am closer to understanding why I experience an error when building with the ARM errata switches. I believe it is related to 32-bit app support in my poky Linux 64-bit build (I add this to support

Dear yocto developer, The below disscussed about azure devops clone issue including test result with Microsoft support team member. We wonder know how Bitbake access repository through SSH. Does it

It is fixed in some r0p4 implementations, indicated in REVIDR[8]. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of

Rpi3 is one of many cortex a53 implementations

As far as I know that is the latest revision. Do you mean that newer revision might come up with this fixed? -- Andrei Gherzan gpg: rsa4096/D4D94F67AD0E9640 | t: @agherzan

Up to r0b4 only so maybe not all a53 implementations are impacted

I was thinking about this. The erratum seems to show that this applies to all revisions of a53. So it sounds like we should add it in `tune-cortexa53.inc`. -- Andrei Gherzan

Hi all. I have a weird issue with the kernel modules not being installed in the image and also not packaged. I see the packages for individual "kernel-module-*.ipk" modules but the

Okay, that's great! Thanks for the information! -- Tanu

Entirely worth writing a proper class and pushing a layer somewhere. No, it's just a way of making shell tasks pause for inspecting the state of the build tree during a task. I was debugging some

Cool, thanks. This one seems to be the most up to date from the python debugger wrappers: https://github.com/ionelmc/python-remote-pdb The `shell_wait()` in your bbclass is related to the pdb()

FWIW, I've done something similar using bare pdb. https://github.com/rossburton/meta-ross/blob/master/classes/pdb.bbclass Just call pdb() from Python context. Not as neat as epdb though. Ross

Hey, there was a question today about options for debugging python scripts in yocto. I've patched up this PoC for remote debugging. If someone finds it useful (it should be copy-pastable), feel free