**** BEGIN LOGGING AT Thu Nov 03 02:59:59 2011
Nov 03 03:29:15 <hrw> Crofton|work: grab gource and play with options
Nov 03 03:29:25 <hrw> Crofton|work: and prepare for loooong time
Nov 03 04:36:40 <adriano87> why is it that when i rebuild the kernel ( bitbake -k linux-yocto ) after reconfiguring the kernel (bitbake -c menuconfig linux-yocto), it does not include my new modules in the modules.tar.gz?
Nov 03 04:53:18 <adriano87> why is it that when i rebuild the kernel ( bitbake -k linux-yocto ) after reconfiguring the kernel (bitbake -c menuconfig linux-yocto), it does not include my new modules in the modules.tar.gz?
Nov 03 04:54:06 <adriano87> it seems like the kernel was not rebuilt
Nov 03 10:58:39 <mckoan> good morning
Nov 03 12:52:09 <Crofton|work> RP__, hopefully people do not read the internet slang book and start using more of it :)
Nov 03 12:56:09 <RP__> Crofton|work: I was thinking that :)
Nov 03 13:07:15 <Crofton|work> bluelightning, http://pastebin.com/n5AP4fDC
Nov 03 13:07:38 <Crofton|work> still need to work out if the gnuradio cmake is making it find x86 headers
Nov 03 13:27:15 <bluelightning> hi Crofton|work
Nov 03 13:27:50 <bluelightning> I saw your pastebin before I went offline last night, I had missed that it was pulling in x86 stuff though
Nov 03 13:27:55 <bluelightning> clearly wrong :;/
Nov 03 13:33:25 <Crofton|work> yeah
Nov 03 13:33:39 <Crofton|work> looking at output oc cmake config
Nov 03 13:33:45 <Crofton|work> and seeing some inteesting warnings
Nov 03 13:35:19 <bluelightning> Crofton|work: do you have any changes on top of gnuradio recipe in meta-oe or is it the same version I just pulled?
Nov 03 13:35:34 <bluelightning> (wondering if I should just try building it here...)
Nov 03 13:36:51 <Crofton|work> http://pastebin.com/XbdZDCtg
Nov 03 13:37:04 <Crofton|work> I do not have an up to date one committed yet :(
Nov 03 13:37:18 <bluelightning> Crofton|work: so, why is gnuradio.inc setting HOST_SYS?
Nov 03 13:38:13 <Crofton|work> history I suspect
Nov 03 13:38:18 <Crofton|work> there is python around
Nov 03 13:39:50 <Crofton|work> you are thinking they should be removed?
Nov 03 13:42:13 <Crofton|work> it look slike cmake is picking up the x86 systroot stuff
Nov 03 13:42:17 <bluelightning> Crofton|work: well, I'm not entirely sure what those are doing; they look like they might be legacy
Nov 03 13:42:26 <bluelightning> probably not related to the issue at hand though
Nov 03 13:43:48 <Crofton|work> yeah
Nov 03 13:45:22 <Crofton|work> hmm
Nov 03 13:45:28 <Crofton|work> need to look at configure out again
Nov 03 13:45:39 <Crofton|work> cinfigure errors without them set btw
Nov 03 13:48:13 <Crofton|work> -- Found Qt4: /home/balister/src/git/oe-core/build/tmp-angstrom_2010_x-eglibc/sy
Nov 03 13:48:13 <Crofton|work> sroots/x86_64-linux/usr/bin/qmake2 (found suitable version "4.7.4", required is
Nov 03 13:48:13 <Crofton|work> "4.2.0")
Nov 03 13:48:23 <Crofton|work> line from cmake, it finds qt in x86
Nov 03 13:48:45 <Crofton|work> so the question is, how does cmake find qt
Nov 03 13:49:15 <Crofton|work> the gnuradio cmake guru is on the west coast :(
Nov 03 13:50:49 <bluelightning> hmm... we need some way of forcing it not to look in that place
Nov 03 13:53:24 <Crofton|work> yeah
Nov 03 13:53:44 <Crofton|work> I guess I need to read the cmake source :(
Nov 03 13:54:09 <bluelightning> all the qt finding logic is in a FindQT4.cmake file IIRC
Nov 03 13:55:15 <Crofton|work> yep
Nov 03 16:46:01 <gebi> hi all :)
**** BEGIN LOGGING AT Thu Nov 03 21:40:18 2011
Nov 03 21:49:22 <ant____> JaMa|Wrk: I built for c7x0 after building for poodle. No strange rebuilds here
Nov 03 22:08:59 <JaMa|Wrk> ant____: I've just sent mail with analysis :)
Nov 03 22:09:16 <ant____> thx !
**** ENDING LOGGING AT Fri Nov 04 02:59:57 2011