**** BEGIN LOGGING AT Wed Jan 03 03:00:01 2018 Jan 03 08:54:53 New news from stackoverflow: Read a specific memory address via /dev/mem from the command line Jan 03 10:05:44 Dear All, Jan 03 10:06:13 I do need to add #include to my yocto distro (one of my programs requires it) Jan 03 10:06:40 I've tried to add util-linux recipe, but hexdump.h seems to be only used locally there Jan 03 10:07:04 also I've manually installed hexdump.h into ${D}/includedir/ Jan 03 10:07:09 and this file is visible there Jan 03 10:07:27 unfortunately, it requires some other files "c.h" Jan 03 10:07:43 I'm wondering if I doing the stuff with correct approach Jan 03 10:08:04 has anybody seen hexdump.h to be self contained? E.g. a part of a compiler bundle ? Jan 03 11:00:41 lukma: do you actually need the version from util-linux? that one's for the hexdump(1) utility, and I don't think it's ever been expected to be shipped publicly Jan 03 11:02:32 Has someone seen this eror 'Exception: ValueError: invalid literal for int() with base 10: 'resize'' while builidng an image? I have no clue what could be causing it Jan 03 11:03:18 (complete error: https://pastebin.com/cXvswvh8) Jan 03 11:12:59 At this line: Jan 03 11:12:59 numbers.add(int(f.split("-")[0])) Jan 03 11:12:59 "f.split("-")[0]" returns the string "resize" while an integer is expected. No idea about the root cause tho :D Jan 03 11:15:30 It was caused by a file which contained a '-' in its file name... Jan 03 11:15:47 aparently the way Yocto parses the version of different packages during some phase at rootfs creation is just splitting by '-'.... Jan 03 11:16:12 Maybe it is illegal to have a file with a '-' in its name, I didn't read about that. Anyway, fixed by just replacing it to '_' Jan 03 11:33:28 Any idea which package can provide 'truncate' to the host? Jan 03 11:44:20 ttllkk: it's part of coreutils here Jan 03 11:49:21 rakuco: the hexdump.h looks like some standard one..... Jan 03 11:55:30 New news from stackoverflow: how to use yocto sdcard image Jan 03 12:16:47 rakuco: thanks, adding coreutils-native as a dependency fixed it Jan 03 12:25:36 New news from stackoverflow: Error when I run bitbake Jan 03 12:25:50 I am getting this warnings '[log_check] warning: %post(hostapd-2.6-r0.0.cortexa9hf_neon) scriptlet failed, exit status 1' how can I get more information about which error it is? Jan 03 12:40:32 hello, in Yocto project Rocko release systemd recipe has Polkit option enabled by default... as I am not very familiar with Polkit, I have doubts whether it should be used on a handheld embedded device at all since it is not really a desktop distribution usecase Jan 03 12:40:49 I cannot specify the `SRCREV` to use via `PREFERRED_VERSION_` in my `local.conf`, right? May I override the `SRCREV` of `myPn` via `SRCREV_myPn = c0ffee`? Or do i need to add some python to do that in my `myPn_git.bb` recipe? Jan 03 12:41:07 I am aware Linux has a lot of security mechanisms, but am unsure which ones should be preferred for embedded usecases Jan 03 12:43:44 eduardas_m: polkit is used to control automated transition from unprivileged to privileged for certain actions Jan 03 12:46:47 Son_Goku: yes, but why not just use sudo? Jan 03 12:47:03 sudo is useful for separation across processes Jan 03 12:47:15 polkit is useful for controlling actions within the same process Jan 03 12:47:44 but yes, you could use sudo for most things Jan 03 12:47:53 and polkit in fact uses sudo for quite a bit of stuff Jan 03 12:47:54 Son_Goku: so can Polkit limit a processes actions even if it is run as root? Jan 03 12:47:59 well, no Jan 03 12:48:07 it limits actions of processes that aren't root Jan 03 12:48:19 to limit things running as root, you'll need a MAC like SELinux Jan 03 12:49:57 Son_Goku: I've actually got this strange situation where I have transitioned my BSP from pyro to rocko and my call to systemd d-bus interface no longer works from a Qt GUI running as root Jan 03 12:50:16 ah, polkit authorization Jan 03 12:50:23 you don't have a polkit agent to pick that up, I bet Jan 03 12:50:34 alternatively, you can just set polkit to pass through everything Jan 03 12:53:06 Son_Goku: I can see that /usr/share/polkit-1/actions/org.freedesktop.systemd1.policy has a section with action id="org.freedesktop.systemd1.manage-unit-files" Jan 03 12:53:39 yeah, I forget exactly how to, but you can just tell polkit to always allow everything Jan 03 12:55:46 Son_Goku: thank you for the tip, but do people actually use Polkit for embedded Linux system as a standard practice or is some other security model preferrable? Jan 03 12:56:06 well, it depends on the type of embedded system Jan 03 12:56:32 in your case, since you're using Qt things and whatnot, I have seen it used, mainly to prevent accidental allowance of more actions than should be allowed Jan 03 12:56:49 Son_Goku: I will not ask the end-user for any passwords and there will be no administrator Jan 03 12:57:02 well then it's sort of pointless Jan 03 12:57:25 the main case where I see these is where the systems are centrally managed Jan 03 12:57:32 Son_Goku: device is still supposed to be cloud-connected though Jan 03 12:57:35 and auth requests like that have a central policy applied to them' Jan 03 13:00:02 Son_Goku: yeah, I will not have any central management like that... so do you think it would be valid to remove Polkit altogether just to avoid confusion during development and make the system simpler? Jan 03 13:00:19 probably, yes Jan 03 13:01:49 Son_Goku: thank you for the information provided. I find it really useful Jan 03 13:03:24 hi guys, I created a python module using setup.py. When I install it in my machine it creates a compacted .egg that works, but in my recipe I used distutils that creates .egg path that not work Jan 03 13:03:56 someone knows how to build compacted .egg via recipe? Jan 03 13:06:33 An egg? A binary release? Otherwise, I'd look into pip for installing python modules, but afaik pip does not support binary eggs Jan 03 13:07:19 Ah, you have a setup.py. Then pip can be used Jan 03 13:08:51 See here for recipes in how to use pip http://git.openembedded.org/meta-openembedded/tree/meta-python/recipes-devtools/python Jan 03 13:10:18 s/pip/setuptools/ it seems Jan 03 13:25:25 thank you very mutch sveinse, I will see it! Jan 03 14:56:15 paulbarker: your FOSDEM deck lists _Yocto Project_ reference platforms *except* Intel, any reason for that? Jan 03 14:57:45 joshuagl: What is the reference Intel board these days? I just see genericx86 and genericx86-64 in the meta-yocto-bsp machines Jan 03 14:59:19 paulbarker: README.hardware lists the platforms Intel tests on. Minnowboard MAX seems a reasonable one to list, but the BSP supports most IA platforms AFAIK Jan 03 14:59:32 Ah that's the file I should have been looking at Jan 03 15:00:05 :-) Jan 03 15:00:11 easily and often missed Jan 03 15:01:15 I'll go with Minnowboard MAX Jan 03 15:04:42 I thought MAX had been dropped for Turbot now Jan 03 15:16:37 Son_Goku: even after Polkit option removal from systemd build, my Qt app d-bus integration still does not work... any ideas what I might be doing wrong? Jan 03 15:16:53 check the journal and see what's going on? Jan 03 15:17:27 Son_Goku: busctl monitor does not show anything... will check journal Jan 03 15:18:41 Son_Goku: journalctl does not seem to log anything d-bus related Jan 03 15:19:10 CTtpollard: Last I checked the Turbot was still made of unobtainium Jan 03 15:19:45 Though that was a long while back Jan 03 15:20:11 paulbarker: still is, afaik Jan 03 16:26:27 New news from stackoverflow: During SDK build: environment-setup.d/ conflicts between attempted installs Jan 03 20:08:24 * armpit hmm, thought we where going to remove old branches in the poky-contrib??? Jan 03 21:06:42 Huh, I just hit a similar issue to that stack overflow post on do_populate_sdk with meta-toolchain-qt5. https://pastebin.com/983Zwk9C Jan 03 21:58:48 if I have my own cross compilers (i.e., not openembedded), can I still use yocto for building my project? (should I?) Jan 03 21:59:59 yes, you can use an external toolchain to build. precisely how to do so can vary, depending on the external toolchain in question. the CodeBench/Mentor toolchain is already supported in the meta-sourcery layer, using the meta-external-toolchain layer to do most of the work. you can try using external-toolchain directly, or use meta-sourcery as an example / starting point for adding support for yours Jan 03 22:00:43 and can you have multiple external toolchains for a single project? (say, some components use a proprietary compiler, and some use openembedded's cross-compilers?) Jan 03 22:00:57 doable, but a bit messy, not handled automatically. Jan 03 22:01:02 (possibly multiple proprietary compilers) Jan 03 22:01:26 looking for meta-sourcery layer now... Jan 03 22:01:27 iirc meta-freescale does that to a certain extent to handle running a 64-bit toolchain / configuration for the kernel/bootloader while the rest is 32 Jan 03 22:01:33 layers.openembedded.org Jan 03 22:02:06 thanks Jan 03 22:02:14 np Jan 03 22:03:14 just running the external toolchain is trivial, but we also need to pull files out of the external toolchain sysroot to populate the internal recipe sysroots as well as to emit the binary packages we need to create the root filesystem Jan 03 22:03:47 since the external toolchain sysroot is just a pile of tons of files, we need recipes that list the files we need to include in each package, unless you want to create a single monolithic recipe/package for the entirety, which most tend to avoid Jan 03 22:04:53 meta-external-toolchain helps with it, in the recipe in question, you list the files in the FILES variables we already use for our packaging, and it'll automatically search for and extract those files from the external toolchain. it has existing recipes for the common components, though glibc is a bit messy, since it has to list each individual header file Jan 03 22:05:35 still new to yocto, in general, so I'll just start staring at the code and hope it starts to make sense. :) Jan 03 22:06:16 appreciate all the information/pointers! Jan 03 23:27:56 New news from stackoverflow: Yocto install glibc-locale components Jan 03 23:58:02 New news from stackoverflow: In Bitbake use existing debian maintainer script Jan 04 02:28:29 New news from stackoverflow: Log files with same content after build [on hold] **** ENDING LOGGING AT Thu Jan 04 03:00:01 2018