After some investigation on the debian buildfarm, we can see in the
build/tmp/work/x86_64-linux/qemu-system-native/4.2.0-r0/temp/log.do_configure
"libnfs support yes". If we comment in poky/meta/recipes-devtools/qemu/qemu.inc
all the prepend do_configure_prepend_class-native(), we obtain "libnfs support
no". The function do_configure_prepend_class-native, as written in
commentaries, is to find sdl. But we see now it adds more than just the sdl
support. Is it expected?
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Wednesday 27 May 2020 16:32, Alexander Kanavin <[email protected]>
wrote:
> Runqemu is running qemu binaries from a different location (that of
> qemu-helper-native sysroot), and on my machine, qemu in that location
> resolves libraries correctly. Can you try the same please?
>
> ak@linux-f9zs:~/development/poky> ldd
> build-st/tmp/work/x86_64-linux/qemu-helper-native/1.0-r1/recipe-sysroot-native/usr/bin/qemu-system-aarch64.real
> linux-vdso.so.1 (0x00007ffcf73d9000)
> libvirglrenderer.so.1 =>
> /home/ak/development/poky/build-st/tmp/work/x86_64-linux/qemu-helper-native/1.0-r1/recipe-sysroot-native/usr/bin/../lib/libvirglrenderer.so.1
> (0x00007fdb2efce000)
> libepoxy.so.0 =>
> /home/ak/development/poky/build-st/tmp/work/x86_64-linux/qemu-helper-native/1.0-r1/recipe-sysroot-native/usr/bin/../lib/libepoxy.so.0
> (0x00007fdb2ee9a000)
> libgbm.so.1 =>
> /home/ak/development/poky/build-st/tmp/work/x86_64-linux/qemu-helper-native/1.0-r1/recipe-sysroot-native/usr/bin/../lib/libgbm.so.1
> (0x00007fdb2ee89000)
> libasound.so.2 =>
> /home/ak/development/poky/build-st/tmp/work/x86_64-linux/qemu-helper-native/1.0-r1/recipe-sysroot-native/usr/bin/../lib/libasound.so.2
> (0x00007fdb2ed93000)
> libSDL2-2.0.so.0 =>
> /home/ak/development/poky/build-st/tmp/work/x86_64-linux/qemu-helper-native/1.0-r1/recipe-sysroot-native/usr/bin/../lib/libSDL2-2.0.so.0
> (0x00007fdb2ec5f000)
> libX11.so.6 =>
> /home/ak/development/poky/build-st/tmp/work/x86_64-linux/qemu-helper-native/1.0-r1/recipe-sysroot-native/usr/bin/../lib/libX11.so.6
> (0x00007fdb2eb1f000)
> libgtk-3.so.0 =>
> /home/ak/development/poky/build-st/tmp/work/x86_64-linux/qemu-helper-native/1.0-r1/recipe-sysroot-native/usr/bin/../lib/libgtk-3.so.0
> (0x00007fdb2e440000)
> libgdk-3.so.0 =>
> /home/ak/development/poky/build-st/tmp/work/x86_64-linux/qemu-helper-native/1.0-r1/recipe-sysroot-native/usr/bin/../lib/libgdk-3.so.0
> (0x00007fdb2e38c000)
>
> (etc, there is a lot of similar lines)
>
> Alex
>
> On Wed, 27 May 2020 at 15:59, vygu <[email protected]> wrote:
>
>> For example:
>>
>> with the sstate-cache build on a debian, we have:
>>
>> $ ldd ../build/
>> tmp/work/x86_64-linux/qemu-system-native/4.1.0-r0/sysroot-destdir/home/user/yocto/build/tmp/work/x86_64-linux/qemu-system-native/4.1.0-r0/recipe-sysroot-native/usr/bin/qemu-system-aarch64
>> linux-vdso.so.1 (0x00007ffe7dbc0000)
>> libseccomp.so.2 => /lib/x86_64-linux-gnu/libseccomp.so.2
>> (0x00007f533d18a000)
>> libbrlapi.so.0.6 => /lib/x86_64-linux-gnu/libbrlapi.so.0.6
>> (0x00007f533d17d000)
>> libvdeplug.so.2 => /lib/libvdeplug.so.2 (0x00007f533d175000)
>> libasound.so.2 => /lib/x86_64-linux-gnu/libasound.so.2
>> (0x00007f533d074000)
>> libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f533ce56000)
>> libnfs.so.8 => /lib/x86_64-linux-gnu/libnfs.so.8 (0x00007f533cc1d000)
>> librbd.so.1 => /lib/x86_64-linux-gnu/librbd.so.1 (0x00007f533c8dc000)
>> librados.so.2 => /lib/x86_64-linux-gnu/librados.so.2
>> (0x00007f533c76c000)
>> libacl.so.1 => /lib/x86_64-linux-gnu/libacl.so.1 (0x00007f533c761000)
>> libgfapi.so.0 => /lib/x86_64-linux-gnu/libgfapi.so.0
>> (0x00007f533c732000)
>> libglusterfs.so.0 => /lib/x86_64-linux-gnu/libglusterfs.so.0
>> (0x00007f533c624000)
>> libgfrpc.so.0 => /lib/x86_64-linux-gnu/libgfrpc.so.0
>> (0x00007f533c604000)
>> libgfxdr.so.0 => /lib/x86_64-linux-gnu/libgfxdr.so.0
>> (0x00007f533c5e4000)
>> libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x00007f533c5db000)
>> libpixman-1.so.0 => /lib/x86_64-linux-gnu/libpixman-1.so.0
>> (0x00007f533c535000)
>> libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x00007f533c530000)
>> libfdt.so.1 => /lib/x86_64-linux-gnu/libfdt.so.1 (0x00007f533c524000)
>> libgthread-2.0.so.0 => /lib/x86_64-linux-gnu/libgthread-2.0.so.0
>> (0x00007f533c51d000)
>> libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0
>> (0x00007f533c3fe000)
>> librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f533c3f4000)
>> libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6
>> (0x00007f533c270000)
>> libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f533c0ed000)
>> libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
>> (0x00007f533c0d3000)
>> libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
>> (0x00007f533c0b0000)
>> libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f533beef000)
>> libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f533beea000)
>>
>> /home/user/yocto/build/tmp/sysroots-uninative/x86_64-linux/lib/ld-linux-x86-64.so.2
>> => /lib64/ld-linux-x86-64.so.2 (0x00007f533e447000)
>> libceph-common.so.0 =>
>> /usr/lib/x86_64-linux-gnu/ceph/libceph-common.so.0 (0x00007f5333422000)
>> libboost_system.so.1.67.0 =>
>> /lib/x86_64-linux-gnu/libboost_system.so.1.67.0 (0x00007f533341b000)
>> libboost_thread.so.1.67.0 =>
>> /lib/x86_64-linux-gnu/libboost_thread.so.1.67.0 (0x00007f53333ed000)
>> libattr.so.1 => /lib/x86_64-linux-gnu/libattr.so.1 (0x00007f53333e5000)
>> libtirpc.so.3 => /lib/x86_64-linux-gnu/libtirpc.so.3
>> (0x00007f53333b1000)
>> libcrypto.so.1.1 => /lib/x86_64-linux-gnu/libcrypto.so.1.1
>> (0x00007f53330c8000)
>> libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007f5333054000)
>> libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2
>> (0x00007f5333038000)
>> libboost_regex.so.1.67.0 =>
>> /lib/x86_64-linux-gnu/libboost_regex.so.1.67.0 (0x00007f5332f23000)
>> libboost_iostreams.so.1.67.0 =>
>> /lib/x86_64-linux-gnu/libboost_iostreams.so.1.67.0 (0x00007f5332f05000)
>> libblkid.so.1 => /lib/x86_64-linux-gnu/libblkid.so.1
>> (0x00007f5332eb0000)
>> libsmime3.so => /lib/x86_64-linux-gnu/libsmime3.so (0x00007f5332e81000)
>> libnss3.so => /lib/x86_64-linux-gnu/libnss3.so (0x00007f5332d33000)
>> libnspr4.so => /lib/x86_64-linux-gnu/libnspr4.so (0x00007f5332cf0000)
>> libibverbs.so.1 => /lib/x86_64-linux-gnu/libibverbs.so.1
>> (0x00007f5332cd5000)
>> libboost_atomic.so.1.67.0 =>
>> /lib/x86_64-linux-gnu/libboost_atomic.so.1.67.0 (0x00007f5332cd0000)
>> libgssapi_krb5.so.2 => /lib/x86_64-linux-gnu/libgssapi_krb5.so.2
>> (0x00007f5332c83000)
>> libkrb5.so.3 => /lib/x86_64-linux-gnu/libkrb5.so.3 (0x00007f5332ba3000)
>> libk5crypto.so.3 => /lib/x86_64-linux-gnu/libk5crypto.so.3
>> (0x00007f5332b6d000)
>> libcom_err.so.2 => /lib/x86_64-linux-gnu/libcom_err.so.2
>> (0x00007f5332b67000)
>> libicudata.so.63 => /lib/x86_64-linux-gnu/libicudata.so.63
>> (0x00007f5331177000)
>> libicui18n.so.63 => /lib/x86_64-linux-gnu/libicui18n.so.63
>> (0x00007f5330e9c000)
>> libicuuc.so.63 => /lib/x86_64-linux-gnu/libicuuc.so.63
>> (0x00007f5330ccd000)
>> libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0
>> (0x00007f5330cb8000)
>> libnssutil3.so => /lib/x86_64-linux-gnu/libnssutil3.so
>> (0x00007f5330c86000)
>> libplc4.so => /lib/x86_64-linux-gnu/libplc4.so (0x00007f5330c7f000)
>> libplds4.so => /lib/x86_64-linux-gnu/libplds4.so (0x00007f5330c7a000)
>> libnl-route-3.so.200 => /lib/x86_64-linux-gnu/libnl-route-3.so.200
>> (0x00007f5330a01000)
>> libnl-3.so.200 => /lib/x86_64-linux-gnu/libnl-3.so.200
>> (0x00007f53307e0000)
>> libkrb5support.so.0 => /lib/x86_64-linux-gnu/libkrb5support.so.0
>> (0x00007f53307cf000)
>> libkeyutils.so.1 => /lib/x86_64-linux-gnu/libkeyutils.so.1
>> (0x00007f53307c8000)
>>
>> without the sstate-cache, on an ubuntu 16.04, we have:
>>
>> ldd
>> ../build/tmp/work/x86_64-linux/qemu-system-native/4.1.0-r0/sysroot-destdir/home/user/yocto/build/tmp/work/x86_64-linux/qemu-system-native/4.1.0-r0/recipe-sysroot-native/usr/bin/qemu-system-aarch64
>> linux-vdso.so.1 (0x00006b9b308f2000)
>> libasound.so.2 => /usr/lib/libasound.so.2 (0x00006b9b307d0000)
>> libz.so.1 => /usr/lib/libz.so.1 (0x00006b9b307b6000)
>> libpixman-1.so.0 => /usr/lib/libpixman-1.so.0 (0x00006b9b3070e000)
>> libutil.so.1 => /usr/lib/libutil.so.1 (0x00006b9b30709000)
>> libfdt.so.1 => /usr/lib/libfdt.so.1 (0x00006b9b306ff000)
>> libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x00006b9b305d4000)
>> librt.so.1 => /usr/lib/librt.so.1 (0x00006b9b305c9000)
>> libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00006b9b303ec000)
>> libm.so.6 => /usr/lib/libm.so.6 (0x00006b9b302a7000)
>> libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x00006b9b3028d000)
>> libpthread.so.0 => /usr/lib/libpthread.so.0 (0x00006b9b3026b000)
>> libc.so.6 => /usr/lib/libc.so.6 (0x00006b9b300a2000)
>> libdl.so.2 => /usr/lib/libdl.so.2 (0x00006b9b3009c000)
>>
>> /home/user/yocto/buildv1.8/tmp/sysroots-uninative/x86_64-linux/lib/ld-linux-x86-64.so.2
>> => /usr/lib64/ld-linux-x86-64.so.2 (0x00006b9b308f4000)
>> libpcre.so.1 => /usr/lib/libpcre.so.1 (0x00006b9b3002a000)
>>
>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>> On Wednesday 27 May 2020 14:43, Alexander Kanavin <[email protected]>
>> 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
>>> <[email protected]> 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 x86_64, runqemu don't find several libs.
>>>> We have reproduced this problem on two different pc with ubuntu 18.04 and
>>>> 16.04.
>>>>
>>>> We don't have this problem, if we use the shared sstate-cache on another
>>>> debian.
>>>>
>>>> In all cases, a ldd on the qemu binary shows us the use of local/host
>>>> libs, not the yocto libs.
>>>>
>>>> Is it an expected behavior? or not?
>>>> Runqemu's libs have to come from the linux distribution or from the yocto
>>>> build env?
>>>>
>>>> Cordially,
>>>>
>>>> vygu
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#138917):
https://lists.openembedded.org/g/openembedded-core/message/138917
Mute This Topic: https://lists.openembedded.org/mt/74498490/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
