**** BEGIN LOGGING AT Tue Mar 18 02:59:59 2014 Mar 18 05:26:09 hi all i have try to compile eglibc-initial in poky with meta-atmel setup,i got the following error http://pastebin.com/fFm4PpZh i googled but did not get any idea can please help me to solve this issues Mar 18 06:05:06 d Mar 18 06:09:13 Hello. I build a core-image-minimal with qt5 according to this link: http://wiki.wandboard.org/index.php/Getting_started_with_Yocto_on_Wandboard and this link: http://wiki.wandboard.org/index.php/Building_Qt5_using_yocto_on_Wandboard Mar 18 06:09:42 The problem is that this image has not libQt5Declarative.so.5 on it, so I wanted to add QtDeclarative Mar 18 06:10:47 but so far I have not been successful. I tried adding this in INSTALL_IMAGE section in the .bb file under .sources/yocto/meta/receipe-core/images/core-image-minimal.bb Mar 18 06:11:49 I also change the configuration in meta-qt5 in order to include qtdeclarative in ./sources/meta-qt5/receipes-qt/qt/qtbase.inc Mar 18 06:12:26 in the build folder, if I look for the library I need, I can see it, but this library is not included in the yocto image.... Mar 18 06:13:06 Is there anybody who has a tip for this please? By the way, I am working with a wandboard-dual Mar 18 07:12:30 hello? Mar 18 07:12:35 is anybody aout there? Mar 18 07:13:47 naKismus: some people are here,but usually folks will wake up in two or three hours Mar 18 07:58:04 do bitbake questions go in this channel? Will bitbake ever pass arguments to a task function? like python do_mytask(x) { ... } or is all context available through the bb package? Mar 18 08:04:11 good morning Mar 18 09:09:15 good morning Mar 18 09:25:22 hi rburton Mar 18 09:26:06 rburton: do you know why this .bbappend not generating the extra busybox-ntp package? http://paste.kde.org/pheug7iev Mar 18 09:26:27 I see this: bitbake -e busybox | grep ^PACKAGES= Mar 18 09:26:28 PACKAGES="busybox-httpd busybox-udhcpd busybox-udhcpc busybox-syslog busybox-mdev busybox-hwclock busybox-dbg busybox-staticdev busybox-dev busybox-doc busybox-locale busybox busybox-ntp" Mar 18 09:26:53 and I have the file in ./tmp/work/armv5te-foo-linux-gnueabi/busybox/1.20.2-r8/packages-split/busybox/etc/init.d/ Mar 18 09:27:09 but for some reason, the package is not generated in tmp/deploy/ipkg Mar 18 09:29:00 the .ipk is not in ./tmp/work/armv5te-foo-linux-gnueabi/busybox/1.20.2-r8/deploy-ipks/armv5te/ either. Mar 18 09:32:04 bluelightning: hi, just in case you have any clue, http://paste.kde.org/pvanpvejb Mar 18 09:32:15 morning all Mar 18 09:33:22 lpapp: since the entry in PACKAGES is after the main package, perhaps the files are being picked up by the main package instead Mar 18 09:33:39 maybe use PACKAGES =+ instead of PACKAGES += Mar 18 09:33:52 ah, that is why they used prepend in busybox.inc? Mar 18 09:35:19 bluelightning: wow, that fixed it thanks. Mar 18 09:35:24 have a look inside busybox and see if that's where you file ended up Mar 18 09:36:11 ok, the second question is that why is it not enough to use INITSCRIPT_PACKAGES? Mar 18 09:36:17 (I mean in an ideal world) Mar 18 10:06:07 what is the preferred way for custom config files in Yocto, i.e. not a provided interface by the third-party software? Mar 18 10:06:25 is it /etc/default/foo.conf like in debian or there is no "rule of thumbs"? Mar 18 10:06:37 thumb* Mar 18 10:07:55 to concretize this, where shall I put an ntp.conf to set up the peer information at the very least so that the config is sourced properly before the corresponding init.d/ntp.busybox is run on start up? Mar 18 10:08:23 also, will I need to source that explicitly, or it is done behind the scenes magically for me? Mar 18 10:09:36 lpapp: debian style i.e. ${sysconfdir}/default Mar 18 10:09:48 yes Mar 18 10:10:12 but for instance the busybox recipe seems to put them into /etc directly. Mar 18 10:10:21 e.g. inetd.conf or mdev.conf Mar 18 10:10:44 well hang on, it depends if you are talking about scripts that set env vars that initscripts use or conf files Mar 18 10:10:57 ${sysconfdir}/default for the former, ${sysconfdir} for the latter Mar 18 10:10:58 and I do not see those files sourced directly in mdev and inetd, but it might be because those softwares recognize the config by default. I cannot be sure. Mar 18 10:11:24 yes, the latter, I think. Mar 18 10:11:36 so I do not need to source the conf files explicitly? Mar 18 10:11:57 lpapp: I don't know anything about the busybox ntp module, sorry Mar 18 10:14:45 no, the PEER variable would be used only by the corresponding init script to pass it to the -p argument of ntpd. Mar 18 10:15:10 busybox ntpd does not handle config files on its own, so it is not like you pass a config file on the command line or there is a default location. Mar 18 10:15:28 this would need to be handled by the hand-crafted init script and the corresponding config files. Mar 18 10:15:59 I'd be surprised if nobody had ever written one for busybox's ntp daemon Mar 18 10:16:07 (outside of our project) Mar 18 10:16:18 yes, that is why I suggested to upstream this work later. Mar 18 10:16:42 I meant, why write one when someone else will have done it already... Mar 18 10:17:13 https://www.mail-archive.com/yocto@yoctoproject.org/msg00559.html Mar 18 10:17:23 "The busybox ntp client does not support a config file." -> they say the same as I noticed. Mar 18 10:17:36 I understood, but really, I do not find any. Mar 18 10:18:10 ok, in worst case the init script will source /etc/busybox-ntp.conf :) Mar 18 10:18:18 to get the PEER variable into context. Mar 18 10:54:07 hi. i still have the same problem i had some days ago: i try to replace /etc/network/interfaces by overriding the file from recipes-core/init-ifupdown, and it works *but* if i change the file and rebuild the image the new file is not installed! Mar 18 10:55:07 i have removed the old poky-dora directory and untarred poky-dora-10.0.1.tar.bz2 Mar 18 10:55:35 ionte: is it packaged though? Mar 18 10:55:36 i install my custom layer ("cd poky-dora-10.0.1; ln -s ../meta-griffin") Mar 18 10:55:57 setup the environment and run "bitbake griffin-image" Mar 18 10:56:02 lpapp: what does that mean? Mar 18 10:56:13 from within a python bitbake task function, how do i access variables? examples usually go something like "d.getVar(...)", but d is not in my scope? Mar 18 10:56:38 mago_: is it a task function or something defined with "def ..." ? Mar 18 10:57:23 ionte: I think maybe I'm going to have to replicate your scenario here and see if I hit the same problem, because it ought not to behave like that Mar 18 10:57:58 bluelightning: absolutely. i'll hand you my layer files if you want. Mar 18 10:58:19 ionte: if you can that would save me a bit of time Mar 18 10:58:39 bluelightning: yes. also, i'm sure it's something i've missed. just getting started with yocto... Mar 18 10:58:49 so i'm sure the problem is in my layer somewhere... Mar 18 10:59:16 ionte: I'm not ruling out a bug at this point based on the description, but I'll have to see Mar 18 11:01:04 bluelighting: here's the recipe: https://dl.dropboxusercontent.com/u/176615/meta-griffin.bz2 Mar 18 11:01:07 layer.. Mar 18 11:01:51 bluelighting: here's my build commands: http://pastebin.com/bAQzP7Qw Mar 18 11:11:17 ionte: that doesn't seem to contain a bbappend for init-ifupdown... ? Mar 18 11:13:05 uhm.. oh .. wait.. i might not have pushed my changes to git... sorry... Mar 18 11:13:09 one minute Mar 18 11:16:01 bluelightning: here's the current version: https://dl.dropboxusercontent.com/u/176615/meta-griffin-2.bz2 Mar 18 11:18:34 ionte: ok, as far as the bbappend goes it looks like everything is set up correctly; although the file shouldn't need to be in a "qemux86" subdir of files/ Mar 18 11:18:47 I'm just building it to see what happens Mar 18 11:19:35 bluelightning: shouldn't it? i saw that there was such subdirectories in the init-ifupdown recipe and it happens to suit my case very well (on qemux86 i want one network setup, on the hardware device i'm developing for i want another...) Mar 18 11:19:59 bluelightning: and it is installed on the first run so it seems to find it at least... Mar 18 11:20:03 ionte: right, for that scenario yes that makes sense Mar 18 11:21:09 bluelightning: btw, do you know in what order the files are used? mylayer/qemux86/interfaces, mylayer/interfaces, default/qemux86/interfaces, default/interfaces ... ? Mar 18 11:22:26 bluelightning: the best way to get the ntp package into my image would be put it into rrecommends when creating my .bbappend, right? Mar 18 11:22:54 ionte: it's in the order that OVERRIDES lists the overrides; you should be able to see the directories searched in order in log.do_fetch Mar 18 11:23:27 lpapp: or just add it to IMAGE_INSTALL in your image... Mar 18 11:23:57 bluelightning: yes, but that would need to be replicated for different images by default. Mar 18 11:24:43 lpapp: use a packagegroup then Mar 18 11:25:02 lpapp: if you want to put it in the bbappend go ahead, but that's not the way it ought to be done Mar 18 11:26:29 bluelightning, it's a task function, e.g. python do_build() { .. does it matter? Mar 18 11:26:53 bluelightning: that is how all the rest is done in busybox.inc Mar 18 11:28:29 i'll be away for a bit... Mar 18 11:29:17 wgao: how do you know it is "not in your scope"? Mar 18 11:34:50 mago_: then d.getVar('VARIABLENAME', True) should work Mar 18 11:37:54 bluelightning: FYI regarding ccache. You where so nice to tell me that some things might not get rebuild correctly. I've been using it since you told me how to enable it. And it seems to work well. Nothing that should be rebuild does'nt. Mar 18 11:38:12 SorenHolm: ok, great Mar 18 11:38:15 bluelightning, where is d defined then? is it a magic variable that is available in the scope without any declaration in the task function signature? Mar 18 11:39:01 bluelightning: It'd sure be nice to know what actually where broken when it was disabled. Mar 18 11:40:13 mago_: yes; bitbake python task functions can't take arguments, and d is always defined (it points to an instance of DataSmart defined in bitbake/lib/bb/data_smart.py) Mar 18 11:40:29 SorenHolm: I don't have that information I'm afraid Mar 18 11:41:07 bluelightning, is there a list of these superglobal variables? i thought i read the manual quite carefully, but must've missed it Mar 18 11:41:34 bluelightning: no problem. Mar 18 11:41:53 mago_: d is really the only one Mar 18 11:42:57 mago_: this stuff is better documented in the new bitbake manual (WIP version here: http://www.yoctoproject.org/docs/temp/user-manual/user-manual.html ) Mar 18 11:43:21 thank you Mar 18 11:43:52 FYI, in case you would like to know, the "d" that you see in python functions gets into the python environment for the function via exec_func_python() in bitbake/lib/bb/build.py Mar 18 11:44:25 3.4.3 Mar 18 11:44:41 http://www.yoctoproject.org/docs/temp/user-manual/user-manual.html#python-functions Mar 18 11:53:36 bluelightning, if i do bb.note() or any other logger function, where should I expect to see the output? i looked into bb/__init__.py, and the logger defined seem to use some kind of "NullHandler" which just discards logs? Mar 18 11:54:19 mago_: bb.note() and bb.debug() go to the task log file in ${T} (i.e. the "temp" directory in the workdir for the recipe) Mar 18 11:54:48 mago_: bb.warn(), bb.plain() and bb.error() will be printed to the console via the UI Mar 18 11:55:03 ah, great Mar 18 11:55:22 (the latter also go to the log as well as you'd imagine) Mar 18 11:56:59 How come is the following directory empty when the downloads folder contains the "bare repository clone" fine? ./tmp/work/armv5te-foo-linux-gnueabi/bar/version/git/ Mar 18 12:07:20 bluelightning, is it possible for a bitbake python function to call a bitbake shell function? Mar 18 12:08:01 mago_: if you need to you can use bb.build.exec_func() to do that, yes Mar 18 12:09:53 perhaps that is not a common usecase? if not, what is the point in having the ability to write functions in either shell or python syntax? Mar 18 12:19:09 bluelightning: did you get to test build my layer? Mar 18 12:19:53 any ideas? Mar 18 12:20:02 I cannot seem to get the source into the work folder. :( Mar 18 12:36:52 mago_: as bluelightning said, you can use exec_func() to call the shell function Mar 18 12:38:24 I am confused why I see these busybox "subpackages" installed on the core-image-minimal because I only see busybox in the core boot package group, http://paste.kde.org/p41tqwryf Mar 18 12:42:53 lpapp: perhaps there are dependencies on them from other packages? Mar 18 12:45:12 bluelightning, trying to create a build dependency. the manual states i should put in "items" in my DEPENDS variable and that I shall update the deptask varflag of my task functions. What is an item in this case? is the .bb-filename? I see no other "name" assigned to my recipe Mar 18 12:52:05 RP: ok, I will check with opkg what* Mar 18 12:57:36 mago_: DEPENDS must match up with some other recipe's PROVIDES (and a recipe's own name is implicitly in its PROVIDES) Mar 18 12:59:21 okay, and how do i set the recipe name? Mar 18 13:02:12 mago_: it comes from the filename Mar 18 13:02:33 so myrecipe_1.5.bb sets PN to "myrecipe" and PV to "1.5" Mar 18 13:02:53 ok, can I also assign PN directly from my .bb-file? Mar 18 13:31:24 mago_: you can yes Mar 18 13:50:43 my poky build slows down on the download of a linux kernel from git.yoctoproject.org. how might i speed this up? Mar 18 14:04:24 j8: faster internet, it's cloning the full kernel. it's a one-time download, don't worry. Mar 18 14:11:33 i am using a local PREMIRROR and SSTATE_MIRRORS for caching. i have traced linux-yocto/.../log.do_fetch, and it extracts git2_git.yoctoproject.org.linux-yocto-3.10.git.tar.gz. it appears to slow on git fetch -f --prune Mar 18 14:11:51 the second run through, it appears to populate from its new local SSTATE_CACHE Mar 18 14:15:17 bluelightning: sorry to nag, but did you get a chance to test my layer? Mar 18 14:15:56 ionte: so I tested just the recipe alone, and changing the file did do what I expected i.e. the changed file ended up in the package Mar 18 14:16:06 I am now testing the image Mar 18 14:16:13 ok! Mar 18 14:16:52 ionte: btw did you try bitbake -c cleansstate init-ifupdown ? Mar 18 14:17:20 ionte: not that you should have to do this but I wonder if this is caused by some old cached state and the file being missing earlier Mar 18 14:17:57 bluelightning: no, but i deleted the whole poky-dora directory and tried again.. Mar 18 14:18:20 the exact steps are in the pastebin i posted Mar 18 14:18:31 http://pastebin.com/bAQzP7Qw Mar 18 14:19:59 ok... sorry I'm doing this in a VM so it's not exactly blazingly fast Mar 18 14:20:41 np Mar 18 14:22:09 Hello Everybody!! Mar 18 14:23:20 Hello. I build a core-image-minimal with qt5 according to this link: http://wiki.wandboard.org/index.php/Getting_started_with_Yocto_on_Wandboard and this link:http://wiki.wandboard.org/index.php/Building_Qt5_using_yocto_on_Wandboard Mar 18 14:23:30 The problem is that this image has not libQt5Declarative.so.5 on it, so I wanted to add QtDeclarative Mar 18 14:23:31 [07:10am]naKismus:but so far I have not been successful. I tried adding this in INSTALL_IMAGE section in the .bb file under .sources/yocto/meta/receipe-core/images/core-image-minimal.bb Mar 18 14:23:41 I also change the configuration in meta-qt5 in order to include qtdeclarative in ./sources/meta-qt5/receipes-qt/qt/qtbase.inc Mar 18 14:23:49 in the build folder, if I look for the library I need, I can see it, but this library is not included in the yocto image.... Mar 18 14:23:55 Is there anybody who has a tip for this please? By the way, I am working with a wandboard-dual Mar 18 14:25:56 Is there anybody there? Mar 18 14:26:37 yes, there are, but i'm too new to be of any help Mar 18 14:31:46 yeaahh I am too.... Mar 18 14:33:05 naKismus, There is a Yocto Project Technical Team Meeting at 11am Eastern Daylight Time so maybe you will have more chance later ;) Mar 18 14:33:32 naKismus: it's IMAGE_INSTALL not INSTALL_IMAGE Mar 18 14:34:05 blue lightning I meant INSTALL_IMAGE Mar 18 14:34:21 blue lightning I meant INSTALL_IMAGE Mar 18 14:34:45 INSTALL_IMAGE doesn't exist, IMAGE_INSTALL is the name of the variable that specifies the list of packages to install into the image Mar 18 14:34:50 bluelightning I meant INSTALL_IMAGE Mar 18 14:35:08 also, you can use tab completion for nicknames ;) Mar 18 14:35:26 HAHAHAHA ok!! Thansk!!! :) bluelightning Mar 18 14:36:30 naKismus, did you try to simply append it into your local.conf with IMAGE_INSTALL_append = " bzip2 example" Mar 18 14:40:00 does YP 1.6 have a code name yet? It's not recorded here: Mar 18 14:40:01 https://wiki.yoctoproject.org/wiki/Releases Mar 18 14:40:45 kapare: I also tried that. I appended qtdeclarative-qmlplugins to IMAGE_INSTALL_append in ./build/conf/local.conf... but also did not work. Mar 18 14:41:03 And I also add it to IMAGE_INSTALL_extras Mar 18 14:44:45 kapare: in which part of the globe is this technical team located? I am in Germany. Here the time is 15:43 pm Mar 18 14:45:35 haas sorry... Eastern Daylight time.... thanks! Mar 18 14:45:57 naKismus: its in 15 minutes :) Mar 18 14:46:13 haha yeah.. I just checked on Google :) thanks! Mar 18 14:47:33 naKismus, https://lists.yoctoproject.org/pipermail/yocto/2014-March/018607.html Mar 18 14:59:16 YPTM: IonutC is on Mar 18 15:00:26 YPTM: Scott Rifenbark is on the call Mar 18 15:00:34 YPTM: Matthew Weigel is on the call Mar 18 15:01:03 YPTM: Cristiana is on the call Mar 18 15:01:11 YPTM: cristian.iorga present Mar 18 15:01:12 YPTM: Participant passcode: 42001078 Dial-in number: 1.972.995.7777 US Toll Free number: 1.877.561.6828 BlackBerry users, click this link to join your conference as a participant: 1.972.995.7777x42001078# Mar 18 15:01:31 YPTM: belen joined Mar 18 15:01:55 YPTM: calling in now Mar 18 15:02:34 YPTM nitin joined the call Mar 18 15:02:41 YPTM: ross joined Mar 18 15:03:29 YPTM: Saul is on Mar 18 15:03:32 YPTM Jefro is here Mar 18 15:03:43 YPTM: 1.4.3 status and 1.5_M4 status Mar 18 15:03:47 YPTM: Tom Z on Mar 18 15:04:12 it's an open Mar 18 15:05:20 YPTM: Richard is on the call Mar 18 15:05:26 YPTM: hi all Mar 18 15:06:56 YPTM: Paul Eggleton is on Mar 18 15:07:10 YPTM: Bruce Ashfield is on Mar 18 15:17:27 otavio: http://autobuilder.yoctoproject.org/main/builders/nightly-fsl-arm-lsb/builds/100 :/ Mar 18 15:19:19 RP: Oh OK Mar 18 15:19:24 I will look into it Mar 18 15:19:59 RP: I am finishing a build with clutter and will do a core-image-minimal to check the providers; this seems to be the error you are seeing Mar 18 15:20:24 otavio: also http://autobuilder.yoctoproject.org/main/builders/nightly-fsl-arm/builds/96 :( Mar 18 15:21:14 RP: It is the same Mar 18 15:21:22 RP: I mean; same root cause Mar 18 15:21:30 otavio: ok Mar 18 15:22:07 RP: is this reproducable with master or just master-next? Mar 18 15:22:19 otavio: Is it building the wrong kernel there? Mar 18 15:22:24 RP: yes Mar 18 15:22:56 otavio: right, this is "our" fault then, probably due to http://git.yoctoproject.org/cgit.cgi/poky/commit/?h=master-next&id=5b6d1850dd7b6f4ceafe0a17d81ecf8aaeef5302 Mar 18 15:23:12 otavio: sorry, I hadn't realised the kernel provider was getting messed around like that Mar 18 15:23:23 sgw_: We need to find a more conditional way of testing this Mar 18 15:24:08 RP: No problem; in any case I started a fresh build in my builder using master and tip of fsl-arm Mar 18 15:24:56 RP: you can set it as ?= Mar 18 15:25:08 RP: I think it will do the trick no? Mar 18 15:25:32 RP: or set it to the yocto-bsp machines Mar 18 15:25:48 ^ seems ideal Mar 18 15:26:38 tf: please take a look in master branch of meta-cluttr Mar 18 15:26:45 tf: i did some fixes Mar 18 15:29:13 otavio: right, we'll need to improve it Mar 18 15:29:46 RP: sure; that's is the beauty of open source development :) Mar 18 15:41:51 RP: yes agreed, it's a big switch and could be more conditional, that will also make the AB more complex! Mar 18 15:42:30 RP: so let the -next build finish this time and then run a 1.4.3 Mar 18 15:42:49 sgw_: yes Mar 18 15:43:06 sgw_: I think I've found an sstate reuse issue, patch on the list Mar 18 15:43:18 so we could probably do with a master after that with that fix merged Mar 18 15:45:02 RP: sounds like a plan Mar 18 15:45:38 cristianiorga: "WARNING: QA Issue: pulseaudio: configure was passed unrecognised options: --enable-bluez" for pa5 Mar 18 15:45:45 * pidge perks up. Mar 18 15:46:33 sgw_: that patch. uh. that's going to cause me problems, isn't it. Mar 18 15:47:05 pidge: we'll find some way to make sure its "easy" to use Mar 18 15:48:01 rburton: PA5 upgrade was submitted by Khem Raj Mar 18 15:48:22 cristianiorga: good point :) Mar 18 15:48:45 RP: heh. Ok, so, I can override it via the UI and in release branches just do a commit that pins it when the time is right. Mar 18 15:49:59 This is probably a sign we shouldn't merge the pa5 upgrade Mar 18 15:51:51 considering the regression that cristian has talked about i agree Mar 18 15:52:36 nerdboy: are you around? Mar 18 15:53:06 RP: would be others also :-D Mar 18 15:55:02 RP: shouldn't that be set with a machine override for the machines in our BSPs rather than just set for everything? Mar 18 15:55:41 bluelightning: yes Mar 18 15:55:55 bluelightning: that's that I was thinking also, we would need somekind of UI for that in the AB or I would have to make the changes by hand all the time for the -dev testing. Mar 18 16:02:19 ionte: ok, I seem to have reproduced your problem Mar 18 16:02:50 ionte: init-ifupdown does get rebuilt, but do_rootfs never seems to be executed - is that what you see also? Mar 18 16:27:37 ionte: ah, now I remember... try applying this patch: http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=paule/dora-image-fix&id=cfeca813912084385401499379c95ad7a06b86ca Mar 18 16:50:11 its normal to not be able to run menuconfig on targets such as core-image-sato yes? Mar 18 16:50:31 menuconfig is provided by the buildsystem of the software in question Mar 18 16:50:37 busybox, the kernel,e tc provide 'make menuconfig' Mar 18 16:50:42 I assume you have to run it on linux-yocto to point directy to the kernel Mar 18 16:51:07 assuming linux-yocto is what you need to configure, yes. it's not the only recipe that supports it Mar 18 16:51:35 kergoth: Paul mentioned you had some thoughts about the signal handlers? Mar 18 16:51:51 kergoth: We're seeing hangs on some of the builds, looks like its looping around waitpid :( Mar 18 16:52:14 is there a command that lists all available targets of menuconfig? Mar 18 16:53:19 asdf_: no, only the other way around, you can use -c listtasks to list the tasks that can be run for a given recipe Mar 18 16:53:33 RP: not offhand, no. I've seen some of the issues too, but haven't had time to dig into it, sorry Mar 18 16:54:05 kergoth: ok. I'm at a loss as to what is breaking right now :/ Mar 18 16:55:18 honestly, i'd probably have to bust out my copy of advanced programming in the unix environment, my signal handling is a bit rusty :) Mar 18 17:01:28 kergoth: reading a bit more, this could well be a peculiarity about the way python delays signal handlers Mar 18 17:02:06 Yeah, for some reason the config frags I've made are not actually getting propagated to the build. I run menuconfig, locate the config file, create fragments that are placed in my BSP layer /meta-minnow/recipes-kernel/linux/linux-yocto/ Mar 18 17:02:29 and the SRC_URI is updated in my bbappend for that layer: http://pastebin.com/a9u9xUCY Mar 18 17:02:54 bbappend is linux-yocto_3.10.bbappend Mar 18 17:03:15 linux dir of that path above Mar 18 17:03:55 did you use bitbake -e to examine SRC_URI in linux-yocto and make sure it's set to what you think it is? Mar 18 17:03:59 * kergoth shrugs Mar 18 17:04:45 halstead: bugzilla appears down Mar 18 17:06:32 kergoth: is that listed in the include history/ Mar 18 17:06:33 ? Mar 18 17:07:21 include history just lists the files parsed, but farther down is the actual valueso f the variables, and just above that is the exact lines of the files where the value of that variable was altered Mar 18 17:09:43 So, does anyone know why the lttng 2.4 upgrade went in lacking support for ARM? I'd think it'd be better to leave off the upgrade than to regress on support for one of hte major architectures right before release Mar 18 17:09:52 seems a bit odd to me Mar 18 17:10:11 s/support/lttng support/ Mar 18 17:14:36 looks like its parsing them: # "file://usb.cfg file://bluetooth.cfg file://ps3.cfg" # "was: git://git.yoctoproject.org/linux-yocto-3.10.git;bareclone=1;branch=${KBRANCH},${KMETA};name=machine,meta file://usb.cfg file://bluetooth.cfg file://ps3.cfg" Mar 18 17:14:49 oops, that was supposed to be a pastebin, sorry Mar 18 17:15:05 kergoth: looks like an upstream issue based on the commit message... Mar 18 17:15:17 kergoth: on the face of it though I'd have to agree Mar 18 17:15:28 bluelightning: yeah, it's either an lttng bug or a toolchain bug, but either way, its a bit odd to move to it before it works for everybody.. Mar 18 17:15:31 * kergoth shrugs Mar 18 17:44:02 otavio: are you aware of this ^ ? Mar 18 17:45:07 bluelightning: I was not Mar 18 17:45:16 kergoth: the reason lttng was upgraded was to work with the 3.14 kernel, I didn't realise ARM had regressed :( Mar 18 17:45:18 bluelightning: but I agree that we ought to avoid upgrading it Mar 18 17:45:30 Hi again!!! I posted a question a few hours ago but the yocto engineering team was apparently in a meeting Mar 18 17:45:45 I build a core-image-minimal with qt5 according to this link: http://wiki.wandboard.org/index.php/Getting_started_with_Yocto_on_Wandboard and this link:http://wiki.wandboard.org/index.php/Building_Qt5_using_yocto_on_Wandboard Mar 18 17:45:54 The problem is that this image has not libQt5Declarative.so.5 on it, so I wanted to add QtDeclarative Mar 18 17:46:00 but so far I have not been successful. I tried adding this in INSTALL_IMAGE section in the .bb file under .sources/yocto/meta/receipe-core/images/core-image-minimal.bb Mar 18 17:46:08 I also change the configuration in meta-qt5 in order to include qtdeclarative in ./sources/meta-qt5/receipes-qt/qt/qtbase.inc Mar 18 17:46:18 in the build folder, if I look for the library I need, I can see it, but this library is not included in the yocto image.... Mar 18 17:46:30 s there anybody who has a tip for this please? By the way, I am working with a wandboard-dual Mar 18 17:47:08 naKismus: you keep on saying INSTALL_IMAGE.. it's IMAGE_INSTALL, you are setting the latter right? Mar 18 17:47:33 haha yes sorry... Mar 18 17:47:41 I just copied pasted it Mar 18 17:47:59 so what are you adding to that variable and how are you adding it? Mar 18 17:48:41 I am adding "qtdeclarative-qmlplugins" at the end of the list (in IMAGE_INSTALL) Mar 18 17:49:31 naKismus: are you sure that's the package containing the library in question? Mar 18 17:50:06 well.... I also tried just qtdeclarative.... but then I read somewhere that qtdeclarative-qmlplugins should be added Mar 18 17:52:59 also.. I college in the company suggested me to try: bitbake core-image-minimal -c compile -f Mar 18 17:53:12 that's not going to help Mar 18 17:53:15 then bitbake core-image-minimal -c deploy Mar 18 17:53:21 in fact it won't do anything useful at all Mar 18 17:53:27 and finally bitabke core-image-minimal Mar 18 17:53:34 mmm ok Mar 18 17:53:36 I see Mar 18 17:54:08 I'd suggest that you look under the workdir for the qtdeclarative recipe to see which package contains the library you want Mar 18 17:54:32 the easiest way to find that workdir is to do bitbake -e qtdeclarative | grep ^WORKDIR= Mar 18 17:54:43 then look under packages-split within that directory Mar 18 17:55:09 ok.... Mar 18 17:55:27 haas ok ok... i will try that! Thanks! Mar 18 17:55:56 but anyways... I should see at least qtdeclarative or qtdeclarative-qmlplugins in my final image right??? Mar 18 17:56:10 there is absolutely nothing name *qtdeclarative* Mar 18 17:57:38 depends what those packages have in them Mar 18 17:57:48 I don't have a tree with meta-qt5 enabled here to check Mar 18 17:58:28 otavio: it has been upgraded already in master Mar 18 18:04:11 http://git.yoctoproject.org/cgit.cgi/poky-contrib/commit/?h=rpurdie/t2&id=032b7afeb5a5dbc902aabebb4ff313795e833c2f is what I think will fix the chld hang issue Mar 18 18:04:18 will have to deal with it later though, out of time now Mar 18 18:10:24 I'm having some trouble building a distutils recipe--for some reason it installs it into an egg folder in site-packages as opposed to just site-packages, anyone experience this before? Mar 18 18:12:01 neabax: just checking, this is definitely for a module that uses distutils and not setuptools ... ? Mar 18 18:15:03 bluelightning: er that's a good question, embarrassingly I'm not super familiar with the difference, this is the package: https://pypi.python.org/pypi/watchdog , and its setup.py seems to import distutils Mar 18 18:18:35 neabax: ok... to be honest I think what you are seeing might be expected for the distutils class Mar 18 19:04:20 does anyone know what this is supposed to be: Failed to fetch test data from the network. Please ensure your network is configured correctly. ? Mar 18 19:04:29 what is bitbake trying to do there? Mar 18 19:16:08 I am interested in some FOSS work and am finding the bugzilla server down. I was looking for a bug to poke at to play with my new board. Thoughts? Mar 18 19:17:25 bugzilla --> 502 Bad Gateway Mar 18 19:18:52 hmm, bitbake-whatchanged is showing STAMPS_DIR changing.. STAMPS_DIR was changed by bitbake-whatchanged :) Mar 18 19:19:02 * kergoth guesses it must need to get added to the hash whitelist Mar 18 19:19:29 sqqqrly: for what its worth, the yocto bugzilla works fine from here Mar 18 19:21:07 kergoth: It is working now for me as well....thanks Mar 18 19:21:52 ah, goood Mar 18 19:23:23 rburton, sgw_ Bugzilla is back online. Mar 18 19:35:53 if i'm using SSTATE_MIRRORS, do i need to grab the stamps directory? Mar 18 19:36:54 it only download sthe sstate archive and the siginfo if it exists Mar 18 19:36:55 so no Mar 18 19:41:57 bitbake like to re-fetch linux-yocto when using an SSTATE_MIRRORS. specifically, it untars the existing git2_git.yoctoproject.org.linux-yocto-3.8.git.tar.gz from local mirror, and then it git fetches the latest ref which take a while Mar 18 19:42:07 *takes Mar 18 19:42:34 subsequent builds populate linux-yocto fully from the sstate_cache Mar 18 19:45:47 sounds like the sstate in your mirror doesn't match the one being produced, due to something changing in the metadata Mar 18 20:13:40 would i use bitbake-diffsigs to check the metadata differences? Mar 18 20:33:32 j8: yes Mar 18 20:44:32 after the build, the stamp for linux-yocto's do_fetch in my cache and working build show no differences Mar 18 21:01:17 so the distutils class doesn't seem to add my .egg to the PYTHONPATH, is this a manual step that needs to be done? Mar 18 21:01:59 bluelightning: thanks for the link to that patch! i will apply it tomorrow! Mar 18 21:07:25 bluelightning: btw, do you know if that patch will be included in future releases? Mar 18 21:21:01 ionte: it's already in master for the 1.6 release, but if it solves your problem I will try to ensure it gets in for the 1.5.2 dora point release as well Mar 18 21:41:15 fsl-image-machine-test@imx23evk (1/5) .../build/tmp/sysroots/x86_64-linux/usr/lib/rpm/bin/debugedit: canonicalization unexpectedly shrank by one character Mar 18 21:41:29 Do someone know whatthis debugedit fails means? Mar 18 22:58:38 otavio: I ran into similar issue my fix was PACKAGE_DEBUG_SPLIT_STYLE = "debug-without-src" Mar 19 02:26:52 Anyone still up? Mar 19 02:29:40 I have pretty solid Linux chops, but don't know squat about Yocto. I'm working with an Intel Galileo, and would like to tweek Intel's preconfigured Yocto archive to build only the packages I need, vs. it's default which is to build *everything* Mar 19 02:30:01 How do select/deselect which packages get built? Mar 19 02:32:43 spec_, Have you read the Quick start & Dev doc? Mar 19 02:33:44 I remember reading the Quick start a few days ago, but not the dev doc. Mar 19 02:34:30 spec_, http://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html Mar 19 02:35:14 spec_, http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html Mar 19 02:35:46 Yep. Been going through the ref manual of late. Mar 19 02:36:03 It's a lot to take in! Mar 19 02:37:18 spec_, http://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html#working-with-packages Mar 19 02:37:50 spec_, the last link explain how to 5.10.1. Excluding Packages from an Image Mar 19 02:39:10 I assume bu excluding from the final image, this means it gets skipped during the build as well? Mar 19 02:42:15 spec_, never tried but the doc says skip install so I presume the previous task are done. Mar 19 02:42:54 spec_, Otherwise just change the image recipe to have what you want in it. Mar 19 02:46:04 Awesome, thanks. **** ENDING LOGGING AT Wed Mar 19 02:59:58 2014