**** BEGIN LOGGING AT Mon Sep 16 02:59:59 2013
Sep 16 20:54:52 <fenrig> Hi i'm having troubles with "linux-firmware-iwlwifi-license", I probably have to do something to include it?
Sep 16 20:56:00 <fenrig> or accept the license
Sep 16 21:46:09 <fenrig> So I tried adding a license whiteflag for propietary licenses, but that doesn't fix the problem -.-
Sep 16 22:18:59 <fenrig> Hi i'm having troubles with "linux-firmware-iwlwifi-license", I probably have to do something to include it? to accept the license?
Sep 16 22:44:09 <Crofton|work> hmm
Sep 16 22:44:18 <Crofton|work> where is this bb file locates?
Sep 16 22:44:23 <Crofton|work> which layer?
Sep 16 22:44:38 <fenrig> Crofton|work: well I can't find it :/
Sep 16 22:44:56 <Crofton|work> grep iwl * -r ?
Sep 16 22:46:51 <fenrig> Crofton|work: give me a sec ;)
Sep 16 22:47:13 <fenrig> https://gist.github.com/fenrig/6587631
Sep 16 22:47:17 <fenrig> here is the error :D
Sep 16 22:47:26 <fenrig> let me do the grep for a moment ;)
Sep 16 22:47:45 <fenrig> I tried "find | grep iwlwifi"
Sep 16 22:49:39 <fenrig> Crofton|work: "grep iwl * -r" returns a lot of matches in binaries, but nothing useful yet
Sep 16 22:50:35 <fenrig> Crofton|work: I find a lot of references of it in linux-firmware_git.bb
Sep 16 22:50:49 <fenrig> but I really need that package for another dongle
Sep 16 22:51:02 <Crofton|work> try asking in #oe/#yocto
Sep 16 22:51:19 <Crofton|work> it would appear that it comes from oe-core as part of the kenel build i think
Sep 16 22:51:31 <fenrig> I'm already consulting yocto
Sep 16 22:51:35 <fenrig> but not yet oe 
Sep 16 22:51:38 <fenrig> I'll try there
Sep 16 22:51:41 <Crofton|work> maybe
Sep 16 22:51:43 <Crofton|work> hmm
Sep 16 22:51:59 <Crofton|work> #oe and #yocto are almst but not quite the same people
Sep 16 22:52:39 <fenrig> Crofton|work: okay :)
Sep 16 22:53:19 <Crofton|work> openembedded-core/meta/recipes-kernel/linux-firmware/linux-firmware_git.bb:FILES_${PN}-iwlwifi-license =   "/lib/firmware/LICENCE.iwlwifi_firmware"
Sep 16 22:53:31 <Crofton|work> so it should be pakcged
Sep 16 22:53:40 <Crofton|work> oddly I can work out how it gets into the image
Sep 16 22:53:47 <Crofton|work> does your kernel have this file
Sep 16 22:54:08 <Crofton|work> ahh
Sep 16 22:54:21 <Crofton|work> the firmware ipks RDEPEND on the license
Sep 16 22:54:29 <fenrig> Crofton|work: ...
Sep 16 22:54:41 <Crofton|work> I feel like your kernel source has the firmware, but not the licesne file
Sep 16 22:54:43 <fenrig> Crofton|work: can you elaborate on that, I'm still a noob at yocto/oe
Sep 16 22:54:52 <Crofton|work> so there are ipks with the firmware
Sep 16 22:55:00 <Crofton|work> and they pull in the license ipk
Sep 16 22:55:04 <Crofton|work> make sense?
Sep 16 22:55:18 <Crofton|work> but the linux-firmware recipe didn't find the license so no ipk
Sep 16 22:55:54 <fenrig> Crofton|work: yeah kinda :)
Sep 16 22:56:01 <Crofton|work> run with that idea
Sep 16 22:56:08 <fenrig> Crofton|work: So how do I go about fixing it ?
Sep 16 22:56:13 <Crofton|work> read the recipe
Sep 16 22:56:20 <Crofton|work> and watch build messages carefully
Sep 16 22:58:26 <Crofton|work> maybe you just need to allow it to build things with the Propietaty license
Sep 16 22:58:48 <fenrig> Crofton|work: I tried that already :)
Sep 16 22:58:59 <fenrig> LICENSE_WHITEFLAG = "Proprietary"
Sep 16 22:59:04 <Crofton|work> do you see the license ipks or any weird messages
Sep 16 23:00:20 <fenrig> Crofton|work: I'll take a look at the error log 
Sep 16 23:00:33 <fenrig> Crofton|work: but at first inspection I did not find much information
Sep 16 23:03:04 <Crofton|work> remind me how to run bitbake in setiup scrpt land
Sep 16 23:03:21 <fenrig> Crofton|work: uhm :D
Sep 16 23:03:32 <fenrig> Crofton|work: are you using angstrom v2013.06?
Sep 16 23:03:39 <Crofton|work> I got it
Sep 16 23:03:52 <Crofton|work> DISTRO            = "angstrom"
Sep 16 23:03:52 <Crofton|work> DISTRO_VERSION    = "v2013.06"
Sep 16 23:04:36 <fenrig> Crofton|work: when you ran ./oebb.sh
Sep 16 23:04:47 <Crofton|work> yeah
Sep 16 23:04:56 <fenrig> It produces a enviroment-... file
Sep 16 23:05:00 <fenrig> you have to source it :)
Sep 16 23:05:04 <Crofton|work> running it now
Sep 16 23:05:06 <fenrig> it's probably in setup-scripts
Sep 16 23:05:23 <fenrig> and then you can run bitbake like usual :)
Sep 16 23:06:20 <fenrig> do you need my image :)
Sep 16 23:06:30 <fenrig> because I'm using a custom image .bb file :)
Sep 16 23:06:37 <fenrig> I'll gist it :p
Sep 16 23:06:51 <Crofton|work> http://pastebin.com/tex4bKHu
Sep 16 23:08:09 <fenrig> https://gist.github.com/fenrig/b4fe637fd9bf24d0dfc2
Sep 16 23:08:56 <fenrig> Crofton|work: I don't see any license ?
Sep 16 23:11:35 <fenrig> Crofton|work: also I have to note that it only happens when populating the sysroot
Sep 16 23:11:49 <Crofton|work> the ipk does not end up in the ipk directory
Sep 16 23:12:10 <Crofton|work> you could edit the linux firmware recipe and elimniate the RDEPENDS lines :)
Sep 16 23:13:16 <fenrig> Crofton|work: yeah I already did that once, but I thought I should notify you guys and try to find a better solution
Sep 16 23:13:36 <fenrig> Crofton|work: I was also thinking I was missing something, but apparently this is something new 
Sep 16 23:13:41 <Crofton|work> yeah
Sep 16 23:14:26 <fenrig> Crofton|work: Well thx anyway :D now i can comment that line out in peace :D
**** ENDING LOGGING AT Tue Sep 17 02:59:58 2013