Hello,
We observe an issue with qemu (runqemu) when we use our shared sstate-cache.
If we build the sstate-cache on a debian x86_64, and after we use it on an
ubuntu x86_64, qemu looks for several not-found libs.
We have reproduced this problem on two different pc with ubuntu. We don't have
libnfs for example
‐‐‐ Original Message ‐‐‐
On Wednesday 27 May 2020 14:43, Alexander Kanavin
wrote:
> Can you please provide the lib names which are problematic?
>
> Alex
>
> On Wed, 27 May 2020 at 14:29, vygu via lists.openembedded.org
> wrote:
>
>>
Hello,
Since the zeus serie (also with dunfell), we observe an issue with runqemu when
we share the sstate-cache thanks to a mirror between different linux
distribution supported by yocto.
If we build a sstate-cache on a debian 10 x86_64 buildfarm, and after that we
use it on an ubuntu 18.04
b308f4000)
libpcre.so.1 => /usr/lib/libpcre.so.1 (0x00006b9b3002a000)
‐‐‐ Original Message ‐‐‐
On Wednesday 27 May 2020 14:43, Alexander Kanavin
wrote:
> Can you please provide the lib names which are problematic?
>
> Alex
>
> On Wed, 27 May 2020 at 14:29, vygu v
Andre McCurdy wrote:
> On Wed, May 27, 2020 at 5:29 AM vygu via lists.openembedded.org
> vygu=protonmail...@lists.openembedded.org wrote:
>
> > Hello,
> > Since the zeus serie (also with dunfell), we observe an issue with runqemu
> > when we share the sstate-cache thanks to a m
-1.so.0 => /usr/lib/libpixman-1.so.0 (0x6b9b3070e000)
>> libutil.so.1 => /usr/lib/libutil.so.1 (0x6b9b30709000)
>> libfdt.so.1 => /usr/lib/libfdt.so.1 (0x00006b9b306ff000)
>> libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x6b9b305d4000)
>
Hello,
We observe this following error about cve_check after a populate_sdk:
ERROR: Execution of event handler 'cve_save_summary_handler' failed
Traceback (most recent call last):
File "/home/user/poky/meta/classes/cve-check.bbclass", line 65, in
cve_save_summary_handler(e=):
>
