**** BEGIN LOGGING AT Tue Jan 20 02:59:59 2015
Jan 20 09:50:50 <spaszkoPL> morning everyone
Jan 20 10:05:25 <Crofton|work> WHy i smy build trying to build two kernels?
Jan 20 10:18:21 <koen> likely one kernel recipe lacks COMPATIBLE_MACHINE
Jan 20 10:18:23 <Crofton|work> Why would a kernel for a machine that is not the one I am building for build?
Jan 20 10:18:30 <Crofton|work> hmmm
Jan 20 10:18:42 <Crofton|work> let me think about this
Jan 20 10:18:50 <Crofton|work> I'm using linux-dummy
Jan 20 10:18:58 <koen> if you're building for an intel architecture, that new intel-foo-common thing will always drag in linux-yocto
Jan 20 10:19:17 <Crofton|work> thi salso happens in dizzy
Jan 20 10:19:18 <koen> I had to resort to PNBLACKLIST'ing linux-yocto in my x86 machine configs
Jan 20 10:19:40 <koen> I need to fix linux-dummy to support work-shared
Jan 20 10:20:17 * koen waits for cognitive dissonance to hit everyone
Jan 20 10:30:37 <bluelightning> morning all
Jan 20 10:35:23 <Crofton|work> COMPATIBLE_MACHINE_zynq = "zynq"
Jan 20 10:35:23 <Crofton|work> KMACHINE_zynq ?= "zynq"
Jan 20 10:35:39 <Crofton|work> ?
Jan 20 10:36:16 <koen> COMPATIBLE_MACHINE_zynq = "zynq"
Jan 20 10:36:31 <koen> that needs context
Jan 20 10:36:34 <koen> in a recipe it's bogus
Jan 20 10:36:35 <Crofton|work> nrossi, is likely asleep
Jan 20 10:36:45 <koen> in a bbappend it's the right thing to do
Jan 20 10:36:59 <hrw> zynq?
Jan 20 10:38:07 <hrw> Xilinx has job offer. System Software Architect for Zynq
Jan 20 10:38:22 <Crofton|work> where at?
Jan 20 10:39:00 <hrw> San Jose
Jan 20 10:39:14 <hrw> Crofton|work: mail you details?
Jan 20 10:39:25 <Crofton|work> I am curious
Jan 20 10:39:31 <Crofton|work> mainly because we use their stuff
Jan 20 10:39:48 <hrw> http://pastebin.com/JEW7rZ53
Jan 20 10:40:59 <Crofton|work> there are a lot of words and not many specifics
Jan 20 10:41:35 <hrw> yep
Jan 20 10:42:58 <Crofton|work> I think they are looking for a thought leader
Jan 20 10:44:17 <Crofton|work> arg, I need to work out if the eveil is really using meta-xilnx and then building for non-zynq machines
Jan 20 11:00:49 <Crofton|work> hmm, I think part of the issue is tools-profile brings in oprofile, which wants kernel-vmlinux
Jan 20 11:00:58 <Crofton|work> which appears to not come from linux-dummy
Jan 20 11:16:10 * Crofton|work wonders if we should drop oprofile from the package group and favour perf instead
Jan 20 11:33:26 <koen> Crofton|work: perf needs kernel-source, which linux-dummy doesn't provide
Jan 20 11:33:33 <koen> Crofton|work: that's what I'm trying to fix now :)
Jan 20 11:33:43 <Crofton|work> yeah, but it is a rrecommends
Jan 20 11:33:51 <Crofton|work> I just need something to build
Jan 20 11:34:09 <koen> ERROR: Task do_configure in /build/linaro/build/openembedded-core/meta/recipes-kernel/perf/perf.bb depends upon non-existent task do_shared_workdir in /build/linaro/build/openembedded-core/meta/recipes-kernel/linux/linux-dummy.bb
Jan 20 11:34:16 <Crofton|work> if I kill all the providers for the kernel-vmlinux the build carries on
Jan 20 11:34:23 <Crofton|work> yep, I see that also
Jan 20 11:34:47 <Crofton|work> I've been thinking about talking about dropping oprofile for a bit
Jan 20 11:39:56 <Crofton|work> from the tools-profile packagegroup
Jan 20 11:46:53 <spaszkoPL> One question, where is finger command? Is it in busybox with special configuration or it has own recipe(could you tell me in which layer)? 
Jan 20 11:49:34 <Crofton|work> layers.openembedded.org might help
Jan 20 15:04:58 <Crofton|work> koen, my linux-dummy issue is partially caused by oprofile triggering builds of other kernel recipes
Jan 20 15:11:23 <bluelightning> Crofton|work: I have filed https://bugzilla.yoctoproject.org/show_bug.cgi?id=7202, FYI
Jan 20 15:11:49 <Crofton|work> Invalid bug id?
Jan 20 15:12:05 <Crofton|work> ah, the comma got into the link
Jan 20 15:12:20 <Crofton|work> thanks
Jan 20 15:12:54 <Crofton|work> I need to get this machine away from needing it :)
Jan 20 15:13:32 <Crofton|work> I beat it into spitting out a rootfs and need to go look at what they have in meta-gumstix again
Jan 20 16:04:10 <awozniak> in oe-core, is there a way to tell the recipe NOT to cache specific elements in SRC_URI ?  I have a special case where a firmware blob is in active development, and I want to make sure I fetch whatever is current on the download site every time.
Jan 20 16:07:17 <koen> ah, you want a non-deterministic build
Jan 20 16:07:21 <koen> good luck with that
Jan 20 16:07:42 <Crofton|work> koen, sometimes people want them :)
Jan 20 16:14:43 <LetoThe2nd> well who wouldn't want a little randomness in software?
Jan 20 16:15:07 <awozniak> fair point.  Maybe I should take care of it out of the oe build system.
Jan 20 16:19:20 <bluelightning> AFAIK, we support that kind of thing for git://, but not individually fetched files 
Jan 20 19:07:49 <Crofton|work> Do we have a nativesdk-python- everything target?
Jan 20 19:11:28 * Crofton|work guesses nativesdk-python-modules is what he wants
Jan 20 21:08:38 <chrisw987> Hi, I'm using udev 182-r7, and ppp device is not getting created.  I think it is related to links.conf, but even with that file in /etc/udev, it doesn't get created.  Any pointers?
Jan 20 23:14:46 * kergoth hacks around meta-fsl-arm's fsl-kernel-localversion - https://github.com/MentorEmbedded/meta-mentor/commit/247a521
**** ENDING LOGGING AT Wed Jan 21 02:59:58 2015