**** BEGIN LOGGING AT Wed Jan 22 02:59:59 2014 Jan 22 03:10:29 hello JaMa Jan 22 04:48:06 hi Jefro Jan 22 04:53:10 Hell JaMa, I'm Robert Yang Jan 22 04:53:31 I'm Sorry, JaMa s/Hell/Hello/ Jan 22 04:54:01 The terrible typo Jan 22 08:56:42 good morning Jan 22 09:17:39 mornin' Jan 22 09:37:58 morning all Jan 22 09:51:14 robertYang: Hello :) Jan 22 09:54:15 Hell JaMa Jan 22 09:54:34 Did you see my reply, please ? Jan 22 09:54:40 yes, just read it Jan 22 09:54:59 as I replied yesterday, it's not about INHERIT Jan 22 09:55:48 Have you checked is there sysroots/qemux86/usr/src/ ? Jan 22 09:58:25 I have another build already running so checking it now wouldn't be very accurate Jan 22 09:59:28 JaMa, thanks,I've got an idea suddenly, let me try it Jan 22 09:59:34 what is weird is, that next build in same directory has also do_patch often failing, because the patches are already applied Jan 22 09:59:38 e.g. Patch binutils-uclibc-100-uclibc-conf.patch can be reverse-applied Jan 22 10:00:17 357 recipes failing like this, so it's not just special case Jan 22 10:00:56 and in this build I've already disabled ARCHIVER_MODE[diff] = "1" Jan 22 10:01:20 JaMa, I wonder what's different between yours and mine Jan 22 10:01:45 I should also say that in my case I'm using archiver.bbclass backported to dylan release Jan 22 10:02:13 JaMa, so you reproduce the errors on dora ? Jan 22 10:02:25 JaMa, but not on master ? Jan 22 10:02:41 I'm not using it on dora or master Jan 22 10:02:59 JaMa, but where ? Jan 22 10:03:28 but backport was rather straightforward, so I don't expect the issue there - it worked OK with that archiver fix I've sent earlier Jan 22 10:03:31 dylan Jan 22 10:03:53 JaMa, I think that there will be errors Jan 22 10:04:00 I only tested it on master ... Jan 22 10:04:06 JaMa, so that's the point Jan 22 10:04:29 JaMa, if we really need it on dylan, we need do more other work Jan 22 10:06:40 JaMa, would you like to try it on master ? Jan 22 10:12:26 if I find time than yes Jan 22 10:12:40 hi all, i have used poky with meta-atmel ,and enabled tools-testapps " EXTRA_IMAGE_FEATURES = "debug-tweaks" "tools-testapps" " option in build/conf/local.conf file after that when the filesystem boot it ask me the passwd,but without tat option it didn't ask me anything eventhough i did not assign any passwd,is there any default passwd for yocto? Jan 22 10:16:40 linu1: do you really have extra quotes in the middle? if so, they shouldn't be there Jan 22 10:17:34 bluelightning, the actual entry is EXTRA_IMAGE_FEATURES = "debug-tweaks" "tools-testapps" Jan 22 10:17:56 linu1: right, it should be EXTRA_IMAGE_FEATURES = "debug-tweaks tools-testapps" Jan 22 10:18:17 that may be why you are seeing the behaviour you are seeing Jan 22 10:18:50 bluelightning, oh ok ok i will change. Jan 22 11:02:09 how come there is no dora branch for meta-raspberrypi? Jan 22 12:50:57 i used to create ubi filesystem in yocto,previously it is working fine,it creates ubi ext3 tar.gz rootfs in /tmp/deploy/images,but i just made a change in local.conf as EXTRA_IMAGE_FEATURES = "debug-tweaks tools-testapps" after the compilation ,there are only ext3 and tar.gz file in images directory,no ubi. my conf entries are http://pastebin.com/U04ipKBc where i did mistake. Jan 22 13:34:58 otavio: ping? Jan 22 13:35:37 rburton: pong Jan 22 13:35:56 otavio: are you still the person to talk to about fsl bsp issues? Jan 22 13:36:07 rburton: maybe, depends Jan 22 13:36:22 rburton: ARM, yes. PPC no. Jan 22 13:36:32 specifically, the autobuilder is failing to build piglit on fsl-arm (piglit being the EGL test suite) Jan 22 13:36:41 | /home/pokybuild/yocto-autobuilder-dev/yocto-slave/nightly-fsl-arm/build/build/tmp/sysroots/imx6qsabresd/usr/include/EGL/eglvivante.h:244:2: error: #error "Platform not recognized" Jan 22 13:36:41 | #error "Platform not recognized" Jan 22 13:36:44 rburton: I found it in my builder Jan 22 13:36:52 rburton: I didn't look at it yet. Jan 22 13:36:56 ok Jan 22 13:37:11 rburton: I am not sure how hard will be to add AMD and Vivante support for it Jan 22 13:37:20 without looking it looks like your egl headers want defines set Jan 22 13:37:23 (mesa wants the same) Jan 22 13:37:48 rburton: if you fixed it in mesa case, please send me the pointer so I can use as reference Jan 22 13:38:01 rburton: but I will look at it; just not today Jan 22 13:38:22 rburton: I am finishing two big patchsets for fsl-arm Jan 22 13:39:16 rburton: I hope to fix this for Friday Jan 22 13:50:50 otavio: are you planning on integrating your meta-ti sdcard_image changes upstream? Jan 22 13:51:10 Net147: I stopped hacking on it for long time Jan 22 13:51:23 Net147: and we did a lot of improvements in our FSL version Jan 22 13:51:38 otavio: where's the fsl version located? Jan 22 13:51:44 Net147: so if you intend to look at it, base in ours Jan 22 13:52:12 http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/tree/classes/image_types_fsl.bbclass Jan 22 13:53:23 I am intending to build an image for BBB Jan 22 13:54:37 Net147: great Jan 22 13:55:04 Net147: the long term solution is to work in the 'wic' tool Jan 22 13:55:35 otavio: does wic support MBR disk signatures? Jan 22 13:56:07 Net147: I think so but it is still quite dump regarding U-Boot handling Jan 22 13:57:12 otavio: I use generated DISK_SIGNATURE support in boot-directdisk.bbclass to generate a root path to pass to kernel from syslinux Jan 22 13:57:40 otavio: great, thanks Jan 22 13:57:51 otavio: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/meta/classes/boot-directdisk.bbclass?id=b52d2bb46ed7c893077ccf9e5a83dc7f11c7f61b Jan 22 13:59:00 Net147: neat! Jan 22 14:05:34 hello Jan 22 14:06:07 i have an issue with multilib in yocto Jan 22 14:06:28 i build a live image for x86_64 that works fine Jan 22 14:07:09 but when i add multilib support my kernel can't load the initramfs Jan 22 14:07:53 and i can't do bitbake virtual/kernel -c menuconfig when multilib is enabled Jan 22 14:08:02 someone has an idea? Jan 22 14:40:07 rburton: you're welcome :-) Jan 22 15:26:47 otavio, do you use libsoc yourself or do you have customers that use it, purely out of interest :) Jan 22 15:55:15 jackmitchell: I have one which will use it ;-) Jan 22 15:56:09 otavio: good to hear, pwm support is upcoming too linux 3.12+ only though :) Jan 22 15:57:43 jackmitchell: yes; it will be quite nice Jan 22 15:58:01 jackmitchell: why you cannot make it backwards compatible with previous kernel? Jan 22 15:58:10 jackmitchell: iio would be nice to have as well Jan 22 15:58:21 otavio: pwm subsystem support was only introduced with 3.12 Jan 22 15:58:47 otavio: iio is something I've considored, it will take a bit more thinking though as the implementations can differ a bit from what I've seen Jan 22 15:59:43 otavio: http://lwn.net/Articles/553755/ Jan 22 16:03:45 jackmitchell: cool; easy to backport, it seems Jan 22 16:13:54 just started using yocto for "BD SL i.MX6" Jan 22 16:15:31 got a working rootfs and kernel using yocto dora and fsl-community-bsp, now I am wondering how to build my application that requires stuff like ALSA, GStreamer and so on - I am searching the cross-gcc on the one hand and some pkgconfig files to be used for cross compilation on the other hand Jan 22 16:16:03 as far as I got cross gcc was build by yocto in build/tmp/sysroots/x86_64-linux/usr/bin/cortexa9hf-vfp-neon-poky-linux-gnueabi ? Jan 22 16:16:21 so I might just export this path and use this as cross compiler? Jan 22 16:16:46 TobSnyder: not really. Jan 22 16:16:49 you have 2 options. Jan 22 16:17:10 1) you create bitbake recipes for your application, and include them in the image, like any other recipes. Jan 22 16:17:42 2) create a 'SDK' out of your yocto build. that will be a 'relocatable' SDK that you can install somewhere on your machine (or on another machine). Jan 22 16:17:56 the SDK will include the sysroot (with the .pc, libs, .h, ...) and the cross compiler. Jan 22 16:18:52 creating a SDK seems to be more reasonable to me and seems to fit my previous work flow Jan 22 16:18:53 for #1 you would typically create your own 'layer' and put your recipes in it. Jan 22 16:19:06 ok, then #2. Jan 22 16:19:26 #1 would be usefull after development is nearly finished for releasing something "complete" Jan 22 16:19:55 well, it's up to you in fact. Jan 22 16:20:03 for #2, you should start by reading this: http://www.yoctoproject.org/docs/current/adt-manual/adt-manual.html Jan 22 16:20:53 in fact, to generate the SDK, the command is " bitbake image -c populate_sdk " Jan 22 16:21:18 it will generate SDK with all the .h, .libs, .pc, ... for all the packages installed in Jan 22 16:24:16 ndec: so no "bitbake adt-installer" ? Jan 22 16:24:36 well, that's not what i use.. so i cannot comment ;-) Jan 22 18:26:15 sgw_: there ? Jan 22 18:26:44 sgw_: I am trying to reproduce the binutils 2.24 issue Jan 22 18:26:48 here is what I did Jan 22 18:27:00 build wireless-tools for qemuppc Jan 22 18:27:03 went fine Jan 22 18:27:21 then cleaned it and rebuild it that went fine too it used sstate Jan 22 18:27:39 then I cleaned sstate and rebuilt and that went fine too Jan 22 18:28:00 cleanall;rebuild also went fine Jan 22 18:28:16 how can I reproduce it ? Jan 22 18:28:38 do I have to punt out complete tmp/ Jan 22 18:30:52 khem, honestly not sure, it's been a while since I built with that on the Auto builder, which does clean tmp builds but uses sstate to speed things up Jan 22 18:34:29 sgw_: ok Jan 22 18:34:43 sgw_: if ab has cycles can we retry Jan 22 18:34:58 and give me access to one of machines if we can reproduce it Jan 22 18:35:12 I have debian here and archlinux Jan 22 18:36:09 may be just try qemuppc builds if you have such an option in AB that way we can get to verify it faster Jan 22 18:36:45 yeah, after we get M2 rc2 and the 1.4.3 done we should have cycles later Jan 22 19:56:24 howdy challinan Jan 22 19:56:56 hey mranostay how are ya? Jan 22 19:57:42 not too bad **** ENDING LOGGING AT Thu Jan 23 02:59:58 2014