**** BEGIN LOGGING AT Tue Apr 23 02:59:58 2013 Apr 23 06:19:18 hi, in the Yocto JF default build have only "mkfs.cramfs mkfs mkfs.bfs", how can I add "mkfs.ext2" or "mkfs.ext3"? Apr 23 06:20:05 e2fsprogs or util-linux-mkfs ? Apr 23 08:33:09 otavio: Hi! Are these http://patchwork.openembedded.org/project/meta-freescale/list/ the patches you are mentioning here https://lists.yoctoproject.org/pipermail/meta-freescale/2013-April/002371.html ? Apr 23 08:34:58 I've tried them and also tried to "bitbake -c clean xserver-xorg xf86-video-imxfb-vivante gpu-viv-bin-mx6q xf86-dri-vivante" but the rebuilt image still has the same problem, not going past "test Initializing EXA"... Apr 23 11:14:34 Hi, does yocto gather some build statistics like code lines etc? Apr 23 11:27:21 panda84kde: I been using this without issues Apr 23 11:27:30 panda84kde: and here it goes over EXA Apr 23 11:27:41 panda84kde: maybe you need to upgrade your u-boot Apr 23 11:28:26 otavio: thank you. Don't really know what could be wrong then. Do you suggest a clean build? Apr 23 11:28:39 panda84kde: danny or master? Apr 23 11:28:47 master + patches Apr 23 11:30:13 do you suggest using danny? Apr 23 12:07:30 hi, i don't understand the kernel defconfig strutur ind meta-fsl-arm.. there is a defconfig in "recipes-kernel/linux/linux-imx-3.0.35/mx6" but this one doesn't match to the defconfig with which the system builds.. where does this happens? Please help me. I am confused.. Regards matt Apr 23 12:53:51 anyone please can explain me this phenomen? How it works? Apr 23 13:22:45 otavio: Have you got any suggestion on how I can debug it more? Apr 23 13:35:28 Does exynos have its own yocto meta layer somewhere? Are any other Cortex A15 SoC's working with yocto? Apr 23 14:05:00 panda84kde: I did merge the pending patches Apr 23 14:05:29 panda84kde: I think it'd be great if you could send this to the mailing list with the Xorg log and also copy Eric (from Boundary) Apr 23 14:07:34 otavio: thanks. Are those merged patches v2? I'll surely update everything, build, test, and post on ML (with Eric in copy). Apr 23 14:09:13 I'll rephrase better. Did you merge version 2 of the patches? Apr 23 15:00:12 YPTM: On the clal now Apr 23 15:00:18 call even Apr 23 15:00:29 YPTM: Darren has joined Apr 23 15:00:49 YPTM: Polk is here Apr 23 15:00:51 YPTM: Tom here Apr 23 15:01:02 YPTM: belen joined Apr 23 15:01:02 YPTM: Welcome to the technical team meeting, please let me know who's on the bridge. Thanks! Apr 23 15:01:02 YPTM: Saul here Apr 23 15:01:09 YPTM: Corneliu joined Apr 23 15:01:14 YPTM: Mark is here... Apr 23 15:01:19 YPTM: Nitin joined the call Apr 23 15:01:21 YPTM: Richard is here Apr 23 15:01:22 YPTM: Beth dialing in in a moment. Apr 23 15:01:25 YPTM: Kevin Strasser is here Apr 23 15:01:46 YPTM: ross here Apr 23 15:02:06 YPTM: Scott Rifenbark joined the call Apr 23 15:02:19 YPTM: Laurentiu Palcu joined Apr 23 15:02:22 YPTM: Bruce Ashfield on the call. Apr 23 15:02:35 alex d is in Apr 23 15:03:10 YPTM: Björn Stenberg joined the call, on the train :) Apr 23 15:03:29 YPTM: Any opens? Apr 23 15:03:51 * mihai joined Apr 23 15:04:11 Joined YPTM Apr 23 15:04:29 (I'm leaving IRC, still on the call) Apr 23 15:05:59 Latest 1.4 Full Pass report (still a few IDLE, will be ready tomorow) : https://wiki.yoctoproject.org/wiki/1.4_QA_Status Apr 23 15:07:01 YPTM: jzhang on the call Apr 23 15:08:48 pidge: i thought the new AB code was faster, what's your problem? :) Apr 23 15:08:50 * rburton runs Apr 23 15:09:09 rburton: you need to duck as well Apr 23 15:09:19 duck and roll Apr 23 15:09:38 I thought it was bob and weave Apr 23 15:09:43 * scottrif good idea on the single page summarizing releases Apr 23 15:09:53 * sgw_ agrees Apr 23 15:10:11 I'd like to also have the "old" unsupported releases listed in the same place.. Apr 23 15:10:18 with either contact of obselance links Apr 23 15:13:04 http://marcin.juszkiewicz.com.pl/2013/04/23/time-to-visit-uk-again/ Apr 23 15:13:18 * hrw out Apr 23 15:14:41 I had proposed a page for listing releases along with links to Features, Status and QA pages, adding the stable info here would be good also. Apr 23 15:14:45 https://wiki.yoctoproject.org/wiki/StableReleases/1.1.1 Apr 23 15:14:58 https://wiki.yoctoproject.org/wiki/Releases ? Apr 23 15:15:05 Does not list stable info Apr 23 15:15:28 sgw_: that's the place to extend it though Apr 23 15:15:49 rburton: sure. Apr 23 15:17:44 https://wiki.yoctoproject.org/wiki/Releases Apr 23 15:19:11 rburton: It is. Why what's the issue? Apr 23 15:19:20 * scottrif agrees Apr 23 15:19:32 pidge: just commenting on you not wanting to do 1.4.1 and 1.3.2 at the same time Apr 23 15:19:49 rburton: Oh. autobuilder is. I'm not :P Apr 23 15:20:33 https://wiki.yoctoproject.org/wiki/Planning Apr 23 15:21:41 yes Apr 23 15:25:02 good here Apr 23 15:34:49 pidge: ok.. may... Apr 23 15:36:19 fray: Yes, I'm out 1-7th Apr 23 15:37:02 * pidge is going to crawl up into a ball and sleep then hop on the motorcycle and go someplace without phone/irc/internet. Apr 23 15:37:30 http://packages.yoctoproject.org/ Apr 23 15:38:53 https://www.yoctodev.org/charts/ Apr 23 15:48:51 halstead: I like the graph! :) Apr 23 15:49:45 RP, Thanks. I'm adding fields so you can set the date range as well. Apr 23 15:50:17 dvhart: FILES_${PN}-rtl-license_append_pn-linux-firmware = " /lib/firmware/LICENCE.rtlwifi_firmware.txt" into the machine.conf files which use linux-firmware Apr 23 15:50:52 RP, ok, that is the same fix I would put in a bbappend, but the bbappend would fix it everywhere. Apr 23 15:51:01 So what would the rationale be for doing it per machine? Apr 23 15:51:32 just minimal impact? Apr 23 15:51:47 dvhart: I was worrying about potential issues when we come to 1.4.1 when the fix is merged Apr 23 15:52:05 dvhart: Its probably irrelevant though so ignore me Apr 23 15:52:06 at that point the bbappend would be a no-op Apr 23 15:52:14 * RP is trying to do way too much at once :( Apr 23 15:52:23 RP, tis the nature of the beast Apr 23 15:52:36 * dvhart goes to test fix in meta-intel Apr 23 15:53:12 RP: bugs filed: 4359 and 4358 (I think I triaged them after I filed them) Apr 23 15:53:34 Here's yocti to respond to the bugs? Apr 23 15:53:41 Where's yocti? Apr 23 15:54:27 sgw_: that would explain why I didn't see them Apr 23 15:54:42 and I did not respond to the emails, so my bad, sorry Apr 23 15:55:58 halstead: Is the code somewhere I can look at/play with? Apr 23 15:57:26 RP, Sure. There is the python/SQL code the works on the bugzilla database and then JS+HTML for the display. I need to gather it all up. Apr 23 15:58:45 halstead: Its not urgent but I am interested. Part of the reason for doing this is to see if we can then improve the metrics which means experimenting with the data/charts a bit Apr 23 18:45:44 wb darknighte Apr 23 18:45:55 mranostay: hullo Apr 23 18:46:09 i demand an e Apr 23 18:46:19 mranostaye... Apr 23 18:46:32 seems a bit more olde schoole, but okaye... Apr 23 18:46:51 * darknighte doffs his cap to mranostaye Apr 23 18:47:09 Hi folks. Suppose I have a recipe that building a shared lib. What package suffix should that file go into? Apr 23 18:47:17 ${PN}-dev? Apr 23 18:47:59 -dev is for headers iirc Apr 23 18:48:13 I tried just putting it with my ${PN} package, but I get QA issues with GNU_HASH in elf binary Apr 23 18:49:13 Looking at bitbake.conf, it looks like they ought to go in package ${PN} Apr 23 18:49:39 but then, do I need to suppress this QA issue? Is that the right way to solve the problem? Apr 23 18:50:30 mranostay: yeah, that was my understanding too Apr 23 18:51:14 Garibaldi: mranostay: usally it's for headers and the like. I've seen some packages combine -dbg and -dev together, so it can also include some libraries. Apr 23 18:51:53 Garibaldi: depends on what you need to do. It sounds like the intent is to provide the library itself? Apr 23 18:52:20 yeah, I have a package that includes a set of binaries that depend on a lib Apr 23 18:52:32 I'd like to just include the lib as part of the package Apr 23 18:53:10 I added INSANE_SKIP_${PN} = "ldflags" and it suppressed the error I was getting, but that doesn't feel "right" Apr 23 18:54:19 heh. I haven't used INSANE_SKIP before... Apr 23 18:54:28 sounds like you just want to add it to the FILES var? Apr 23 18:54:50 yeah, it's in there, it's some QA error about GNU_HASH in the file Apr 23 18:57:20 Garibaldi: hmmm, I must admit that I generally ignore those. (shame on me, I know) Apr 23 18:58:02 how do make it not an error? :-) Apr 23 18:58:22 ERROR: QA Issue: No GNU_HASH in the elf binary Apr 23 18:58:48 Garibaldi: here's a thread that deals with the same... Apr 23 18:58:49 https://lists.yoctoproject.org/pipermail/yocto/2012-August/011106.html Apr 23 18:59:45 thanks, I went though that -- that's where I got the INSANE_SKIP_${PN} = "ldflags" business Apr 23 19:00:09 I guess I'll just go with that until I learn otherwise :-) Apr 23 19:00:10 thanks again Apr 23 19:00:33 Garibaldi: moving the binary into -dev or -dbg or whatever won't suppress the QA warning...or at least, will cause a different one Apr 23 19:00:36 Garibaldi: sorry, I haven't really run into it much and when I have it's been a warning, not an error. Apr 23 19:00:44 no problem Apr 23 19:02:04 you got me curious now though… I'll keep an eye out for a solution... Apr 23 19:02:18 yeah, let me know if you hear anything -- I'll do the same Apr 23 19:02:23 Garibaldi: I don't remember INSANE_SKIP specifically, but I do know the correct approach disables the QA check, which sure sounds like what INSANE_SKIP does Apr 23 19:03:08 evanp: ah, good :-) Apr 23 19:06:42 Garibaldi: evanp: I took another peek at the code and I sounds like that is the correct mechanism. As with evanp, I seem to recall you have to disable the QA check... Apr 23 19:09:55 I found a solution that I like Apr 23 19:10:07 I did a PACKAGES += "${PN}-lib Apr 23 19:10:45 put my .so in there, did INSANE_SKIP_${PN}-lib = "ldflags", and RDEPENDS_${PN} += "${PN}-lib" Apr 23 19:11:04 I wanted to limit the scope of that INSANE_SKIP as much as possible Apr 23 19:11:48 (i.e., I wanted the QA check for my binaries in ${PN}, but not for the .so) Apr 23 19:13:25 seems pretty reasonable. Apr 23 21:21:39 hello, what the different between openembedded-core, meta-openembedded and poky? Apr 23 21:51:56 I wonder if the problem was at ftp://ftp.astron.com/ or with our network? Apr 23 21:54:57 alex_kag, the READMEs at https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/README and http://cgit.openembedded.org/openembedded-core/tree/README start to explain. Apr 23 23:14:03 i'm having trouble with meta-selinux: it fails to fetch one of the patches for findutils. is it possible to download the patches myself and get bitbake to recognize i've done that? Apr 24 00:42:42 hi , where can I find document for what output files created by "bitbake linux-yocto -c compile" , "bitbake linux-yocto -c deploy" , "bitbake linux-yocto " Apr 24 00:44:16 and after these, if I want to create new .hddimg image file, should I use "bitbake core-image-basic"? or can I do other faster way? **** ENDING LOGGING AT Wed Apr 24 02:59:58 2013