**** BEGIN LOGGING AT Fri Jan 04 02:59:57 2019 Jan 04 17:10:30 hi, anyone manage to install 32 and 64 bit python using multilib? I am getting ERROR: core-image-minimal-1.0-r0 do_rootfs: Multilib check error: duplicate files /opt/openembedded-core/build/tmp-musl/work/qemuarm64-oe-linux-musl/core-image-minimal/1.0-r0/multilib/lib32/usr/include/python2.7/pyconfig.h /opt/openembedded-core/build/tmp-musl/work/qemuarm64-oe-linux-musl/core-image-minimal/1.0-r0/rootfs/usr/include/python2.7/pyconfig.h is no Jan 04 17:57:10 athoik: I haven't. If you open a defect in https://bugzilla.yoctoproject.org/ Kang Kai will take a look. Jan 04 17:57:24 Why do you want both pythons in your image? Jan 04 17:57:54 err Kai Kang that is. Jan 04 17:58:17 in order to make some 32bit only closed blobs to work Jan 04 17:58:56 athoik: that's what I expected. Does it only happen with musl by chance (I doubt it). Jan 04 18:00:09 vmeson: it happens on eglibc as well Jan 04 18:01:02 athoik: k, I thought so. Let me know the defect ID so Kai can work on it on Monday. Jan 04 18:01:37 s/can work/will take a quick look and maybe work/ ;-) Jan 04 19:08:12 vmeson: tried right now using glibc it works (although it didn't work on older OE morty). So it's only musl related. Opening ticket now. Jan 04 19:09:54 https://bugzilla.yoctoproject.org/show_bug.cgi?id=13122 Jan 04 19:13:39 oe_multilib_header for musl does nothing most probably. Jan 04 19:19:02 thanks for having a look ;) Jan 05 01:24:25 Is there anyone who has done a virtualenv-based python deployment on Yocto (I'm on Xilinx specifically, but I don't think that would affect anything at this level)? Jan 05 01:34:03 My assumption is that I need to get python3 (3.5 in xilinx) as a DEPENDS in the package with the build sysroot including the actual python3 binary and libraries/modules. Then I need to setup something like crossenv or distutilscross to handle doing the actual cross-compilation of modules. Jan 05 01:35:50 Since crossenv, at least, needs the *same* version of python3 for the host and target, I'm assuming I want to extend the bbclasses of python3 with nativesdk so that I can run crossenv with build-python3 generating the matching target-python3. Jan 05 01:37:23 The virtualenv scripts also need access to the target python3 (binary, modules, etc) in order to copy them into the final virtualenv, so I suppose that means I need to add staging to the python3 bbclasses too? Jan 05 01:43:51 But staging alone doesn't seem sufficient to get the target python's bytes into the recipe's sysroot, so I suppose I need to add something to SYSROOT_DIRS, but so far I haven't figured out what would go in there. **** ENDING LOGGING AT Sat Jan 05 02:59:56 2019