**** BEGIN LOGGING AT Mon Nov 12 02:59:58 2012 Nov 12 06:16:21 yotci 1 Nov 12 06:16:27 bug #1 Nov 12 06:16:43 arg Nov 12 06:16:46 wrong channel Nov 12 06:54:04 does anyone know anything about device nodes creation? Nov 12 07:04:52 mknod? Nov 12 07:12:39 dm8tbr: yeah, but where do I put it in? Nov 12 07:13:54 nothing I try to create this way underneath /dev in the package appears in the resulting rootfs Nov 12 07:14:42 I don't know about that, you only asked about /anything/ Nov 12 07:14:53 dm8tbr: ok, thanks anyway :) Nov 12 07:15:21 the question still remains though... Nov 12 08:28:00 good morning Nov 12 09:14:13 morning all Nov 12 10:19:18 morning all Nov 12 10:22:08 bluelightning: morning, did you see the update patch I sent for Hiawatha Webserver last week? Nov 12 10:22:27 jackmitchell: I did... I'll merge it now Nov 12 10:22:38 (was at ELCE last week) Nov 12 10:22:48 bluelightning: thanks, I know ELC-E had everyone busy! Nov 12 10:24:03 good morning Nov 12 10:24:43 gm bluelightning, florian, all Nov 12 10:24:53 hi florian, mckoan Nov 12 10:32:52 hi all Nov 12 10:34:09 hey pb_ Nov 12 10:36:18 hi pb_ Nov 12 11:16:49 hi bluelightning Nov 12 12:50:38 pb_: you around? Nov 12 13:53:44 ant_work: hi Nov 12 14:24:26 hello pb_, I have same oops and panic with 3.3.8, 3.4.11-yocto and 3.6.6 kernels :/ Nov 12 14:26:22 just to be sure, the last instruction is listed in PC/LR isnt't? Nov 12 14:53:27 ant_work: yes, usually Nov 12 15:08:31 hello there Nov 12 15:11:01 pb_: I see, all kernels are failing in a similar manner and in PC is always __gpio_get_value Nov 12 15:11:22 I *guess* the gpiolib rework broke pxa255 Nov 12 15:12:24 hi, has anyone here tested meta-toolchain-qte with danny ? Nov 12 15:13:09 sounds like it, yeah. Nov 12 15:18:49 I've been delving into oe recipes and bitbake code. With the hello world project I mentioned yesterday, I kind of got how bitbake works. However, there are a few points that I couldn't understand. First one is staging area, and the second one is how image and rootfs is formed. Accordingly to the documentation, staging area is a shared area in which the libraries and header files are kept while a package is being Nov 12 15:18:51 built in the case it needs. It didn't make much sense Nov 12 15:23:05 I couldn't clearly follow the recipes and bbclass files for building an image. I know that when the package has been built, it is installed into ${D}. In which stage, then, are these installed files copied to deploy dir, and the image is formed (tar.gz, cpio, ext3 etc) ? Nov 12 15:27:11 no, your understanding is incorrect. it isn't that a package is instaleld into ${D} when it's built Nov 12 15:27:14 eren: if a program being compiled needs to link against a library, it needs the headers and the library file for that library; those will have previously been placed in the sysroot (previously referred to as staging) assuming the DEPENDS have been set correctly Nov 12 15:27:23 it's that the do_install task run for a recipe installs files to ${D}. other tasks do more with that Nov 12 15:31:09 eren: almost all of the image building logic is actually defined in the metadata rather than in bitbake Nov 12 15:31:22 kergoth: ok, do_install install files into ${D} after do_compile, I was referring to that Nov 12 15:31:54 eren: first packages are created for each recipe (do_package and do_package_write(_rpm|_ipk|_deb)) Nov 12 15:32:51 eren: then during do_rootfs for an image the packages in IMAGE_INSTALL are installed into a directory, then that directory is turned into the image file and put into the deploy dir Nov 12 15:35:21 bluelightning is an OE living encyclopedia Nov 12 15:35:44 bluelightning: ok, I was confused on how the packages in IMAGE_INSTALL are installed into a directory (I guess it's a deploy dir). In image.bb recipe, I see that ${IMAGE_INSTALL} is just passed to DEPENDS = with some extra such as ${LINGUAS_INSTALL} Nov 12 15:36:21 eren: the packages in IMAGE_INSTALL are installed to ${WORKDIR}/rootfs, not the deploy dir Nov 12 15:36:33 (WORKDIR for the image recipe that is) Nov 12 15:36:57 the deploy dir on the other hand being tmp/deploy/images Nov 12 15:37:09 hi, while testing meta-toolchain-qte generated for armv7 with danny, it seems the c++ headers are not found during compilation : http://pastebin.com/iF3aDR1G any idea of what could be wrong there ? Nov 12 15:38:01 bluelightning: ok, what confuses me is that in image.bbclass, IMAGE_INSTALL variable is passed to RDEPENDS Nov 12 15:38:27 sorry if that was answered previously ... my irssi session was killed as the server was migrating from LTS 10.04 to LTS 12.04 :-( Nov 12 15:38:43 ericben: don't know if this is related but it sounds similar: https://bugzilla.yoctoproject.org/show_bug.cgi?id=1231 Nov 12 15:38:50 (from some time ago) Nov 12 15:39:40 ok, lets start from scratch. Assume that A.bb depends on B, C. When A is being processed by bitbake, bitbake first processes B, C Nov 12 15:39:45 eren: that's just to ensure that all of the packages get built before do_rootfs is executed Nov 12 15:40:25 eren: if you really want to understand how bitbake works you need to be thinking at the task level, not the recipe level Nov 12 15:41:15 bluelightning: thanks, that's as similar problem Nov 12 15:41:22 yes I really understand how bitbake works. Thinking in recipe level is caused by my background in packaging, I guess :) Nov 12 15:41:53 bluelightning: actually I'm using qt 4.8.3 but I'm not sure the qt versions makes a big difference here, will try a build with 4.8.1 Nov 12 15:42:18 and qt apps are properly compilated inside oe, only the sdk usage is broken Nov 12 15:43:03 bluelightning: ok, we have tasks defined in base.bbclass, such as do_fetch, do_unpack, do_patch, do_compile, do_install, do_populate_sysroot and do_build, respectively. Right? Nov 12 15:43:15 right Nov 12 15:43:18 there are a few for cleananing but I'm not mentioning them Nov 12 15:44:03 do_install just does "make DESTDIR=${D} install" for autotools, and there are other different routes defined in other classes. Nov 12 15:44:17 after the recipe has been installed to ${D} Nov 12 15:44:23 what does do_populate_sysroot do? Nov 12 15:45:12 I guess it's defined in staging.bbclass Nov 12 15:46:45 * eren s/I really understand/I really want to understand/g btw, sorry for mistyping Nov 12 15:47:52 eren: do_populate_sysroot effectively copies files from ${D} to ${STAGING_DIR} (tmp/sysroots/...) Nov 12 15:48:05 bluelightning: ok the issue is which sdk relocation, if I install the sdk in /usr/local everything works fine. So the problem is different to the one in the bugreport Nov 12 15:48:22 bluelightning: I'll create a bug report for this on yocto's bugzilla Nov 12 15:48:22 hmm, sysroot_stage_all() is called and it gives ${D} and ${SYSROOT_DESTDIR} to sysroot_stage_dirs(), which copies files to sysroot Nov 12 15:48:40 then, ${D} variable is recipe specific and it's set by bitbake? Nov 12 15:48:50 s/which sdk/with sdk/g Nov 12 15:49:18 eren: read bitbake.conf. Nov 12 15:49:24 how do I make a specific package rebuild each time I create an image? Nov 12 15:49:30 kergoth: ok, looking Nov 12 15:51:54 kergoth: right, everything seems to start from "PN = "${@bb.parse.BBHandler.vars_from_file(d.getVar('FILE'),d)[0] or 'defaultpkgname'}" Nov 12 15:52:00 btw the new yocto website has a nice look ;) Nov 12 15:52:17 or other way around, what do I need to put in "do_rootfs_append()" in the image package so that it would clean up a specific package (in order for it to get rebuilt next time I create an image) Nov 12 15:52:34 PR and PF are set accordingly Nov 12 15:53:14 angri: I don't think that would be the right way to do that Nov 12 15:53:26 bluelightning: ok, and what is the one? Nov 12 15:53:36 angri: you may wish to generate the dynamic contents of the package in a rootfs postprocessing function instead Nov 12 15:54:16 bluelightning: yeah, that might be it... let me look Nov 12 15:54:37 angri: if you really do want the contents packaged you should set it up so that the signature changes on each invocation, i.e. the dynamic part goes into a variable value and something within the recipe depends on that variable value Nov 12 15:54:53 ok, after do_install, all the recipe's files are copied into STAGING_DIR, namely sysrootfs Nov 12 15:55:06 angri: this sort of happens with base-files, every time DATE changes it gets rebuit Nov 12 15:55:44 now, there comes do_build task after do_populate_sysroot Nov 12 15:55:51 it's left blank in base.bbclass Nov 12 15:56:41 eren: do_build is the default task that is there to have dependencies such that the "right" thing gets done for any particular target you request to be built Nov 12 15:56:48 bluelightning: couldn't find any reference to DATE in base-files.bb :( Nov 12 15:57:41 angri: by default in Poky at least it comes in via DISTRO_VERSION which is referred to in do_install_basefilesissue Nov 12 15:58:49 angri: in any case, usually it is enough just to refer to the variable within a function as is done there Nov 12 15:59:31 ericben: Have you seen this message "QWSLock::up(): Invalid argument, QWSLock::down(): Invalid argument" when running example/demo applications built with Qt? I am running Qt 4.8.0 and I never saw this message when I was using Qt 4.7.2 Nov 12 16:01:52 bluelightning: I just tried to refer to ${DATETIME} in do_install() but it didn't help - the package doesn't get rebuilt even when I bitbake it spefically Nov 12 16:02:14 fcooper: I don't see this message with qt-embedded 4.8.3 and an helloworld Nov 12 16:02:36 bluelightning: could using of nostamp flag help? Nov 12 16:03:03 angri: I'm not sure if nostamp would be appropriate here Nov 12 16:03:04 bluelightning: If I'm not wrong, it seems that all the files that are installed with do_install go to staging area (sysrootfs). The task of building an image may also be gzipping the staging area? Nov 12 16:03:08 bluelightning: https://bugzilla.yoctoproject.org/show_bug.cgi?id=3409 hope that's clear Nov 12 16:03:43 eren: it's not that simple in either case Nov 12 16:04:17 bluelightning: as far as I see, ipk or deb related functions are called, which then write their configurations, create their directories Nov 12 16:04:44 bluelightning: could using of nostamp flag help? Nov 12 16:04:52 oh, sorry for double-posting Nov 12 16:04:54 angri: it shouldn't be needed Nov 12 16:05:02 angri: the signature should change Nov 12 16:05:37 bluelightning: I'm still confused on when (at which task) ipk or deb packages are created, and its relation with image creation (image.bbclass) Nov 12 16:05:52 ericben: Can you try running usr/bin/qtopia/demos/deform? Nov 12 16:06:20 fcooper: I'll try to install the example Nov 12 16:06:27 eren: do_package_ipk for ipk, do_package_rpm for rpm, do_package_deb for deb Nov 12 16:06:34 eren: read package_ipk.bbclass, etc Nov 12 16:07:09 eren: these create packages for each directory in ${WORKDIR}/packages-split Nov 12 16:07:21 (effectively) Nov 12 16:09:08 angri: if it is a date/time stamp you're trying to implement, it's probably best done in a rootfs postprocessing function though Nov 12 16:09:44 bluelightning: yeah, probably... how do I add the rootfs postprocessing function? Nov 12 16:09:50 is there a known issue with hicolor-icon-theme leading to : Failed to create file '/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache.BIUVNW': No such file or directory /var/lib/opkg/info/hicolor-icon-theme.postinst: line 13: gtk-update-icon-cache: not found ? Nov 12 16:10:35 bluelightning: I guess do_rootfs_append() would not work Nov 12 16:10:38 or would it? Nov 12 16:12:20 fcooper: # /usr/bin/qtopia/demos/deform/deform -qws -> no log on stdout Nov 12 16:12:24 angri: define a shell function in your image recipe and then add it to the end of ROOTFS_POSTPROCESS_COMMAND Nov 12 16:12:44 fcooper: which version of OE are you using ? Nov 12 16:12:52 angri: see the functions at the end of image.bbclass and the core-image-minimal recipe for examples Nov 12 16:12:59 bluelightning: ok, I'll try that, thanks! Nov 12 16:13:00 ericben: oe-core denzil Nov 12 16:13:17 fcooper: ok here thats danny Nov 12 16:14:19 fcooper: time to upgrade ;-) switching a project from denzil to danny qt 4.7 to 4.8 was far much easier than what I expected. Nov 12 16:17:35 ericben: I am currently using 4.8.0 but I will try 4.8.3 to see if that fixes the issue. But your right other than this weird message the switch was alot easier than I expected. Nov 12 16:18:45 oh here it is. package.bbclass defines do_package after do_install, and package_write before do_build after do_package Nov 12 16:18:48 hmmm Nov 12 16:19:00 it's beginning to makes sense Nov 12 16:21:59 ericben: R you using the X11 version of Qt or the directb version? Nov 12 16:27:50 fcooper: none the qws one? Nov 12 16:30:46 ericben: Ok thats what I am using. I need to do some more investigating. Thanks for trying out those demos Nov 12 16:36:47 hey. how can i override a function defined in a base package from a bbappend recipe? i want to totally obliterate pkg_postinst, and set it anew from my bbappend Nov 12 16:45:13 bluelightning: I used rootfs postprocess command and it worked, thank you! Nov 12 16:45:28 angri: np Nov 12 16:45:34 bluelightning: do you by chance know what is the right way to create /dev/net/tun ? Nov 12 16:45:58 bluelightning: well, although packaging tasks are defined in package.bbclass, I couldn't find a reference which makes use of package.bbclass (inherit package) so that the tasks are added for processing Nov 12 16:46:10 angri: I don't I'm afraid, no... Nov 12 16:47:36 angri: although surely it must be there within build-appliance-image or you wouldn't be able to use the runqemu script within it.. Nov 12 16:49:08 eren: it gets brought in via PACKAGE_CLASSES I think Nov 12 16:50:22 bluelightning: ok, I take it granted then Nov 12 16:52:21 I guess it's now more clear. after do_populate_sysroot, related packaging tasks are run. They create the packages using ipk, deb or tar.gz and stage them into deploy dir Nov 12 17:00:54 how do i get the autotools class to specify build/host/target the way they are in gcc? (where my current system is build and host, and the crosscopmile target is target) Nov 12 17:00:58 while creating the image, sources.list file is written in staging dir (sysroots) and gets exported via APT_CONFIG. Later, apt-get update is called and bunch of packages are installed via apt into image dir Nov 12 17:01:26 bluelightning: however, shouldn't apt be called within ${IMAGE_ROOTFS} ? Nov 12 17:02:08 eren: I think it is... Nov 12 17:02:17 I couldn't see any reference to "export PWD=${IMAGE_ROOTFS}" or cd Nov 12 17:05:41 eren: maybe it's not necessary since the root path is specified in the configuration Nov 12 17:06:22 bluelightning: to summerize, bitbake handles a number of tasks which produces ipk or deb archive for each bb recipe at the end. When all the tasks finis, there comes to task defined in image.bbclass (rootfs before do_build). In do_rootfs, deb or ipk related rootfs creation routes are called. These routines basically sets up apt/ipk configuraton in staging dir, exports the config and start isntalling packages Nov 12 17:06:37 s/finis/finish Nov 12 17:07:08 the order in which bitbake runs tasks would differ, but I guess the logic is more or less the same as I said? Nov 12 17:07:20 s/routes/routines Nov 12 17:08:15 if you say OE rather than bitbake and add rpm to the list of package formats, that's a very high level distillation of what happens yes Nov 12 17:10:27 bluelightning: oh okkie, I'm glad that I got the big picture, at least Nov 12 17:10:41 bluelightning: thank you for all your help! Nov 12 17:10:43 kergoth: you too :) Nov 12 17:13:12 bluelightning: I'm thinking of writing a documentation about what I've learned. Understanding the OE is a bit hard for newcomers. If it wasn't for #oe, It would really long time to understand it Nov 12 17:13:26 should I post it to oe-devel for revision? Nov 12 17:14:32 s/it would/it would take/ Nov 12 17:22:07 eren: I guess so, but it may overlap with existing documentation - did you have a look at the Yocto Project documentation at all? Nov 12 17:27:57 stand alone oe docs are good Nov 12 17:28:32 Crofton|work: which docs do you mean? Nov 12 17:59:18 bluelightning: yes, I've checked yocto and openembedded documentation and haven't seen a "big picture" part Nov 12 17:59:51 eren: the quick start guide has a diagram at least Nov 12 18:01:48 bluelightning: yes, but it does not delve into bbclass files, how tasks are defined, which code gets run while preparing an image and deb/ipk/rpm files Nov 12 18:03:40 bluelightning: I had to search a lot to find bitbake "hello world" project, which helped a lot to understand the basic bitbake functionality Nov 12 18:04:02 right, that is very new though (last month or so) Nov 12 18:18:08 eren: i'd be very curious to hear if you have any thoughts on how best to structure a document covering the big picture. it's a common complaint, that it's missing from the documentation. some folks come in and follow tutorials and use it for years and never actually wrap their heads around the underlying concepts and structure, i suspect Nov 12 18:18:13 heh Nov 12 18:19:12 don't get me wrong, I certainly wouldn't want to dismiss the idea of documenting this better Nov 12 18:19:45 there have been some other attempts (from slightly different angles) Nov 12 18:19:48 what we have is good, certainly, and has improved quite a bit over the years Nov 12 18:19:49 e.g. http://lists.linuxtogo.org/pipermail/bitbake-devel/2011-December/001571.html Nov 12 18:19:51 * kergoth nods Nov 12 18:20:07 it seems to be a hard thing to express clearly Nov 12 18:21:03 also: http://www.aosabook.org/en/yocto.html Nov 12 18:21:52 kergoth: you're even mentioned by name in there :) Nov 12 18:22:49 :) Nov 12 18:23:00 good point, i forgot about that. beth did a good job there Nov 12 18:23:11 * kergoth gets food Nov 12 18:25:16 indeed she did Nov 12 18:30:07 i keep wanting to write something up about this stuff from a historical perspective, looking at the original requirements and design. see if that perspective helps people understand why it is the way it is Nov 12 18:30:11 oh well, one of these days Nov 12 18:32:43 kergoth: I know I would certainly be interested to read that if you do get around to it... Nov 12 18:56:43 kergoth: I would definitely appreciate the historical perspective Nov 12 18:57:36 bluelightning: I did not know "How bitbake works" e-mail, btw. This seems to be a good draft. I was referring to this hello world project: http://www.mail-archive.com/yocto@yoctoproject.org/msg09379.html Nov 12 19:04:23 bluelightning, I mean that stand alone oe docs would be a good thing Nov 12 19:04:24 kergoth: I would write my thoughts on it, at least how I understand it, and my mental representation :) Nov 12 19:05:11 the idea of adding a task with a relation to other tasks in a recipe is new to me because I have a regular packaging background Nov 12 19:06:28 + the organization of bbclass files are a bit hard to grasp Nov 12 19:37:41 re **** ENDING LOGGING AT Tue Nov 13 02:59:57 2012