**** BEGIN LOGGING AT Tue Dec 23 02:59:59 2014 Dec 23 06:54:11 Good morning all Dec 23 07:50:50 hello all Dec 23 07:55:12 I am using raspian and open embedded with toradex boards. The difference is, that I have a reduced busybox on my open embedded system. Is there a easy way to remove the busybox package and use standard debian? Or is this small design the main target of the project without any option to change this? Dec 23 08:53:40 what controls which header files and libraries get included when I "bitbake target -c populate_sdk"? my resulting /opt sysroot does not contain any header files Dec 23 09:18:38 pegu, normally all the libraries and header files used in the target-image Dec 23 09:18:53 which header files are you lacking? Dec 23 09:19:22 morning all Dec 23 09:21:08 AndersD: I don't lack it, I'm just trying to understand where it's located, I don't find it with find in opt, but when I try the hello world tutorial it works so it must be somewhere Dec 23 09:22:55 Ok, so cross-compiling with your installed SDK works? Then the header files has to be under the sysroot in your install location. (Per default e.g. /opt/poky/1.6.1/sysroot/) Dec 23 09:23:45 You can find the location of your sysroot by running: $CC --print-sysroot Dec 23 09:27:17 AndersD: find ~/opt/ -name 'stdio.h' gives no result as I mentioned, but --print-sysroot gives me a clue: /home/yocto/test-yocto/qemuarm # but I don't know where I specified that when I did "bitbake rpi-hwup-image -c populate_sdk" Dec 23 09:27:50 I'm just trying to learn how yocto is tied together... Dec 23 09:29:08 pegu, Have you installed the generated SDK and sourced it's environment-file? Did you install it under /opt, or did you specify another install path during the SDK installation? Dec 23 09:29:55 I'd guess that you have installed it, and changed the installation path to /home/yocto/test-yocto? Dec 23 09:31:45 AndersD: yes I installed it under ~/opt, but I must have specified test-yocto somewhere as they have almost the same creation date Dec 23 09:32:58 Then I'd suggest removing the installed SDK and installing it again. It should all be installed under either the default install path, or the path you supply during installation time. Dec 23 09:33:02 AndersD: I should delete everything as I have quite a few test cases laying around, and re-built the sdk part, then I'll probably figure it out Dec 23 09:33:34 AndersD: I'll do that. Thanks a lot for your help. Dec 23 09:33:46 pegu, no problem! Dec 23 12:18:15 * RP watches bitbake-selftest fail and isn't happy Dec 23 13:01:17 hi, does someone know the differences between qconnman and libconnman-qt? do i need both, imho not, but what should be used when i want to use qt and connman ? Dec 23 13:13:56 grma: AIUI libconnman-qt is just a library which the qconnman UI makes use of Dec 23 13:14:54 bluelightning: so if i want controll connman from qt in need both in my target Dec 23 13:15:35 grma: pretty much yes, unless you're writing your own UI... if you install qconnman you will get the library automatically through dependencies Dec 23 13:15:57 bluelightning: ahh cool, thx now it is clear for me Dec 23 13:49:45 bluelightning: but the qconnman inc file downloads the qconnman-ui ? is there no direct qconnman bb file, i do not whant to use qconnman-ui from OS Systems i want to use qconnman lib from devonit ... Dec 23 13:50:00 but how ? Dec 23 13:50:35 grma: ah, sorry... I didn't know such a thing existed; do we even have a recipe for this qconnman library? Dec 23 13:51:35 i dont think so, the inc file is called qconnman but downloads: git://github.com/OSSystems/qconnman-ui.git Dec 23 13:51:50 so i do not think there is a recipt for devonit lib Dec 23 13:51:53 right, it's not related at all Dec 23 13:52:02 you'll probably have to write a recipe for it Dec 23 13:52:29 :) i ask devonit :) Dec 23 13:55:18 so that means, i don not need libconnman-qt if i only use the devonit lib Dec 23 13:55:23 correct ? Dec 23 13:55:42 I'd assume not, but I really don't know anything about this other library Dec 23 13:55:53 i will give a try Dec 23 15:44:43 halstead: Ping Dec 23 17:51:20 hi guys, just received an info about ntpd vulnerabilities, http://support.ntp.org/bin/view/Main/SecurityNotice Dec 23 17:52:11 in meta-oe we are still on 4.2.6 (affected version), latest from ntp.org, production version is 4.2.8 Dec 23 18:04:49 Xz: hey Dec 23 18:05:09 bluelightning: hi there Dec 23 18:05:37 Xz: ntp isn't really a recipe the Yocto Project maintains, since it's in meta-networking Dec 23 18:05:50 (although you could argue perhaps that it ought to be in OE-Core) Dec 23 18:06:26 the security vulnerabilities were noted the other day though Dec 23 18:07:22 I'm guessing an upgrade would be fairly simple to do; I believe someone may already be working on a patch for just the vulnerabilities but I wouldn't expect it until after christmas Dec 23 18:23:36 I think the easiest way to do it would be just to bump ntp version to 4.2.8 Dec 23 19:03:41 g/ 41 Dec 23 21:43:28 ant__: Hi, i was refferred to you by bluelightning Dec 23 21:45:37 ant__: : got two rather similar problems with creating an initramfs image Dec 23 21:50:25 ant__: first, i want to build some out of source kernel modules to go inside the initramfs - i am using module.bbclass which DEPENDS on kernel - so i get a circular dependency error when building my out of source modules Dec 23 22:45:41 darkhorse_, hi there Dec 23 22:47:39 once you have your own linux-foo recipe which skips conflicting tasks you should be ok Dec 23 22:48:18 however, I've seen there are changes about kernel in the ML, I plan to read and test that soon Dec 23 22:55:19 I mean Dec 23 22:55:21 [PATCH 3/7] kerneldev: create kernel-devsrc packaging Dec 23 22:55:53 [PATCH 2/7] kernel: fix out of tree module builds Dec 23 22:56:04 that oe-core patchset **** ENDING LOGGING AT Wed Dec 24 02:59:59 2014