* armpit needs to be blacklisted from working RP, i did find a couple of people that expressed support about building windows apps using yocto, on the mailing list: Or is it not so wide spread across the industry?Īrmpit: we could just blacklist this test on fc30 for warrior Is it worth learning yocto to become a better embedded engineer? * armpit thinks the host is missing something. If the host can't do that, then there is something wrong Using master and I run "runqemu qemux86-64" it complains of Failed to run qemu: Could not initialize SDL(x11 not available) - exiting I was trying that and that when I saw the lsbSDL2 message.įc30 only has v1 installed but I think we should be using oe native versionĪrmpit: sounds like its missing a dependencyĪrmpit: Note that those tests do change qemu-native's PACKAGECONFIG I have seen thos /dev/ message on warrior be it does no not have the headless testĪrmpit: Did you find 4.1.0 worked but 3.1.0 doesn t? 11:49:58,104 - oe-selftest - INFO - /dev/dri directory does not exist no render nodes available on this machine. skipped '/dev/dri directory does not exist no render nodes available on this machine.' 11:49:58,102 - oe-selftest - INFO - test_testimage_virgl_headless (runtime_test.TestImage) 11:43:50,710 - oe-selftest - INFO - test_testimage_virgl_gtk (runtime_test.TestImage) tmp/work/x86_64-linux/qemu-system-native/4.1.0-r0/sysroot-destdir/home/pokybuild/yocto-worker/oe-selftest-fedora/build/build/tmp/work/x86_64-linux/qemu-system-native/4.1.0-r0/recipe-sysroot-native/usr/bin/qemu-system-i386: error while loading shared libraries: libSDL2-2.0.so.0: cannot open shared object file: No such file or directory tmp/work/x86_64-linux/qemu-system-native/4.1.0-r0/sysroot-destdir/home/pokybuild/yocto-worker/oe-selftest-fedora/build/build/tmp/work/x86_64-linux/qemu-system-native/4.1.0-r0/recipe-sysroot-native/usr/bin/qemu-system-i386 -version Hmmm, way is zeus and master passing qemu tests * armpit back to troubleshooting warrior failure (also I am not sure that the 3g packages pull in a cairo dependency but I didn't need it anyway. I had to work backwards from the graph filesĪdding `DISTRO_FEATURES_remove = " 3g bluetooth nfc "` obviated the dependency on cairo you'll get an error with a dependency set of how/why cairo was built PNBLACKLIST = "don't build this" (add that to your nf * wbn is reading about the `-g` argument to bitbake. So my build is failing at recipes-graphics/cairoīut i'm not sure why it's even being builtĬan i check the dependency chain between two targets with bitbake? « Friday, Index Sunday, » *** BobPungartnik has quit IRC
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |