**** BEGIN LOGGING AT Fri Dec 12 02:59:59 2014 Dec 12 03:33:47 fishey: oe-core.git $ head meta/recipes-kernel/linux/linux-yocto-dev.bb Dec 12 03:33:47 # This recipe tracks the linux-yocto-dev repository as its upstream source. Dec 12 03:33:47 ^^^ seems to be what you're looking for but I don't work on the kernel recently at least. Dec 12 08:52:09 Hi, In which package can I find the qt modules "QtQuick.Layouts" and "QtQuick.Controls"? Dec 12 08:53:20 Can any one please point me out how tmp/deploy/images directory comes from? Dec 12 09:11:19 #beagle Dec 12 10:15:00 silviof: You have to add an >>PACKAGECONFIG_append_pn-qtbase = " accessibility "<< to your configuration. Dec 12 10:15:08 silviof: thx Dec 12 10:27:22 u-boot not found in the base feeds ,getting this error while bitbake minimal image,can any one tell me what is the reason? Dec 12 10:35:15 Hi, anyone having experience using yocto + eclipse plug-in for "Build system derived toolchain"? I would be pleased to have some assistance:) Dec 12 12:24:07 u-boot not found in the base feeds ,getting this error while bitbake minimal image,can any one tell me what is the reason? Dec 12 12:25:05 ramose_ : did u prepare card correctly with 2 partitions? Dec 12 12:28:26 JustasMika:Sorry didn't get you,I was bitbake minimal image and getting this error Dec 12 12:29:37 aa while trying :) sorry, misread :) are u using stardard setup from yocto or adding your layers? Dec 12 12:30:21 JustaMIka:I have added my own layer Dec 12 12:31:39 what layer consists of? kernel? uboot? Dec 12 12:32:32 JustasMika:Both Dec 12 12:33:36 try to check your recipes then of uboot,what is layer u are adding called? Dec 12 12:38:32 JustasMika:Do you want me to ckeck u-boot recipe file? Dec 12 12:40:07 *check Dec 12 12:40:38 try :) its not easy. what is the layer? Dec 12 12:45:43 JustasMika: I Just checked the error logs :NOTE: Installing the following packages: u-boot udev-extraconf run-postinsts packagegroup-core-boot Dec 12 12:46:12 ERROR: u-boot not found in the base feeds Dec 12 13:01:17 Hi, anyone having experience using yocto + eclipse plug-in for "Build system derived toolchain"? I would be pleased to have some assistance:) Dec 12 13:14:58 ramose__, have u-boot actually been built? Dec 12 13:15:27 AnderD: Yes,its been built Dec 12 13:17:15 AndersD: I can see u-boot.bin /tmp/deploy/images folder. Dec 12 13:18:08 Do you have u-boot in your IMAGE_INSTALL? Dec 12 13:19:16 AndersD: IMAGE_INSTALL of local.conf? Dec 12 13:20:58 There or in your image recipe... Another question, do you find a u-boot package under tmp/deploy//? Dec 12 13:22:10 should there even be one? after all, the main output of u-boot is the bootloader binary - is there an actual u-boot package to go into the image as well? Dec 12 13:24:56 That's correct; that's why I'm wondering if he has u-boot in IMAGE_INSTALL... If he has, he might have some reason, but quite likely no package has been generated. Dec 12 13:26:13 Though, the default seems to be to actually create such a package, and install u-boot under /boot. Though, I've never used that package myself... Dec 12 13:30:45 I guess I've not (knowingly) made use of that either Dec 12 13:30:49 AndersD : Sorry for delayed response,I have IMAGE_INSTALL in my image recipe file Dec 12 13:31:16 the next question is is that supported/working in all of the various u-boot recipes we have floating around in different layers? Dec 12 13:33:14 AndersD: Also I have u-boot package under tmp/deploy/rpm/ Dec 12 13:40:56 ramose__, hm, if you have the an u-boot rpm there, it ought to be found. What's the name of that package? Dec 12 13:41:34 And also, just as bluelightning is asking, do you have a use-case for having u-boot in IMAGE_INSTALL? Dec 12 13:44:02 AndersD: This image recipe alredy has IMAGE_INSTALL defined when I started working on it and add a new machine in conf/machine/machine.conf,so I have to go with it :) Dec 12 13:44:38 *added a new machine in conf/machine/machine.conf,so I have to go with it :) Dec 12 13:45:12 But does it have u-boot in the IMAGE_INSTALL? Dec 12 13:47:05 Is it a public machine and image? If so, which layer? Dec 12 13:54:27 its this http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-ppc layer. Dec 12 13:56:00 <_valle_> Is it possible to use files from a meta-layer in a ROOTFS_POSTPROCESS_COMMAND? Dec 12 13:56:31 <_valle_> The files should not be transfered to the rootfs but I want to use them to create a package Dec 12 13:56:45 Well, for one thing, it looks like it does create an empty u-boot-package, that could explain your issue. Which image is it that add u-boot to IMAGE_INSTALL? Dec 12 14:21:49 AndersD; Image is not public actually Dec 12 14:24:29 AndersD:sorry ,this is the image recipe "https://github.com/kraj/meta-fsl-ppc/blob/master/images/fsl-image-minimal.bb" Dec 12 14:26:32 Ok. Though, using meta-fsl-ppc and assuming that you're using u-boot from that layer, did you actually have a u-boot-rpm in tmp/deploy/rpm/...? I just verified that it should work using standard poky and a beaglebone machine. Dec 12 14:27:56 So if you have a real package it ought to work. Though, I can't really see what files should have been installed in that package though. Dec 12 14:29:15 AndersD : But I'm getting this error while bitbake fsl-image-minimal Dec 12 14:29:47 The u-boot binary et al gets packaged in u-boot-images. though I don't know why you want u-boot binaries installed in the image. Dec 12 14:30:19 AndersD: if I remove u-boot then I get error on " packagegroup-core-boot" not found in the base feeds Dec 12 14:30:29 Yes, the problem is that when you're bitbake fsl-image-minimal, bitbake can't find the u-boot rpm... Dec 12 14:31:56 AndersD: but what is workaround ,shall I call image_install in local.conf Dec 12 14:31:58 ? Dec 12 14:32:07 Ah, that a bigger issue. Previously we, well I, thought that it was a u-boot problem. Dec 12 14:35:19 The question goes again, do you have packagegroup-core-boot-*.rpm in tmp/deploy/rpm/? Dec 12 14:35:45 If you have, it's almost time for a fresh rebuild... Dec 12 14:35:54 let me check but I have u-boot rpm in respected folder Dec 12 14:36:49 sgw_: hi. Would you be able to backport http://git.openembedded.org/openembedded-core/commit/meta/recipes-connectivity/resolvconf?id=853e8d2c7aff6dddc1d555af22f54c4ecef13df1 to dizzy? Dec 12 14:37:06 Though, what are the complete names of the u-boot rpm's? Could you paste them to pastebin? Dec 12 14:41:59 AndersD : Its the name of "packagegroup-core-boot-1.0-r17.machinename.rpm " Dec 12 14:43:13 AndersD: its name for "u-boot-2014.01+fslgit-r0.machinename.rpm" for u-boot Dec 12 14:46:41 AnderD: Names look oK to me as I checked with older machines that has already supported Dec 12 14:47:07 Then I'd guess that bitbakeing core-image-minimal also fails (just to doublecheck) Dec 12 14:47:39 Yes, they seems pretty OK to me. What's your machine name? Dec 12 14:48:15 Just to check if you've got something in the machine name that could break something Dec 12 14:50:06 hi all, I trying to cross compile a program with qtmobility and systeminfo. I succeed my build with LIBS+=/home/kapt/Linux/sources/poky/build/tmp-eglibc/sysroots/q7imx6kpack/usr/lib -lQtSystemInfoE, but not sure this is realy yocto compliant, which path shoud I use instead? Dec 12 14:50:34 AndersD: should it be the same with as defined in MACHINE ?? of local.conf? Dec 12 14:51:33 ramose__, Yes, that's the variable used to keep track of machine. I'm thinking about - and _ et. Dec 12 14:56:04 AndersD:It actually is different and differnce lies in case sensitiveness Dec 12 14:59:33 Ah, that could very well explain it. (Not that I'm an expert on that part). Dec 12 15:00:49 AndersD: Let me just test to see if you really hit the bulls eye :) Dec 12 15:01:02 Even though it likely take you some time, I'd suggest replacing all the capital letters and re-run the test. Dec 12 15:01:34 I do think that you actually hit the bulls eye! Dec 12 15:04:21 AndersD:oK,thanks for your time,will Let you know the result :) Dec 12 15:41:29 AndersD:Thanks again,it worked well . Dec 12 16:04:28 in a recipe, if I use : SRC_URI = "file://test.tar.gz", by default file:// point to a "files" subdir. If I want to use another subdir name (like ${PN}-${PV} subdirectory name) how can I achieve that ? Dec 12 16:38:49 weeb0: it also searches ${BPN}-${PV} by default... http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#var-SRC_URI Dec 12 16:39:34 weeb0: But to extend the search path you use FILESEXTRAPATHS_append (or _prepend): http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#var-FILESEXTRAPATHS Dec 12 16:40:58 gabrbedd: Thank you a lot !!! Dec 12 17:22:11 Suppose I'm building for a product that can't have any GPLv3 stuff on it. Dec 12 17:22:40 The obvious way is to do INCOMPATIBLE_LICENSE = "GPLv3 GPLv3+ LGPLv3 LGPLv3+ AGPLv3 AGPLv3+" in the distro's conf. Dec 12 17:22:58 But then, we can't build a "developer build" -- which is OK to have GPLv3 stuff. Dec 12 17:23:23 If I split it to a separate distro... then we're developing with different versions of software than we are shipping on the product. Dec 12 17:23:35 Any recommendations for how to handle this? Dec 12 17:25:23 gabrbedd: What do you need in the developer build which is GPLv3? Dec 12 17:25:41 paulbarker: for example, gdb Dec 12 17:26:18 you could possibly try setting INCOMPATIBLE_LICENSE_pn-gdb = "" Dec 12 17:28:02 That should change INCOMPATIBLE_LICENSE just for gdb and nothing else Dec 12 17:28:39 paulbarker: in the distro conf file? Dec 12 17:29:01 distro conf or local.conf should be fine Dec 12 17:29:02 paulbarker: one reason for _not_ doing that... it could accidentally end up in the product image. Dec 12 17:29:31 Hmm... or I could add the override to the images that need it. Dec 12 17:29:52 The override needs to apply when the gdb recipe is read so you can't put it in an image file Dec 12 17:30:57 you could create a dummy recipe, set "CONFLICTS = gdb" in that and install it in the customer image but not the developer image Dec 12 17:31:31 That should trigger an error if gdb somehow got pulled into the customer image Dec 12 17:32:54 paulbarker: let me see if I understand.... in the distro conf I set INCOMPATIBLE_LICENSE = "GPLv3...", and also set INCOMPATIBLE_LICENSE_gdb = "". Dec 12 17:33:35 I think the syntax is _pn-gdb not _gdb Dec 12 17:33:42 paulbarker: Then create a special "poison" package that declares a CONFLICTS with things lik gdb. Dec 12 17:33:50 paulbarker: what is "_pn" ? Dec 12 17:33:59 And you may need to set INCOMPATIBLE_LICENSE using ?= so it can be overridden Dec 12 17:34:26 It's a prefix, think it means 'package name' Dec 12 17:38:41 Also see PACKAGE_EXCLUDE in http://www.yoctoproject.org/docs/1.7/mega-manual/mega-manual.html Dec 12 17:40:21 Hey guys! My foo.hdimg file (which is generated by my custom bitbake file): when I run it in qemu, fdsik can't recognize the partitions it creates. Has anyone seen this? Dec 12 17:41:13 http://www.jeremymoles.com/yocto-00.png Dec 12 17:58:06 There's a screenshot of the output. Dec 12 19:51:54 vmeson: thanks for the pointer to linux-yocto-dev. Dec 12 20:32:58 Hi.. I'm strugling with Eclipse + plug-in (Build system derived toolchain).. I am trying to build/run the hello world autotools example project, but get the following errors when reconfiguring my project: Missing PROG arm-poky-linux-gnueabi-dlltool, Missing PROG arm-poky-linux-gnueabi-mt, Missing PROG dlltool.. Dec 12 20:35:59 ...appreciate any help ;) Dec 12 21:20:15 fishey: I'm glad it helped. Dec 13 02:16:56 So I upgraded from dora to dizzy, and python-dbus doesn't seem to be working? http://paste.ubuntu.com/9496601/ **** ENDING LOGGING AT Sat Dec 13 02:59:58 2014