**** BEGIN LOGGING AT Thu Jun 25 02:59:57 2020 Jun 25 13:25:18 hi, why cannot I install a 64 SDK on my 64 bit machine? lpapp ~ $ source polatis-eglibc-x86_64-arm-toolchain-9.0.sh Jun 25 13:25:21 bash: source: polatis-eglibc-x86_64-arm-toolchain-9.0.sh: cannot execute binary file Jun 25 13:25:24 lpapp ~ $ uname -a Jun 25 13:25:26 Linux pol-lx-007 5.5.13-arch2-1 #1 SMP PREEMPT Mon, 30 Mar 2020 20:42:41 +0000 x86_64 GNU/Linux Jun 25 13:25:29 lpapp ~ $ Jun 25 13:26:46 lpapp, i'd try running it directly instead of sourcing it Jun 25 13:26:54 dunno if that is equivalent or not Jun 25 13:27:02 lpapp: run it with sh, don't source Jun 25 13:27:21 o_O Jun 25 13:28:47 thanks Jun 25 14:14:03 is EGL supported on QEMU x86-64? I'm sure it is not supported on QEMU ARM Jun 25 14:14:27 yann: I sent the patch to chunkify large messages between the client and server Jun 25 14:15:18 xtron: I frequently use it on i386, so I suspect it also works on x86-64 Jun 25 14:15:55 JPEW, great Jun 25 14:49:17 JPEW: \o/ Jun 25 15:04:37 what opengl is default on qemuarm64? mesa? Jun 25 15:10:26 mcfrisk: Yes, it has to use virtio/virgl Jun 25 15:10:42 mcfrisk: Oh, sorry, though you said x86-64 :) Jun 25 15:20:54 JPEW: no problem. I'm trying to reproduce a build failure from different BSP on qemuarm64.. Jun 25 15:42:47 hmm. trying to support a combined oe sdk as an external toolchain is non-trivial unless the user specifies the environment-setup to use, otherwise i'd have to look for an exact TUNE_PKGARCH match, or parse them all and take a heuristic approach to attempting nto identify a best match for the sysroot to use Jun 25 15:43:10 maybe i could emit TUNE_FEATURES or PACKAGE_ARCHS and look for the closest match Jun 25 16:01:50 I'm starting to get crazy.. Why is do_package trying to write into recipe-sysroot-native? Jun 25 16:02:21 I have a recipe DEPENDS-ing on openssl10-native and do_package also brings openssl-native for some reason into recipe-sysroot-native Jun 25 16:07:22 specifically, extend_recipe_sysroot fails Jun 25 17:13:06 qschulz: Is there a do_package[depends] = "openssl-native" ? Jun 25 17:13:26 no, I have a foo recipe which is litterally DEPENDS = "openssl10-native" only Jun 25 17:13:48 the weird thing is that it happens only every two tries when I run bitbake foo -C package Jun 25 17:14:28 JPEW: ^ Jun 25 17:16:19 JPEW: but maybe another class, I shall find out with a bitbake -e I guess. I'm out for the week-end, I'll pop on the chan again next week Jun 25 17:27:34 hi. has anyone tried to compile luajit from meta-openembedded zeus branch? it fails to build for me. Jun 25 17:32:22 mischief: it needs 32bit toolchain on your host Jun 25 17:32:34 IIRC its documented in readme or recipe Jun 25 17:35:31 o.O Jun 25 17:36:29 the comment says my host needs libc6-dev-i386 installed. it is installed. Jun 25 17:37:56 the compilation failure is https://gist.github.com/nick-owens-eero/9a9dff56fa628dc79c61bfc273d68bbd which seems like some sort of host contamination? Jun 25 17:56:39 mischief: it also says lib32-gcc-libs Jun 25 17:57:10 actually, i can produce the same error by just cloning and trying to build from luajit git. maybe not a yocto problem. Jun 25 17:57:13 which is compiler runtime, however the problem could be in your host install too, if you have 32bit toolchain installed Jun 25 17:57:30 right Jun 25 17:57:50 Is there a meta-lua I'm just not aware of? Jun 25 17:58:21 hmm, not to be confused with metalua, which is different Jun 25 17:58:29 JPEW: that would be neat but im just using luajit from meta-openembedded. Jun 25 17:59:33 khem: my luajit_2.0.5.bb doesn't mention lib32-gcc-libs. Jun 25 18:00:04 Well, I have a few lua modules I need... perhaps time to start a meta-lua... Jun 25 18:07:06 okay... Jun 25 18:07:22 i installed `gcc-multilib` on my host system and now luajit compiles in yocto Jun 25 18:07:40 but gcc-multilib conflicts with the arm cross compilers, so no more arm cross compiler in my host :/ Jun 25 18:07:52 https://bugs.launchpad.net/ubuntu/+source/gcc-defaults/+bug/1300211 Jun 25 18:07:55 silly ubuntu Jun 25 18:14:18 mischief: I usually just use the pre-built toolchain tarballs from ARM to get around that Jun 25 18:27:34 I'm a newbie to Yocto and using a Variscite development kit for the i.MX8MM MINI. I need to enable spidev, but it appears that the device tree is buried deep in the build's tmp directory. Can someone describe how I can modify an existing .dts file and override the default in our own custom layer? We can add layers to the sources directory and Jun 25 18:27:35 keep them under version control, but obviously don't want to version control the build and tmp directories. Can anybody help a struggling newbie? Thanks! Jun 25 18:32:00 surrealist14: You need to create a patch file against the kernel and then include that in your kernel recipe Jun 25 18:33:02 surrealist14: Have a read through https://www.yoctoproject.org/docs/3.1.1/kernel-dev/kernel-dev.html#kernel-dev-common Jun 25 18:33:47 surrealist14: Maybe do a trivial test patch against a qemu target using the linux-yocto kernel to confirm you've got it right, then look at your dts again Jun 25 18:34:22 Will do, thanks for your pointers! Jun 25 20:31:40 does anyone know how to troubleshoot "libGl error failed to load driver virtio_gpu"? occurred when running glxgears and other applications that use opengl. i passed "-vga virtio" to runqemu. Jun 25 21:03:56 mischief: its in README for meta-oe **** ENDING LOGGING AT Fri Jun 26 03:01:39 2020