**** BEGIN LOGGING AT Tue Dec 16 02:59:58 2014
Dec 16 05:46:32 <fishey> I'm seeing an kernel version being used when I do runqemu despite it building the new one (maybe it didn't completely install?) any ideas?
Dec 16 07:26:09 <fishey> any guesses when kernel 3.18 will land?
Dec 16 07:26:14 <fishey> or bluez5?
Dec 16 07:26:19 <fishey> or libsanitizer?
Dec 16 07:31:17 <LetoThe2nd> fishey: exactly when someone has submitted patches than have then been accepted for upstream.
Dec 16 09:16:01 <LetoThe2nd> in master the DISTRO_FEATURES systemd and udev are mutually exclusive. since when is this active? e.g., will a modified distro config break on daisy?
Dec 16 09:25:32 <teachme> On this URL https://communities.intel.com/docs/DOC-22226, there are 2 huge files "Board Support Package (Yocto archive 1 of 2)" and "Board Support Package (Yocto archive 2 of 2)". Do I need to download these 2 huge files to compile a Yocto image for Galileo board?
Dec 16 09:36:43 <teachme> Hi. Anyone around?
Dec 16 09:36:46 <abelloni_> yprobably not
Dec 16 09:37:02 <teachme> Would you know what time do they come in? How long more to wait?
Dec 16 09:37:27 <abelloni_> but I would think it contains everything that will downloaded by the build proce"ss anyway
Dec 16 09:37:29 <teachme> bluelightning:  glad to see you here
Dec 16 09:37:53 <teachme> On this URL https://communities.intel.com/docs/DOC-22226, there are 2 huge files "Board Support Package (Yocto archive 1 of 2)" and "Board Support Package (Yocto archive 2 of 2)". Do I need to download these 2 huge files to compile a Yocto image for Galileo board?
Dec 16 09:39:04 <teachme> abelloni_: thanks. But if I have problem downloading certain source code due to firewall blocking while building, should I download these 2 huge files to work around?
Dec 16 09:39:47 <bluelightning> morning all
Dec 16 09:41:27 <teachme> bluelightning: good morning. I just ran 'bitbake image-full-galileo'. Got some error. http://pastebin.com/E7bNJTnV
Dec 16 09:42:32 <bluelightning> teachme: I'm surprised they have not fixed that already
Dec 16 09:43:30 <bluelightning> teachme: you basically need to make the following fix to the recipe: http://lists.openembedded.org/pipermail/openembedded-devel/2014-June/096235.html
Dec 16 09:43:34 <teachme> bluelightning: not sure if it is my fault, actually. I followed instructions in Quark_BSP_BuildandSWUserGuide_329687_006.pdf
Dec 16 09:44:30 <bluelightning> teachme: no, it was caused by upstream repository being re-created, but I thought they'd updated the recipe already for that
Dec 16 09:49:13 <teachme> bluelightning: thanks. I am figuring out how to use diff. Never used it before.
Dec 16 09:49:36 <bluelightning> teachme: in this instance the change is so trivial you can make the edit manually ;)
Dec 16 09:49:49 <bluelightning> but a useful thing to know in any case
Dec 16 09:54:13 <teachme> just made the changes. Hope I did the right thing. Building now. So far so good
Dec 16 09:54:41 <teachme> would you know how long it takes to 'bitbake image-full-galileo'?
Dec 16 09:55:12 <bluelightning> teachme: depends on how fast your machine is, really
Dec 16 09:57:28 <teachme> encountered error again. http://pastebin.com/i3mYH57L My guess is that git got blocked by the firewall. Do you think that is the case?
Dec 16 09:58:12 <bluelightning> teachme: are you behind some form of proxy?
Dec 16 09:58:55 <teachme> Yes. I'm in my company office. I think the firewall is too strict.
Dec 16 09:59:35 <teachme> On this URL https://communities.intel.com/docs/DOC-22226, there are 2 huge files "Board Support Package (Yocto archive 1 of 2)" and "Board Support Package (Yocto archive 2 of 2)". Should I download these 2 files to work around the firewall?
Dec 16 10:00:27 <bluelightning> I honestly don't know what is in those, but I am guessing by the size that it includes the source
Dec 16 10:01:06 <bluelightning> but to be honest if a proxy is available you should be able to set that to fetch from the git repositories
Dec 16 10:01:22 <teachme> bluelightning: what time is it at your side now? Around what time is this irc channel active so that I can get support?
Dec 16 10:02:06 <teachme> the proxy is out of my control. Those IT guys are too strict and bureaucratic. Guess I have to try out from home
Dec 16 10:03:38 <bluelightning> teachme: you don't necessarily need control over the proxy itself, just knowing the address may be enough
Dec 16 10:03:57 <bluelightning> teachme: see https://github.com/openembedded/oe-core/blob/master/meta/conf/site.conf.sample for the example configuration required for git proxy usage
Dec 16 10:04:44 <bluelightning> teachme: it's 10AM here in the UK... this channel is active-ish at most times of the day, but it may not always be the best place to get galileo-specific support
Dec 16 10:05:27 <teachme> Then, besides here, where can I get galileo-specific support?
Dec 16 10:05:33 <bluelightning> teachme: the primary forum for galileo is https://communities.intel.com/community/makers
Dec 16 10:06:03 <bluelightning> I'm happy to help here if I'm around though
Dec 16 10:06:33 <bluelightning> (if I'm able to be helpful, of course)
Dec 16 10:08:05 <maxin> Is there any particular reason why meta-fsl-ppc  master still uses openssl-1.0.1g (PREFERRED_VERSION_openssl = "1.0.1g")
Dec 16 10:08:29 <teachme> Glad that you're here. let me try out the proxy. are you the only Intel guy here?
Dec 16 10:09:04 <bluelightning> teachme: no, there are others as well
Dec 16 10:09:36 <bluelightning> maxin: I can't think of a good one, please ping the layer maintainer
Dec 16 10:10:08 <maxin> bluelightning: thanks, sure..
Dec 16 10:12:59 <teachme> In https://github.com/openembedded/oe-core/blob/master/meta/conf/site.conf.sample, I cannot find oe-core/meta/conf/site.conf.sample. This file is in openembedded. Is it also available in yocto?
Dec 16 10:14:08 <teachme> bluelightning: Is this irc channel only up during UK time? Is it up during Asia time? Time over here now is 6:13 pm
Dec 16 10:15:37 <bluelightning> teachme: in poky you will find it in meta-yocto/conf/site.conf.sample
Dec 16 10:16:02 <bluelightning> teachme: it's an international channel, it's open 24/7 :)
Dec 16 10:26:17 <teachme> is it also available during the weekend?
Dec 16 10:31:23 <LetoThe2nd> there is always weekend somewhere :)
Dec 16 10:31:50 <teachme> Got to go now. Thanks for your support, bluelightning
Dec 16 10:32:16 <bluelightning> teachme: it's quieter but there's always someone around yes
Dec 16 10:32:22 <bluelightning> teachme: ok, no problem - cya
Dec 16 11:00:49 <boucman_work> hello everybody
Dec 16 11:01:16 <boucman_work> what is the magic command to force bitbake to regenerate a rootfs from scratch ? I have doubts whith his current state
Dec 16 11:08:03 <bluelightning> boucman_work: if you mean really from scratch, just delete your TMPDIR and SSTATEDIR (tmp and sstate-cache by default)
Dec 16 11:08:14 <bluelightning> boucman_work: what is causing you to have doubts about its current state?
Dec 16 11:08:49 <boucman_work> when I launch a certain binary, it launches correctly in my build, but it has some libraries not found on my customer's image
Dec 16 11:09:12 <boucman_work> the libraries are there, in a specific dir, there is a file in /etc/ld.so.conf.d/ to point there
Dec 16 11:09:21 <boucman_work> so it seems ldconfig was run for me but not for him
Dec 16 11:09:49 <boucman_work> (I didn't find anything in the doc on how to tell yocto to run ldconfig, I assume it's at the end of the rootfs build stage)
Dec 16 11:10:14 <boucman_work> if possible I would like to avoid recompiling since that's probably not the problem here
Dec 16 11:13:03 <frsc_> boucman_work: I guess "bitbake <image-name> -c rootfs -f" to force regeneration of the rootfs only
Dec 16 11:13:16 <frsc_> should work
Dec 16 11:13:21 <boucman_work> awesome, i'll try that, thx
Dec 16 11:39:56 <noisebleed> Hi all. I'm trying to launch my first image through runqemu but I'm stuck after "Setting up tap interface under sudo"
Dec 16 11:40:22 <noisebleed> sudo is asking for some password, and I don't know which one. Empty doesn't work as stated in the video tutorial
Dec 16 11:40:51 <bluelightning> noisebleed: it will be your user's password on your system (it needs privileges on your system to set up the tap interface)
Dec 16 11:41:08 <noisebleed> bluelightning: the guest system?
Dec 16 11:41:17 <bluelightning> noisebleed: no, the host
Dec 16 11:44:30 <noisebleed> bluelightning: thank you, I've reinstalled my OS last week and forgot to setup sudo. my fault. thanks again!
Dec 16 11:44:38 <bluelightning> noisebleed: no worries
Dec 16 12:51:46 <RagBal> I'm trying to build a simple image with qt5 in it, the image itself builds perfectly but the meta-toolchain-qt5 doesn't, it complains about unable to satisfy a dependency package qttools-plugins : http://pastebin.com/3JPteduq
Dec 16 12:52:31 <RagBal> Can anybody shed some light in this matter?
Dec 16 13:02:14 <abelloni_> RagBal: can you add ALLOW_EMPTY_qttools-plugins = "1" to you local.conf and test again ?
Dec 16 13:12:48 <boucman_work> Ok, I tested some more and it seems indeed that yocto doesn't update ld.so.cache when I add a file in /etc/ld.so.conf.d/ I need to manually run ldconfig on the image
Dec 16 13:13:13 <boucman_work> is that a known issue ? is there something I need to do in the relevant .bb to tell yocto that I'm adding a new ld.so path ?
Dec 16 13:14:50 <RagBal> abelloni_, thanks I'm going to try it right away
Dec 16 13:23:31 <RagBal> abelloni_, the sdk just finished, thnx! Any way I can prevent the need of "ALLOW_EMPTY_qttools-plugins" added to my local.conf?
Dec 16 13:24:13 <abelloni_> I would add it to the machine configuration but I'm not sure this is the correct way
Dec 16 13:26:34 <boucman_work> is there a way to "configure" the target easily (set the hostname, enable dhcp at startup, that sort of stuff...)
Dec 16 13:37:04 <RagBal> abelloni_, ok but why do I need this setting?
Dec 16 14:39:33 <achest> Hello! I want to Compile(use) some java jni app. I made a recipe and bekam a compile Error ( no jni.h found) what cann a do?
Dec 16 14:40:25 <achest> I 'm working with this app: https://github.com/entropia/libsocket-can-java
Dec 16 14:54:15 <abelloni_> RagBal: basically, your qttools-plugins package is empty
Dec 16 14:54:26 <abelloni_> because there are no plugin for your machine
Dec 16 14:54:31 <abelloni_> so it is not generated
Dec 16 14:54:47 <RagBal> Yea I could extrapolate that from the option name =)
Dec 16 14:55:20 <RagBal> Hm ok, shouldn't it rather generate a warning then just stopping the build?
Dec 16 14:56:12 <abelloni_> yeah, ask JaMa :)
Dec 16 14:57:21 <RagBal> Thanks for your help =)
Dec 16 15:28:13 <achest> bluelightning: can you help me to compile some java jni library?
Dec 16 15:28:38 <bluelightning> achest: I have no knowledge of jni at all, sorry
Dec 16 15:31:06 <achest> bluelightning: I want to use this: https://github.com/entropia/libsocket-can-java or some other libraries (ARM)
Dec 16 15:31:39 <achest> bluelightning: Ideas how can i compile it?
Dec 16 15:59:53 <sjolley> YPTM:   Ready-Access Number:    8007302996  Access Code:    2705751
Dec 16 16:00:09 <RP> sjolley: Richard joined the call
Dec 16 16:00:12 <sjolley> YPTM: Stephen Joined
Dec 16 16:00:18 <sgw_> YPTM: Saul is here
Dec 16 16:00:23 <benjamirc> YPTM: Benjamin joined
Dec 16 16:00:26 <armpit> YPTM: armin on
Dec 16 16:00:45 <tomz> YPTM: Tom Z on
Dec 16 16:01:07 <sona> YPTM: sona is on
Dec 16 16:02:03 <joeythesaint> YPTM: Joe MacDonald on.
Dec 16 16:02:15 <denix> YPTM: Denys is dialing in
Dec 16 16:02:37 <bluelightning> YPTM: won't be here due to a conflict again
Dec 16 16:02:56 <Guest57658> YPTM: AlexG here
Dec 16 16:03:14 <zeddii> YPTM: Bruce is on for 10 minutes.
Dec 16 16:03:24 <Guest57658> YPTM: FYI, the 1.8_M1.rc1 report is out: https://wiki.yoctoproject.org/wiki/WW51_-_2014-12-07_-_Full_Pass_-_1.8_M1.rc1#Performance_Charts
Dec 16 16:04:01 <alimon> YPTM: alimon here
Dec 16 16:04:16 <boucman_work> multilib + non-standard library path = mess :(
Dec 16 16:09:00 <rburton> YPTM: joined
Dec 16 16:12:06 <sjolley> YPTM is over
Dec 16 17:04:30 <armpit> I will be collection patches for the upcoming 1.7.1 release. please let me know which patches need to be included. use [Dizzy] in the subject line - thanks
Dec 16 17:07:29 <sgw_> armpit: thanks for working as stable maintainer for Dizzy!
Dec 16 19:28:36 <denix> is there any special, but generic handling of VIRTUAL-RUNTIME variables?
Dec 16 20:11:48 <rburton> denix: no
Dec 16 20:17:26 <maharvey> When read-only-rootfs is in effect, bitbake runs the "postinstall" scripts as part of the do_rootfs task, so that the results are included in the rootfs tarball instead of being attempted during the first boot (when they would fail due to the rootfs being read-only). How do I identify such a script as a "postinstall" script (in Yocto 1.5), so that it will get this special handling?
Dec 16 20:19:00 <bluelightning> maharvey: it's not read-only rootfs that causes that to happen, the system always tries to run those scripts when creating the image, it's only if they fail that they get run on first boot
Dec 16 20:19:32 <bluelightning> maharvey: postinstall scripts are defined using pkg_postinst_<packagename> () { ... }
Dec 16 20:20:20 <maharvey> thanks!
Dec 16 20:20:25 <bluelightning> http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#new-recipe-post-installation-scripts
Dec 16 20:22:54 * zeddii heads out for the day
Dec 16 20:27:25 <denix> rburton: if I have 2 mutually-exclusive packages providing the same library, should they both be made virtual?
Dec 16 20:37:51 <fishey> say I want to use mainline linux from git as my kernel. Should I bbappend on linux-yocto-dev to do that? Or something else?
Dec 16 21:16:39 <Crofton|work> now wic is failing
Dec 16 21:16:41 <Crofton|work> weird
Dec 16 21:20:01 <Crofton|work> tomz, ping
Dec 16 21:20:19 <Crofton|work> -gnueabi/core-image-minimal/1.0-r0/rootfs (rc = 1): mkfs.ext4: invalid option -- 'd'
Dec 16 21:22:51 <bluelightning> Crofton|work: sounds like it's using your host mkfs.ext4 rather than the one from the sysroot
Dec 16 21:23:00 <Crofton|work> yeah
Dec 16 21:23:40 <Crofton|work> yep but why?
Dec 16 21:24:18 <Crofton|work> no mkfs.ext4 in sysroot?
Dec 16 21:24:29 <bluelightning> Crofton|work: don't know - has e2fsprogs-native been built?
Dec 16 21:27:01 <Crofton|work> doesn't look like it
Dec 16 21:27:17 <Crofton|work> I suppose this is a bug
Dec 16 21:29:14 <bluelightning> well, there's at least one - wic doesn't check to ensure it exists
Dec 16 21:29:27 <bluelightning> (in the sysroot)
Dec 16 21:29:45 <bluelightning> as to why it didn't get built - what did you do in this tmpdir before running wic?
Dec 16 21:30:04 <Crofton|work> I nuked it and built core-image-minimal
Dec 16 21:32:46 <bluelightning> hmm, what about before that?
Dec 16 21:35:53 <bluelightning> actually, it shouldn't matter
Dec 16 21:36:37 <bluelightning> if ext2, ext3 or ext4 are in IMAGE_FSTYPES then it should have been built
Dec 16 21:37:53 <Crofton|work> they are not
Dec 16 21:37:56 <Crofton|work> I think
Dec 16 21:38:01 <Crofton|work> only ramdisk and tgz
Dec 16 21:38:44 <Crofton|work> that would be recent for this machine since no one was using them and for large images you would run out of disk space making too many images
Dec 16 21:39:11 <Crofton|work> the way the day is going I should go drink and make dinner
Dec 16 21:39:15 <Crofton|work> and start over tomorrow
Dec 16 21:40:41 <bluelightning> that probably explains why it wasn't built, then
Dec 16 21:41:34 <bluelightning> you could always do EXTRA_IMAGEDEPENDS += "e2fsprogs-native" to work around that though
Dec 16 21:43:47 <Crofton|work> yeah, I'll file a bug
Dec 16 21:44:55 <bluelightning> thanks
Dec 16 22:01:37 * Crofton|work curses
Dec 16 22:02:39 <Crofton|work> I think sgw_ may have fixed the issue (from looking at buildhistory) but no opkg  or ssh on core-image-minmal
Dec 16 22:02:46 * Crofton|work goes to work on dinner and drink
Dec 16 22:07:10 <sgw_> Crofton|work: sorry I missed your updates in OE, check that resolvconf patch, I hope it helped.
Dec 16 22:07:22 <Crofton|work> yeah I am
Dec 16 22:07:41 <Crofton|work> just having pain getting the resolvconf package onto core-image-minimal
Dec 16 22:08:02 <Crofton|work> looking at the buildhistory I see things thaat were missing from earlier ones
Dec 16 22:08:14 <Crofton|work> so I am hopeful I can confirm it is better
Dec 16 22:08:21 <Crofton|work> but I need beer
Dec 16 22:49:46 <Crofton|work> sgw_, thanks. The best problems are ones you find are already fixed
Dec 16 22:49:55 <Crofton|work> any idea if it will go into dizzy?
Dec 16 22:52:51 <sgw_> Crofton|work: beer helped?  Sure this is a good candidate, let armpit know, he and I will be pulling some master patches back for the 1.7.1 release
Dec 16 22:53:28 <armpit> we are pulling beer into dizzy ?
Dec 16 22:53:59 <Crofton|work> OK, I'm not familiar with the patches, I jsut got master built
Dec 16 22:54:09 <Crofton|work> I delayed going for beer :(
Dec 16 22:54:29 <sgw_> Crofton|work: Ok, since it was my patch I will get it to armpit
Dec 16 22:54:44 <Crofton|work> is it only the one pacth?
Dec 16 22:54:51 <sgw_> armpit: it's not late enough here for beer yet,
Dec 16 22:55:05 <Crofton|work> I may try installing this on some older rootfs's (since it is only shell)
Dec 16 22:55:07 <Crofton|work> :)
Dec 16 22:55:08 <sgw_> Crofton|work: yes, I think so was about to check my old patches
Dec 16 22:55:09 <Crofton|work> is here
Dec 16 22:55:25 <Crofton|work> I'll try and double check myslef
Dec 16 22:55:44 <Crofton|work> at some point my computer randomly rebooted during a build so today was not fun
Dec 16 22:56:04 <Crofton|work> I upadted the bios that claims to improve stability
Dec 16 22:56:14 <Crofton|work> we'll see if I can get a build in a vm to work :)
Dec 16 22:56:18 <Crofton|work> anyway, thanks
Dec 16 22:56:24 <sgw_> Crofton|work:  here is the patch to search for [OE-core] [PATCH v2] resolvconf: add fixes for busybox and make it work
Dec 16 22:56:32 <Crofton|work> k
Dec 16 22:56:46 <sgw_> armpit: I did mark that one for dizzy once it came into master ^^^
Dec 16 23:22:35 <armpit> sgw_: k
Dec 16 23:26:01 <sgw_> armpit: thanks
Dec 16 23:33:57 <Crofton> and still getting random reboots when building in vms :(
Dec 17 00:23:45 <fishey> hrm. Even when I prefer linux-yocto-dev and it appears to get built, I'm still ending up with a 3.14.0 kernel (vs 3.17.6)
Dec 17 00:24:01 <fishey> is there something that needs to be cleaned when switching kernel versions?
Dec 17 00:26:33 <sgw_> fishey: I assume you are using master?  What MACHINE?
Dec 17 01:20:39 <fishey> sgw_: MACHINE=qemux86 . oe-core from master (if that's what your
Dec 17 01:20:45 <fishey> 're asking)
Dec 17 01:23:04 <fishey> blowing away tmp/ doesn't do any good. using linux-yocto (not -dev) gets me 3.14.19
Dec 17 01:23:35 <fishey> Is there something I can do to adjust the priority of kernel versions, perhaps?
**** ENDING LOGGING AT Wed Dec 17 02:59:59 2014