**** BEGIN LOGGING AT Wed Oct 07 02:59:58 2015
Oct 07 04:29:26 <namra> greetings
Oct 07 04:30:45 <namra> where can i find the features supported by a yocto kernel? in the kernel-dev manual there's an example for a very old kernel 3.4 and there it states the metadata definition of features can be found in the kernel tree meta/cfg/...
Oct 07 04:31:18 <namra> but the search doesn't find that repo and there's no meta directory in the kernel source tree of 4.1
Oct 07 04:32:52 <namra> i'd like to use a newer kernel for the valleyisland bsp, thus i want to write a new recipe. i looked at the recipe that comes with it for kerenel 3.10 and there it enables the valleyisland-io
Oct 07 04:36:44 <xulfer> so writing a brand new recipe, or are you looking for one to do a bbappend off of?
Oct 07 04:38:08 <namra> brand new kernel recipe to use kernel 4.1 with the a specific feature for the valleyisland bsp. but for that i need to know if that feature is supported
Oct 07 05:38:37 <drou> hi guys
Oct 07 06:16:34 <drou> is there anyway to override something in a .inc file ?
Oct 07 06:36:06 <_4urele_> drou, I would say that you can create a new recipe in another layer
Oct 07 06:36:28 <_4urele_> drou, create a bbappend?
Oct 07 06:37:57 <drou> actually, i want to override SRC_URI variable of meta-qt5/recipes-qt/qt5/qt5-git.inc which is required by several qt5 recipes
Oct 07 06:38:29 <drou> i just want to add ;procotol=http in the default SRC_URI
Oct 07 06:44:40 <_4urele_> drou, did you tried a bbapend? (overiding just the SRC_URI
Oct 07 06:47:27 <drou> _4urele_: not really, i just wanted to avoid creating a lots of .bbappend. otherwise, i'll have to create a qtbase_git.bbappend, gtsvg_git.bbappend, qtwebkit_git.bbappend...
Oct 07 06:49:38 <_4urele_> drou, sry i'm not sure how to do this ;)
Oct 07 07:09:14 <namra> hm how to build an intel bsp? trying to build an image with the valleyisland bsp and followed that guide: http://www.intel.com/content/www/us/en/embedded/products/bay-trail/atom-e3800-devkit-yocto-bsp-user-guide.html
Oct 07 07:09:58 <namra> but when running the build command it complains it can't find recipes for the kernel recipes
Oct 07 07:10:51 <namra> meta-intel/common/recipes-kernel/linux/linux-yocto_3.10.bbappend and meta-intel/meta-isg/meta-valleyisland/recipes-kernel/linux/linux-yocto_3.10.bbappend
Oct 07 07:12:17 <namra> do i have to clone the according kernel?
Oct 07 09:01:48 <premoboss> hello! total newbie in yocto here! my board is cubieboard2, ARM embedded system. it it supported by yocto?
Oct 07 09:06:23 <maxin> premoboss: yes.. using meta-sunxi : http://layers.openembedded.org/layerindex/branch/master/machines/?q=cubieboard2
Oct 07 09:06:38 <premoboss> thanks.
Oct 07 10:11:16 <premoboss> maxin, i gitted the yocto, but now i dont cnow how to proceed.
Oct 07 10:13:22 <maxin> premoboss:  this will help:  http://www.yoctoproject.org/docs/2.0/yocto-project-qs/yocto-project-qs.html
Oct 07 10:13:51 <belen> premoboss: you might also want to try the Toaster UI. It might help somehow to get you started. There is a tutorial here https://www.youtube.com/watch?v=f3gDg75FwFo
Oct 07 10:14:13 <premoboss> tanks all
Oct 07 11:00:22 <LetoThe2nd> ndec: concerning yesterday, see https://github.com/LetoThe2nd/blubber
Oct 07 11:00:55 <LetoThe2nd> ndec: i've checked that the two included examples should be working fine and give you a good idea of the concept.
Oct 07 11:06:31 <ndec> LetoThe2nd: thx
Oct 07 12:00:32 <ryanstur1er> Question about packages
Oct 07 12:00:51 <ryanstur1er> When a recipe is called XXX-native
Oct 07 12:01:04 <ryanstur1er> that's the package that's built for the target architecture, correct?
Oct 07 12:01:13 <ryanstur1er> and XXX is for the build system?
Oct 07 12:01:19 <ryanstur1er> Or do I have that backwards?
Oct 07 12:01:38 <neverpanic> XXX-native is for your build system
Oct 07 12:01:46 <neverpanic> XXX is for the target architecture
Oct 07 12:02:44 <ryanstur1er> Thanks!
Oct 07 13:19:12 <lzm> how can i get the target's CC variable in a native recipe?
Oct 07 13:20:59 <ryanstur1er> I have no idea, but I am curious why you need it - can you elaborate?
Oct 07 13:25:01 <lzm> the recipe will create a wrapper script that can switch between gcc and my own compiler
Oct 07 13:25:22 <lzm> and i can build other recipes with that wrapper script by setting CC_pn-bla = "wrapper_script"
Oct 07 13:33:26 <acidfu> how can I pass "-Wall" from yocto recipe to gcc ?
Oct 07 13:48:04 <bboozzoo> acidfu: try CFLAGS_append in your recipe
Oct 07 13:57:07 <lzm> i managed to recreate CC by inheriting from cross
Oct 07 14:20:21 <acidfu> bboozzoo, thx !
Oct 07 14:29:12 <ryanstur1er> @lzm Neato
Oct 07 14:30:11 <ryanstur1er> If I create a new layer, the recipes I define in my layer aren't added to an image unless they get appended to IMAGE_INSTALL
Oct 07 14:30:20 <ryanstur1er> or unless another recipe depends on them, is that correct?
Oct 07 14:47:52 <acidfu> mmm, I have a recipe to build gpsd, it creates libgps.a ( gpsd/3.14-r0/gpsd-3.14/libgps.a ) but when tie library is installed into ( tmp/sysroots/litecell15/usr/lib/libgps.a  )
Oct 07 14:47:59 <acidfu> all the symbols are stripped out of the .a :|
Oct 07 14:48:12 <acidfu> if I do the nm -s on libgps.a in the installed dir I get nothing
Oct 07 14:48:23 <acidfu> but nm -s on the libgps.a created in the gpsd directory is find
Oct 07 14:48:25 <acidfu> fine
Oct 07 14:53:27 <ryanstur1er> What do I do in the situation where I have 2 layers that provide a recipe with the same name
Oct 07 14:53:35 <ryanstur1er> that are in fact different recipes
Oct 07 14:54:08 <acidfu> change the priority
Oct 07 15:10:39 <acidfu> hey folks, does it exist something like INHIBIT_PACKAGE_STRIP but for .a (archive) file ?
Oct 07 15:10:49 <acidfu> because that juste prevent the binaries from being stripped :|
Oct 07 15:21:52 <ryanstur1er> If I deleted my work/tmp/deploy directory, and I want to re-build my image, how do I do that without having to re-compile everything?
Oct 07 15:22:14 <ryanstur1er> oooh wait I think I may know
Oct 07 15:24:28 <ryanstur1er> bitbake -c clean <imagename>; bitbake <imagename>
Oct 07 15:28:00 <rburton> yeah that works, or bitbake imagename -C rootfs will probably work too
Oct 07 15:28:13 <rburton> (forcibly re-run the rootfs task on imagename)
Oct 07 15:29:08 <acidfu> arm-poky-linux-gnueabi-strip /work/poky/build/tmp/work/cortexa15t2hf-vfp-neon-poky-linux-gnueabi/gpsd/3.14-r0/image/usr/lib/libgpsd.a
Oct 07 15:29:22 <acidfu> How do I block the strip ?
Oct 07 15:31:24 <rburton> acidfu: if you actually mean, i want gpsd debugging info, install gpsd-dbg
Oct 07 15:31:36 <acidfu> im cooking my own recipe
Oct 07 15:31:56 <rburton> you are aware there's a gpsd recipe already right?
Oct 07 15:32:28 <acidfu> I am
Oct 07 15:37:34 <acidfu> there must have something to inhibit the static libraries to be stripped :}|
Oct 07 15:37:37 <acidfu> :|
Oct 07 15:58:21 <jmesmon> Is there a way to ask bitbake what is causing a package to be installed?
Oct 07 16:33:25 <ryanstur1er> @jmesmon You can do bitbake -g
Oct 07 16:33:41 <ryanstur1er> it will produce a couple of helpful dependency graph files
Oct 07 16:34:01 <ryanstur1er> which you can render with graphviz if you like, but they are human-readable too
Oct 07 16:34:11 <ryanstur1er> ls
Oct 07 16:53:03 <acidfu> is there a "target" called something like post_populate_sysroot()
Oct 07 16:53:15 <acidfu> where I can do some stuff after the files are copied to the sysroot ?
Oct 07 16:54:14 <kergoth> its unlikely you want to be doing that. the sysroot population is automatic for good reason
Oct 07 16:55:55 <acidfu> if you tell me how to prevent a static library from being stripped, I won't need to try to find a work around :) hehe
Oct 07 17:31:35 <bryan__> Hello Everybody
Oct 07 17:32:28 <bryan__> i want to add ibus-hangul, imhangul packages in yocto...Do we have any recipe for these packages?
Oct 07 17:38:27 <bryan__> can anyone help in this?
Oct 07 18:20:23 <ryanstur1er> Is there a way I can get bitbake to show the output of the task it's performing at the shell?
Oct 07 18:20:53 <ryanstur1er> I know it performs tasks in parallel, but if I'm just running tasks on a recipe onesey-twosey, is it able to print out the output of, (for example) configure, make, etc.?
Oct 07 18:22:03 <ryanstur1er> All the "verbose/Debug" options I have found expose the internals of bitbake, but not the underlying tasks
Oct 07 18:22:52 <neverpanic> ryanstur1er: you can find the output in the logfiles, but I doubt that's what you're after?
Oct 07 18:24:00 <ryanstur1er> I can, I just prefer a workflow where I don't have to hunt for a logfile every time I do a build
Oct 07 18:25:10 <ryanstur1er> I was hoping there was maybe something I could pass to bitbake to get it to squirt it out to the shell
Oct 07 18:31:45 <ryanstur1er> Another question I have is:  If I do a bitbake -c clean <recipe> and then bitbake <recipe> shouldn't that result in a recompile?
Oct 07 18:32:26 <ndec> ryanstur1er: in general, no. because there is the sstate cache
Oct 07 18:32:57 <ndec> so if no build parameters have changed, the package isn't rebuilt but reused from the cache.
Oct 07 18:33:01 <ryanstur1er> If I've made a change to my recipe file, and I want to provoke it to basically re-build that recipe from scratch what do I need to tell bitbake?
Oct 07 18:33:52 <ndec> -c cleansstate would clean the local work tree, and remove the prbuilt from the cache
Oct 07 18:34:51 <ryanstur1er> Ah that did it.
Oct 07 18:35:25 <ryanstur1er> little by little!  Man, I'm going to start a cheat sheet for this stuff - none of the cheat sheets I've found out there cover some of these seemingly really-important nuggets.
Oct 07 18:51:41 <ryanstur1er> I have added "install -d ${D}/my/directory" in the do_install step in a recipe I'm developing, and I get the QA warning that /my and /my/directory are "installed but not shipped"
Oct 07 18:52:06 <ryanstur1er> This is just an empty directory I want created on the target rootfs for configuration files for my application -
Oct 07 18:53:52 <kergoth> see the yocto docs about packaging.
Oct 07 18:54:14 <kergoth> the content in ${D} is broken up into multuiple binary packages (those listed in PACKAGES), each including the files/patterns in FILES_<packagename>
Oct 07 18:54:24 <kergoth> that path you created isn't included in the default paths for the default binary packages, so you'd ahve to add it
Oct 07 18:54:32 <kergoth> e.g. FILES_${PN} += "/my/directory"
Oct 07 18:54:42 <kergoth> er, /my, actually
Oct 07 18:54:44 <kergoth> but you get the point
Oct 07 18:56:26 <ryanstur1er> Ok
Oct 07 18:57:15 <ryanstur1er> I only have the one package, so I have to add it to the files list for that package.  What is "shipped" is what is specified in FILES_<packagename>
Oct 07 18:57:24 <ryanstur1er> and what is installed is what I actually dropped in {D}
**** ENDING LOGGING AT Thu Oct 08 02:59:58 2015