**** BEGIN LOGGING AT Fri Dec 27 02:59:57 2019 Dec 27 03:31:38 New news from stackoverflow: Building an embedded linux yocto Dec 27 03:32:02 How can I append to a machine-specific DISTRO_FEATURE from an independent layer Dec 27 03:33:06 Specifically, I want to enable systemd init for machine qemuarm64 if/when I have this layer enabled. Dec 27 03:35:39 Would I just put it into my layer's conf/machine/qemuarm64.conf or would that completely override the poky qemuarm64.conf? Dec 27 03:45:34 penguin359: these are distro features, so either define your own distro layer and add it there, or use some pre-existing distro which already does this e.g. Yoe distro. Or modify your local.conf to add it on top of default reference distro that you might be using like poky, but do not add it to a layer which is not a distro layer Dec 27 08:02:22 New news from stackoverflow: Can't run Yocto image with runqemu sama5d27-som1-ek-sd Dec 27 15:33:38 New news from stackoverflow: polkit-0.113-r0 do_configure: Function failed: do_configure Dec 27 16:14:59 RP: has anyone pursued building a yocto toolchain with more tuning configurations? that is, more than just 32/64/x32 multilibs. if i build an armv5te and armv7te will the same cross gcc be built, or will it be rebuilt even if it doesnt' need to be? I might need to build a single toolchain out of oe that has not just multilib, but mjultiple sysroots for additional tunings including bin, not just libdir changing, so was curious if anyone has looked into Dec 27 16:14:59 that. e.g the sourcery external toolchain gcc automatically appends sysroot suffixes for its various multilb configurations, so more than just libdir changes for it. i'm fin explicitly passing --sysroot= for each, just thinking about sdk construction, meta-environment, and whehter it'll rebuild gcc-cross for every configuration Dec 27 18:25:53 kergoth: we do only build gcc-cross once per arch Dec 27 18:27:24 kergoth: I wanted to push it further but haven't had the time and there wasn't interest really either Dec 27 18:41:54 * kergoth nods Dec 27 18:41:59 okay, thanks, that's helpful Dec 27 20:15:09 hello Dec 27 20:21:49 Hello everyone. I'm in trouble, I'm trying to use temp/humidity sensor bme280 with yocto. I use rocko version of poky and latest driver from bosch sensortec for bme280. With driver they provide example connecting to sensor via i2c. I have compiled it and ran it, i gives -2 code which is device not found. But also I habe used i2cdetect and it gives Dec 27 20:21:50 the correct address of device. Can somebody help me or show me what I am missing? Dec 27 23:00:58 kergoth: in case its not clear, the bit which we vary is libgcc and gcc-runtime which build for each target arch Dec 27 23:01:42 kergoth: we've struggled to get gcc-cross to truly not be target specific though :( Dec 28 02:23:54 RP: yeah, i figured, it was mainly gcc-cross i was wondering about **** ENDING LOGGING AT Sat Dec 28 02:59:57 2019