**** BEGIN LOGGING AT Tue Jul 08 02:59:59 2014 Jul 08 03:55:56 trying to test Hongxu's perl 5.20.0 patch... but nothing provides "perl-ptest" Jul 08 03:56:02 what am I missing? Jul 08 05:19:17 hi there, In the Quick Start and in the Required Packages section of the References it is not mentioned that pysqlite is needed. But my build stops with the error " ImportError: No module named pysqlite2 " Jul 08 05:23:14 muprt, It should probably be listed that you need either python-sqlite (for import sqlite3) or pysqlite2. Jul 08 05:25:07 muprt, though, sqlite3 should likely be a part of python standard library... Jul 08 05:25:29 At least that's what it look like when I'm looking at my debian box Jul 08 05:26:16 I am looking at http://www.yoctoproject.org/docs/1.6.1/ref-manual/ref-manual.html#required-packages-for-the-host-development-system right now ... ahh, okay then it is not compiled into builtin python ... Jul 08 05:30:32 No, sqlite3 is needed for bitbake to run properly (well, at least for the prserv part of bitbake, as well as some part for persistant storage). Jul 08 05:36:04 thanks Jul 08 05:36:07 bye Jul 08 10:59:37 hey guys I have a question, when i build yocto for my beaglebone on ubuntu 12.04 i get an error when I add IMAGE_FSTYPES = "tar.bzw2 sdcard" to the local.conf, is there a problem with the sdcard format ? or spelling mistake ? Jul 08 11:02:02 I cannot find anything about these sdcard ready *.sdcard images in the project documentation but my first attempts with th build appliance added such Lines via HOB to the local conf so I thought it would be okay if i use it by myself manually Jul 08 11:03:29 tar.bzw2 seems a typo Jul 08 11:04:07 oh sorry yes Jul 08 11:04:21 tar.bz2 was a typo by my side Jul 08 11:04:44 but no matter what I do it is not possible for me to get a *.sdcard file out of the bitbake process Jul 08 11:05:35 motzer: yes, thats not supported directly. maybe read the documentation for sd card creation in the meta-ti layer Jul 08 11:05:47 motzer: i think they have something like mkcard.sh or such. Jul 08 11:06:21 okay sounds good I will check this Jul 08 11:07:14 I think Freescale layers are using that Jul 08 11:07:39 but in the end, its always... check the docs ;) Jul 08 11:08:05 yes I will check them Jul 08 11:08:10 yes, IMAGE_CMD_sdcard () { Jul 08 11:08:33 meta-fsl-arm Jul 08 11:09:18 okay i am new to this stuff meta-fsl-arm is a layer right ? and in this layer the function for the sdcard image build is included ? Jul 08 11:09:53 so I just add this layer to my bblayers.conf and it I can use this function Jul 08 11:10:01 erm... no. Jul 08 11:10:17 :/ okay Jul 08 11:10:26 some fsl-specific command will get you nowhere on a BBB Jul 08 11:10:50 okay I understand Jul 08 11:10:52 hence, better forget that (except for inspiration), and really have a look at what is documented for meta-ti Jul 08 11:11:42 ok Jul 08 11:12:27 another thing is what is the easiest way to add just one package to my image. For example I build the core-image-minimal successfull and want to add i.e iproute2 package after that ? So that the rebuild does not take hours =) Jul 08 11:15:38 you have to add it to IMAGE_INSTALL ... for a very quick test, it should be possible to do that in the local.conf, but for reproductibility, you should just create you own image and derive it from core-image-minimal Jul 08 11:16:00 i'd suggest just cloning and then modifying core-image-minimal-dev, which is nearly a perfect blueprint. Jul 08 11:16:10 you can also look at https://www.yoctoproject.org/sites/yoctoproject.org/files/ypdd-oct2013-into-hands-on-lab.pdf Jul 08 11:16:18 but IMHO the slides are not in perfect shape Jul 08 11:28:06 Letothe2nd thanks I will try this :) Jul 08 11:29:41 I have a init_ifupdown_1.0.bbappend to append a new interfaces file. In tmp/work/overo.../init_ifupdown/image my interfaces file is found. In tmp/work/arm....../init_ifupdown/image it is another bbappend file present. I believe my image come from arm... why this could append ? Jul 08 11:47:53 Hello, Im looking for a documentation on how to get qemuarm working on armv7a instead of arm926ejs ? Jul 08 11:56:41 hello everybody Jul 08 11:57:14 I am stuck with do_rootfs from a useradd recipe Jul 08 11:57:24 opkg_install_cmd: Cannot install package useradd. Jul 08 11:57:27 that's all I get Jul 08 11:57:49 is there a debugging technique to have a more detailed insight what's going wrong? Jul 08 11:59:26 http://pastebin.com/y3FyUWxJ Jul 08 11:59:50 that's my recipe, but I'd prefer to know a debugging technique Jul 08 12:00:06 bitbake -DDD did not really help Jul 08 13:12:07 root Jul 08 14:26:02 I'm trying to test Hongxu's perl 5.20.0 patch (http://patches.openembedded.org/patch/74513/), but "perl-ptest" has no provider Jul 08 14:26:06 what am I missing? Jul 08 14:59:06 YPTM: Conference Details: Company: WIND RIVER SYS Ready-Access Number: 8007302996/9139049836 Access Code: 2705751 Jul 08 14:59:13 YPTM: Stephen Joined Jul 08 14:59:38 YPTM: Michael on the call. Jul 08 14:59:46 YPTM: Bruce on the call Jul 08 15:00:02 YPTM: Tom Z on the call Jul 08 15:00:43 David C on the call Jul 08 15:00:53 YPTM: Saul is on Jul 08 15:02:15 * Jefro is on YPTM Jul 08 15:02:21 YPTM: Nitin is on the call Jul 08 15:02:53 YPTM: Belen joined Jul 08 15:04:23 * RP joined Jul 08 15:04:35 * RP was stuck on hold music for several minutes for some unknown reason Jul 08 15:04:54 YPTM: Matthew on the call Jul 08 15:04:56 AlexG on the call Jul 08 15:05:05 Doug Boom on the call Jul 08 15:05:23 * zeddii has to drop for a minute but will watch IRC. Jul 08 15:06:07 alex d is on the call Jul 08 15:08:11 moto-timo: have you enabled ptest ? Jul 08 15:12:14 PTEST_ENABLED = "1" and DISTRO_FEATURES_append += "ptest" are in my local.conf Jul 08 15:14:05 moto-timo: we need IMAGE_FEATURES_append = " ptest-pkgs" and DISTRO_FEATURES_append = " ptest" in local.conf Jul 08 15:14:37 YPTM is over. Jul 08 15:16:26 ok, I see that in the YP Ref Man .... sstate changed so now I have a 2 hour build :( Jul 08 15:17:17 YPTM: sorry guys I had a mic problem Jul 08 15:17:23 moto-timo: ok.. :) Jul 08 15:18:24 YPTM: I only wanted to mention again for the people interested that the work in cgl is back on track Jul 08 15:18:52 YPTM: updates and more info can be found here: http://git.enea.com/git/?p=linux/meta-cgl.git;a=summary Jul 08 15:19:37 YPTM: I am waiting for your input Jul 08 15:30:57 tomz: wic imports logging, but I don't think it works as is Jul 08 15:31:36 hrm, so trying to build xfce-taskmanager, which does a git clone with a submodule as part of do_configure. It times out from bitbake, but works if I run the configure command from the devshell. Jul 08 15:32:49 moto-timo: possibly, I haven't used it Jul 08 15:33:14 tomz: ok. I was trying to help Crofton out the other day Jul 08 15:34:20 moto-timo: ok, if it doesn't work, please file a bug so that it gets fixed, if someone needs it Jul 08 15:35:12 tomz: will do. I had a hack that made it work, but I don't think it was a "fix". I'll attach to the bug report. Jul 08 15:35:23 moto-timo, thx Jul 08 15:36:06 tomz: traveling for a couple days, so probably won't file until Friday or the weekend. Jul 08 15:36:16 moto-timo, kk Jul 08 15:40:39 hey tomz Will you be around later? i need to ask more wic questions? Jul 08 15:41:49 Crofton: yeah, I'll be in and out Jul 08 15:41:55 k Jul 08 15:45:36 I have made a file I can dd and ahve an ext4 partitoin, but the vfat partition is "broken" Jul 08 15:45:45 won't mount Jul 08 15:45:51 I suspect it doesn't get formatted Jul 08 15:50:57 tomz, is there a way to get wic to log the commands it runs? Jul 08 15:54:05 Crofton: yeah, the code uses msger.debug() to display the details - you should be able to have that output generated using --debug to wic create Jul 08 15:54:14 hmm Jul 08 15:54:38 at th ewrong machine now, will get back to you after assigning dev days tasks :) Jul 08 16:17:29 I have a init_ifupdown_1.0.bbappend to append a new interfaces file. In tmp/work/overo.../init_ifupdown/image my interfaces file is found. In tmp/work/arm....../init_ifupdown/image it is another bbappend file present. I believe my image come from arm... why this could append ? Jul 08 16:57:07 * moto-timo goes off grid for a couple days Jul 08 17:08:08 quit Jul 08 17:08:10 #exit Jul 08 17:13:18 tomz, shoudl I get one FAT partion with this wks? Jul 08 17:13:19 http://pastebin.com/67yMU0TY Jul 08 17:36:20 Now I read more and more about xfce with Yocto... who is using Yocto as primary workstation? Jul 08 17:37:19 Crofton: it would if there were vfat support for rootfs - currently the only filesystem types supported for rootfs are ext2/3/4 and btrfs. we'd need to add vfat support Jul 08 17:46:32 how do we add vfat? Jul 08 17:46:56 tomz, for arm we need to make vfat partitions on sd cards for most Jul 08 17:46:58 boot Jul 08 17:47:04 boot loaders Jul 08 17:49:54 sorry watching isee-3 twitter Jul 08 17:50:04 thrusters are firing Jul 08 17:50:38 Crofton: likewise for x86 - if you look a the bootimg-pcbios and bootimg-efi plugins, they create fat partitions using mkdosfs and mcopy Jul 08 17:51:06 Crofton: sounds like that needs to be upleveled to some common code Jul 08 17:55:13 intersting, isee-3 uses an USRP Jul 08 18:00:49 tomz, any hints on how to do this? Jul 08 18:00:58 we need to make progress getting wic usable Jul 08 18:07:48 Crofton: I think what needs to be done is to take the dosfs code from the pcbios/efi plugins that I mentioned and use it to implement a new case in /scripts/lib/mic/kickstart/custom_commands/partition.py:prepare_rootfs(). Then of course have those two other plugins reuse the new code. Jul 08 18:08:50 Crofton: I can take a stab at that in the next day or so Jul 08 18:09:19 Crofton: I suppose opening an enhancement bug for that would help to track it Jul 08 18:10:45 Crofton: if you want to open a bug for that, I can assign it to myself and work on it tomorrow or so Jul 08 18:16:12 ok Jul 08 20:09:37 all right, suppose I've got a recipe A which creates two packages, A and B Jul 08 20:09:46 package A RDEPENDS on package B Jul 08 20:10:09 I have observed that package B is installed correctly if A is installed Jul 08 20:10:16 but I cannot run "bitbake B" directly Jul 08 20:10:31 what's up with that? Jul 08 20:11:22 B is probably a package name ${PN}-lib or something similar Jul 08 20:11:42 I wrote the recipe myself Jul 08 20:12:10 bitbake accepts a recipe name / provider, not package name Jul 08 20:12:37 then how come I can bitbake A-native? Jul 08 20:12:45 because A-native is a build time provider Jul 08 20:12:52 dynamically created "recipe" Jul 08 20:12:54 not a binary package name Jul 08 20:12:56 ok Jul 08 20:13:08 so if I were to add B to IMAGE_INSTALL, would it work? Jul 08 20:13:21 yes Jul 08 20:13:27 image_install accepts packages Jul 08 20:13:29 not recipes Jul 08 20:13:29 ok Jul 08 20:13:36 so here's the kicker Jul 08 20:13:40 what if I want a B-native? Jul 08 20:13:45 that wouldn't even make any sense Jul 08 20:13:52 native recipes don't emit packages at all Jul 08 20:14:20 so PACKAGES is the wrong path entirely here, I need a separate recipe file? Jul 08 20:14:49 binary packages get installed on the target Jul 08 20:14:51 thats their purpose Jul 08 20:14:59 natives are temporary, used during the build process Jul 08 20:17:35 what about nativesdk? Jul 08 20:17:56 nativesdk builds packages for installation into the host sysroot of a yocto sdk Jul 08 20:21:04 B operates on files generated by A, and I want to give people the option of running A on their Poky image and then B on their development machine Jul 08 20:21:22 looks like if I don't go the route of separate recipe files, the design of bitbake will just fight me all the way Jul 08 20:21:44 sounds like you want to build A and A-native Jul 08 20:21:53 so then you have target binaries in packages, and the local tools Jul 08 20:22:11 indeed. if B came with A, then A-native will include it Jul 08 20:22:17 okay, I'll drop the formalisms Jul 08 20:22:22 A = bootchart2 Jul 08 20:22:26 B = pybootchartgui Jul 08 20:23:09 if pybootchartgui is present on the Poky image at boot time, then it will automatically be run by bootchart2, and that's very expensive and slow Jul 08 20:23:52 hence why I split them up into separate packages, I wanted to give people the option of not including pybootchartgui Jul 08 20:23:54 so you just install bootchart2 into the image, and let people build bootchart2-native so they can have the local tools Jul 08 20:24:18 fwiw there's already several bootchart clones in oe Jul 08 20:24:30 yep Jul 08 20:24:47 see bug 5893 Jul 08 20:24:48 https://bugzilla.yoctoproject.org/show_bug.cgi?id=5893 Jul 08 20:24:50 Bug https://bugzilla.yoctoproject.org/show_bug.cgi?id=5893 enhancement, Medium, 1.7, max.eliaser, IN PROGRESS IMPLEMENTATION , Rationalise bootchart support Jul 08 20:24:51 Bug 5893: enhancement, Medium, 1.7, max.eliaser, IN PROGRESS IMPLEMENTATION , Rationalise bootchart support Jul 08 20:25:21 lol Jul 08 20:25:45 * rburton maps nick to real name Jul 08 20:26:02 yep, that's me Jul 08 20:27:10 so yeah, split the package as you've done, and if someone wants to generate the images off the target, they build the native tools Jul 08 20:27:25 so I don't mind building a native version of the bootchart daemon that just doesn't get used, that's not a problem Jul 08 20:27:40 you could make the native built not build the daemon to save time Jul 08 20:27:53 ehh, it's a couple of C files, not a big deal Jul 08 20:28:20 and if someone builds bootchart2-native, will pybootchartgui just end up in the native sysroot where they can use it? Jul 08 20:28:53 it will end up in the native sysroot, so they'll have to know where to find it Jul 08 20:29:04 *or* they instal bootchart2 from their distro Jul 08 20:29:17 right Jul 08 20:29:50 dirty secret though, even the target arch pybootchartgui is perfectly useable on my workstation, as it's just a python program anyway Jul 08 20:29:55 shush Jul 08 20:29:56 :) Jul 08 20:30:28 so this is, like, double-pointless Jul 08 20:31:03 i'd be happy with the story for viewing the bootcharts being 1) use pybootchartui on the target, if its capable 2) use pybootchart from your distro 3) build bootchart2-native and use the pybootchart from native sysroot Jul 08 20:31:24 its works now but its probably best to encourage people to use the native form just in case that changes... Jul 08 20:31:32 right Jul 08 20:36:27 I know how to remove the boot up image using menuconfig but is there a way to do it from local.conf or something like that? Jul 08 20:43:22 TRoGd0R: the tux from the kernel? Jul 08 20:44:49 nicest way is to use a boot splash so you don't see the kernel boot at all Jul 08 20:47:19 Yes the tux penguin Jul 08 20:48:01 you can write a config fragment to turn that option off, see the kernel development guide. Jul 08 20:48:22 or install eg psplash so your users don't get an ugly scrolling console Jul 08 20:56:52 So I found this section in the manual "2.3.2. Generating Configuration Files" and it says on step 3 to bitbake linux-yocto -c diffconfig Jul 08 20:57:22 Is that what you were referring to when you said to make a config fragment? Jul 08 20:57:53 not really Jul 08 20:58:03 oh Jul 08 20:58:07 write a something.cfg file that just contains the variables you want to set Jul 08 20:58:15 eg http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-3.14/tree/meta/cfg/kernel-cache/cfg/8250.cfg?h=meta Jul 08 20:58:23 add it to the SRC_URI for your kernel Jul 08 20:58:39 eg with a bbappend Jul 08 20:58:45 OK Jul 08 20:58:53 kernel build notices the fragment, merges it in, builds without tux Jul 08 21:03:47 Where can I find a list of these options? I need the one for disableing the virtual console and the one to remove the tux Jul 08 21:05:37 easiest way is to run menuconfig, find the option, and press help to find its name Jul 08 21:05:51 cool thanks! Jul 08 21:40:20 tomz, https://bugzilla.yoctoproject.org/show_bug.cgi?id=6513 Jul 08 21:40:22 Bug 6513: normal, Undecided, ---, mark.hatle, NEW , wic needs to support creating FAT partitions Jul 08 22:10:55 Crofton: ok, thanks for filing it, I've accepted it and will start working on it Jul 08 23:22:06 /away **** ENDING LOGGING AT Wed Jul 09 02:59:58 2014