**** BEGIN LOGGING AT Tue Jul 29 03:00:00 2014 Jul 29 07:22:48 good morning Jul 29 07:41:44 morning all Jul 29 07:43:37 slainte mhath Jul 29 10:16:49 hello guys with whom should I talk about the yocto project bugzilla Jul 29 10:23:58 AlexVaduva: what exactly is your question about it? Jul 29 10:52:20 ls Jul 29 11:00:21 I am interested in talking the possibility of having the meta-cgl bugs reported there Jul 29 11:00:29 would that be possible Jul 29 11:00:55 and if yes what should I do for that to be possible Jul 29 11:29:31 if i want to use the linux-yocto-custom recipe to build my kernel, is it possible to make it use different SRC_URIs depending on machine? or how am I suppose to create linux-yocto-custom recipes for 2 different machines, without copying the contents of linux-yocto-custom.bb into a new file? Jul 29 11:32:50 use overrides Jul 29 11:39:42 ping: any update on my previous message regarding bugzilla? Jul 29 11:42:45 AlexVaduva: write to the mailing list and/or bugzilla owners. Jul 29 12:01:30 I do not know who are the bugzilla owners Jul 29 12:01:45 if you could help with this information I will write to them Jul 29 12:01:57 but I assumed they could be here Jul 29 12:24:02 I don't exactly understand how to use linux-yocto-custom; the example in OE core/meta-skeleton/recipes-kernel/linux/ seem to indicate that I should only have to create a linux-yocto-custom.bbappend file, but AFAIK, there is no linux-yocto-custom.bb file to override (except for the one in the skeleton dir of course). Am I suppose to copy the linux-yocto-custom.bb into my layer, and then extend it using a .bbappend file? because in that case, I m Jul 29 12:24:02 ight aswell just modify the linux-yocto-custom.bb file directly? Jul 29 12:29:30 mago__: see one possible example here http://tinyurl.com/qhys8ec Jul 29 12:57:56 thanks ant_work. i guess that should work for my case also, even though the example is based on yocto-linux and not yocto-linux-custom Jul 29 13:00:04 Hey guys I still got problem by using autotools in a recipe to install wine. layer recipe and sources are all at the right place, do_unpacking works fine and everythin is placed in the working directory. but there is an error while do_configure. there should be some possibly undefined macros but when I look int the configure.ac i can find them there. would be so nice if someone just have a look over a few lines Jul 29 13:00:05 http://pastebin.com/nyhvgUSB Jul 29 13:55:05 is it possible to intall a *.deb package via a recipe ? my probem is that i want to install wine (Wine Is Not an Emulator). I got wine as deb packages here for i386 and want to install this into my yocto image to use it with qemu to emulate the x86 machine, so I see two ways, first one to install the ready deb packages via a recipe or change the machine from arm to i386 for just one building process part with some kind of an overlay ? Jul 29 14:02:37 I do not want to install a package manager to my distribution but I want to install a deb package while buillding it with some commands in a recipe, any buzzwords for me ? Jul 29 14:04:57 motzer: a deb package is just an ar archive with two tarballs inside. one contains the files themselves and the other package metadata. Jul 29 14:05:36 motzer: with a shell script you can extract these and untar in the root directory. running pre-/post-install scripts is also possible Jul 29 14:07:32 but using something like dpkg -i from the host system is not possible ? Jul 29 14:07:52 because then everything should be moved to the right place or ? Jul 29 14:13:25 but thanks acidx i will try it Jul 29 14:56:57 YPTM: Conference Details: Company: WIND RIVER SYS Ready-Access Number: 8007302996/9139049836 Access Code: 2705751 Jul 29 14:57:03 YPTM; Stephen Joined Jul 29 14:57:17 YPTM: AlexVaduva Jul 29 15:00:40 YPTM: bruce joined Jul 29 15:00:42 YPTM: Matthew on the call Jul 29 15:00:56 YPTM: tomz on the call Jul 29 15:01:12 YPTM: Belen joined Jul 29 15:01:31 YPTM: Saul is here Jul 29 15:01:46 * RP joined the call Jul 29 15:01:54 YPTM: Polk is here Jul 29 15:02:06 YPTM: Darren is one Jul 29 15:02:07 on Jul 29 15:02:19 * Jefro is on YPTM Jul 29 15:03:58 YPTM: Cristian on the call Jul 29 15:04:29 YPTM: Michael here. Jul 29 15:05:22 YPTM: Doug Boom is here too Jul 29 15:10:13 YPTM: Paul Eggleton joined Jul 29 15:11:56 YPTM is over Jul 29 15:45:09 i did a stupid thing. copied my poky folder to a different location. now bitbake says TMPDIR has changed location and refuses building. which files do i have to change to make sure i can build yocto images from new location? Jul 29 15:50:43 microd: you need to delete your tmp directory Jul 29 15:51:06 thank you my friend :) Jul 29 15:51:07 microd: that's not as drastic as it sounds, since a lot of it will be able to be restored directly from the sstate cache on the next build Jul 29 15:52:07 anyway, ran out of space on the disk during build ... there was no other choice than moving the local repo Jul 29 15:59:25 right, it definitely happens sometimes Jul 29 16:00:08 the reason it balks is that paths get hardcoded within the sysroot / work directory, so if it didn't detect the move and fail early it would just break horribly later Jul 29 16:00:55 bluelightning: i'm happy it does so, otherwise i would have freaked out later on :D Jul 29 17:53:58 How can I see my yocto project version? Is there any command for it? Jul 29 17:57:30 geckos, you mean at runtime on the target? Jul 29 17:57:42 geckos, it depends on which image/distro you build Jul 29 17:57:55 do you have an /etc/*release* file? Jul 29 18:11:00 dvhart, I mean the build system, I see documentation for 1.4, 1.5 and 1.6 versions but don't know which apply to me Jul 29 20:22:59 dvhart, heads up -- meta-intel dev kernel bbappend is pointing at an ancient kenrel. Jul 29 20:23:02 LINUX_VERSION_corei7-64-intel-common = "3.14-rc8" Jul 29 20:23:23 ack, thanks Jul 29 20:23:34 * paulg was wondering why he wasn't getting 3.16 Jul 29 20:23:54 that would be do to a PREFERRED_VERSION string though Jul 29 20:24:11 this string.... this just impacts what... the package name? Jul 29 20:24:33 yeah, was trying to avoid that and go with whatever was the default in the main linux-yocto-dev.bb Jul 29 20:25:10 for now I guess I can just clear the above to achieve the same effect. Jul 29 20:25:22 assuming my bbappend comes after yours.... ? Jul 29 20:26:18 right, that ordering is frustrating at times :/ Jul 29 20:26:31 dvhart, it might just be the pkg name, as I was seeing the above on the build screen summary, but did find 3.16 in my build dir. Jul 29 20:26:42 which is also rather confusing :/ Jul 29 20:26:45 yeah Jul 29 20:27:01 maintaining the LINUX_VERSION for -dev is kind of silly really Jul 29 20:27:14 would be nice if we could just extract it Jul 29 20:27:20 * paulg won't complain if dvhart zaps the lines entirely. Jul 29 20:27:27 I think I should be able to Jul 29 20:27:37 need to remember why I had to add it in the first place actually Jul 29 20:27:44 there was some annoying reason... checking logs Jul 29 20:27:53 I know the feeling. running git blame on my own work. :) Jul 29 20:28:01 exactly :-) Jul 29 20:28:25 it is even better when you wonder "what arse did this" and then you run git blame and find your own name. Jul 29 20:28:46 *cough* recent CVE *cough* Jul 29 20:29:58 ugh Jul 29 20:30:05 a1491bc54b60a1c622a9060756fd9b145bc01378 Jul 29 20:30:27 -dev should always be AUTOREV.... which means LINUX_VERSION is basically ALWAYS WRONG Jul 29 20:31:03 I wonder.... could LINUX_VERSION be "HEAD" :-) Jul 29 20:31:15 zeddii, have you noodled through this alread? Jul 29 20:31:16 y Jul 29 20:32:18 I *think* I can just drop the SRCREV and LINUX_VERSION stuff from this recipe though now that we have support for these BSPs in linux-yocto-3.14 Jul 29 20:32:57 Has someone found anything regarding the RPM corruption? Jul 29 20:33:07 I got it again in our builder: http://ci.ossystems.com.br/job/fsl-community-bsp-master/228/consoleFull#1269809759df9aaadc-264d-4163-ae95-fd7844a10b4f Jul 29 20:33:08 paulg, if you comment out all the SRCREV lines and all the LINUX_VERSION lines, and specify PREFERRED_PROVIDER of linux-yocto-dev - does it do what you expect? Jul 29 20:36:42 paulg, actually... I should have removed them in 8b4ab82 intel-common: Remove SRCREVs from linux-yocto-dev Jul 29 20:36:45 I'll do that now.. Jul 29 20:43:00 how would I force a recipe to be compiled with GCC 4.8 instead of 4.9 Jul 29 20:43:15 paulg: Currently 1 running tasks (199 of 419): Jul 29 20:43:15 0: linux-yocto-dev-3.16++gitAUTOINC+f4e98fa4f9_78e9cbe1e8-r0 do_fetch (pid 14791) Jul 29 20:43:23 would be okay with forcing all other recipes too if I have to Jul 29 20:43:37 I don't think gcc uses the PROVIDES mechanism Jul 29 20:44:14 dvhart, looks good ; push it out and I'll pull it in. B) Jul 29 20:45:37 paulg, are you on master or daisy? Jul 29 20:46:41 master I think - let me check Jul 29 20:46:56 yep, master. Jul 29 20:47:42 k, mail on the meta-intel list - tomz_ would you take a quick look? If you don't see any issues I'd like to push this now Jul 29 21:08:00 ah, found it Jul 29 21:08:01 GCCVERSION Jul 30 00:08:01 is there some way to indicate in a recipe that not all CPU architectures are supported by the program it's building? Jul 30 00:08:21 such that it will display an error when someone tries to compile it for a target it doesn't support **** ENDING LOGGING AT Wed Jul 30 03:00:01 2014