**** BEGIN LOGGING AT Mon Mar 28 02:59:58 2016 Mar 28 14:08:34 Has anyone experienced recipes which have not been inbcluded in a build throwing build errors? Specifically for meta-qt5. If so, how did you resolved it or how did you trace where the recipe was being called form? Mar 28 14:10:07 from* Mar 28 14:41:54 hello Mar 28 14:52:57 gm Mar 28 15:12:07 where is a channel for talking about problems with a yocto build problems? #yocto seems vacant or not on topic for this type of talk. Mar 28 15:25:38 davis: #yocto or #oe are both fine and both fairly active Mar 28 15:25:52 it's just quite early in some timezones, it gets more active a bit later Mar 28 15:27:52 both channels are for the same thing, with slightly differenet sets of people Mar 28 15:28:02 highly annoying, especially for new people Mar 28 15:28:15 just ask the question Mar 28 15:28:28 and people will answer as they look at the window Mar 28 15:32:19 kergoth: i'll be honest. The yocto docs on the yoctoproject.org are massive. Its almost so big I feel like skipping them and just trying to figure out the code. Mar 28 15:32:52 i'm trying to take a yocto project which was originally for a ubuntu 12 desktop and get it working on a modern ubuntu. Mar 28 15:33:19 the build system is so tied to ubuntu 12 desktop, i can't get it working on any other release. Mar 28 15:34:13 it complains that sdl is not installed but on my newer box I have it installed with the same package name and the same tools and libraries are available, but I can not track down why it fails on the config. Mar 28 15:36:02 i've done builds on pretty much every distro you can imagine, yocto itself isn't tied to ubuntu. yours might be. regardless, either install the sdl development package for your distro, or edit conf/local.conf and comment out the sdl related lines that enable its use in qemu-native Mar 28 15:36:28 if you comment out those lines, qemu will build without gui support, but if you're not running it anyway, or only run it nographic, it wont matter Mar 28 15:36:50 kergoth: that is the point. ive installed the libsdl. its there. Mar 28 15:36:56 again, it's not sdl Mar 28 15:37:01 it's the sdl *development* files Mar 28 15:37:27 andi t will have to be for the correct sdl version. but again, worst case just comment out those lines and move on Mar 28 15:37:35 (that is, i dont think sdk 1.2 and 2.0 are compatible) Mar 28 15:39:07 https://gist.github.com/netskink/e971f975bbbd9fd46a81 Mar 28 15:39:21 kergoth that is the relevant portion of my local.conf Mar 28 15:39:33 yes, i know Mar 28 15:39:47 comment out the 3 uncommented lines and you can build fine regardless of the sdl Mar 28 15:40:15 ok i can try, but I lose the vncsetup right? Mar 28 15:40:29 no, re-read the commented section Mar 28 15:40:37 those lines enable the sdl output *in addition to the vnc output* Mar 28 15:40:45 vnc will be enabled regardless Mar 28 15:41:44 ok, i'll give it a shot Mar 28 15:42:12 i was going to say, I found the section which looked like where it was configuring libsdl Mar 28 15:42:20 and talk about that Mar 28 15:43:17 if this is a redhat based system, i.e. centos, etc, then the package you need is SDL-devel. for ubuntu, it's libsdl1.2-dev, from what i've seen Mar 28 15:43:25 just as an fyi Mar 28 15:45:36 sorry kergoth, i was talking to a coleague Mar 28 15:46:07 yes, its libsdl1.2-dev and yes, i've compared both boxes and they both have this installed. Mar 28 15:46:35 both boxes are ubuntu. its just one is ubuntu 12 desktop and the other is ubuntu 14 server Mar 28 15:46:51 i build on both of those fine Mar 28 15:46:52 * kergoth shrugs Mar 28 15:47:09 i blieve you Mar 28 15:47:41 its just that i'm working with a setup which was probablly written by people who hacked something together and said "ship it" Mar 28 15:48:56 for instance, I dont understand why this setting I found is not in src/build/local-config but in .build-yocto/conf/local.conf Mar 28 15:49:09 strange Mar 28 15:49:29 indeed Mar 28 15:49:37 definitely some custom setup. still, we just run ./configure in qemu, if that's failing, then it's the upstream qemu buildsystem failing to find sdl on the host, it'd probably fail similarly outside of yocto Mar 28 15:50:12 btw, are you German? This who yocto/openembedded seems to European based. Mar 28 15:51:32 not to mention kergoth of bavaria Mar 28 15:51:53 I'm not, no, but you're right, a substantial portion of the core devs are Mar 28 15:51:57 ahh nvm, its barbaria, not bavaria Mar 28 15:52:24 lol, i worked in germany for six months and went camping once in bavaria. very pretty place. Mar 28 15:59:20 hmm. that comment out did not work. i'll try to do a clean build. Mar 28 17:52:38 10266 KiB systemd Mar 28 17:52:38 5348 KiB udev-hwdb Mar 28 17:52:38 2872 KiB systemd-extra-utils Mar 28 17:52:55 I'm pretty sure president Trump would explode if he knew about this Mar 28 18:00:39 ouch Mar 28 18:03:50 yeah Mar 28 18:04:07 seems like some config options where added to help shrink this Mar 28 18:04:22 i saw a couple patch series on the lists about paring down systemd at one point Mar 28 18:04:26 dunno what happened with that Mar 28 18:04:28 I'm trying to make a minimal ramdisk for bringup Mar 28 18:04:38 I need to investigate Mar 28 18:04:40 sounds like you should ditch systemd for the ramdisk entirely Mar 28 18:05:01 yeah, but I am trying to learn new tricks Mar 28 18:17:53 hmm, we have a ling list of systemd features now Mar 28 18:18:04 but we really need something explaining them :) Mar 28 18:20:02 i've thought about that too, would be nice to have a way to document packageconfigs. i.e. PACKAGECONFIG_DOCS[foo] = "a foo thing" or something Mar 28 18:20:08 * kergoth shrugs Mar 28 18:20:27 yeah, I suspect that tracking down the systemd docs would help Mar 28 18:20:45 assuming the systemd docs explain all its configure options (i doubt it :) Mar 28 18:23:28 :) Mar 28 18:55:16 anyone know who lightens is on Stackoverflow? Mar 28 18:55:17 http://stackoverflow.com/questions/36262794/bitbake-bbappend-file-percent-in-filename Mar 28 19:04:23 <3 https://www.ivarch.com/programs/pv.shtml Mar 28 19:38:34 kergoth: is it possible to use a non-systemd initrd with a systemd rootfs? Mar 28 19:39:02 if your distro features includes both sysvinit and systemd, then selection of which is used can be done on a per-image basis, yes Mar 28 19:39:14 afaik, anyway Mar 28 19:39:14 I thought systemd prevents that somehow (ie it wants to be pid 1) Mar 28 19:39:34 I don't mean openembedded-wise :) Mar 28 19:40:00 I don't understand what you mean. when you exec init on the rootfs from the initrd/ramdisk, init is process 1 Mar 28 19:40:13 what you used to boot the initial ramdisk is irrelevent if it's used to start a real rootfs Mar 28 19:40:31 if you're only using the ramdisk alone, then the other image is irrelevent Mar 28 19:41:03 right, I'd need to re-read/check that info (I've never tried) Mar 28 19:41:31 plenty of initrds just use a /init shell script and don't use an init at all Mar 28 19:41:33 most, even Mar 28 19:42:50 yeah that's what I do as well, but I've never tried to run systemd from there Mar 28 19:43:49 as long as you 'exec' from there, the new process will be the same pid as the original process, that's how exec works Mar 28 19:51:04 yeah Mar 28 19:51:54 I think my ramdisk size issue is mainly a problem of load addresses :) Mar 28 23:10:07 ndec_, http://stackoverflow.com/questions/36184976/building-yocto-image-for-dragonboard-410c-how-to-build-chromium **** ENDING LOGGING AT Tue Mar 29 02:59:58 2016