**** BEGIN LOGGING AT Mon Jul 13 02:59:59 2015
Jul 13 06:35:02 <mansandersson> Building against meta-qt5 I get the following error "Unknown module(s) in QT: quick". Which package am I missing dependency against?
Jul 13 07:47:19 <mckoan> good morning
Jul 13 07:53:59 <AlexVaduva> morning guys
Jul 13 08:11:03 <bluelightning> morning all
Jul 13 09:41:01 <marek__> hi, is it possible to override do_deploy function in bbappend recipe?
Jul 13 09:41:23 <marek__> I create just dummy but do_deploy from .bb is anyways called
Jul 13 09:48:15 <bluelightning> marek__: it definitely is possible yes
Jul 13 09:48:36 <bluelightning> marek__: are you sure your bbappend is being applied? is it listed in bitbake-layers show-appends ?
Jul 13 09:53:22 <marek__> bluelightning: I'm not sure and also not sure how to verify
Jul 13 09:53:44 <bluelightning> marek__: is it listed in bitbake-layers show-appends ?
Jul 13 09:54:25 <bluelightning> that will at least tell you if bitbake has seen it or not
Jul 13 09:55:00 <marek__> bluelightning: yes it's liste
Jul 13 09:55:01 <marek__> bluelightning: yes it's listed
Jul 13 09:55:13 <bluelightning> ok
Jul 13 09:55:29 <bluelightning> so what exactly do you have in your bbappend? could you pastebin it ?
Jul 13 09:55:29 <marek__> I have bb file where is defined do_deploy_append() which is doing something but I want to override that function in bbappend
Jul 13 09:55:38 <bluelightning> oh, right
Jul 13 09:56:08 <bluelightning> if the original is a do_deploy_append it can't really be overridden, because _appends happen towards the end of parsing
Jul 13 09:56:47 <marek__> I see
Jul 13 09:56:54 <marek__> so it seems as source of my trouble
Jul 13 09:57:28 <bluelightning> where is this do_deploy_append ? is it a public layer?
Jul 13 09:57:46 <marek__> nope it's not
Jul 13 09:57:53 <marek__> and it seems it's not correct
Jul 13 09:58:05 <marek__> and must be fixed
Jul 13 09:58:55 <bluelightning> this is probably where you need to work with whoever supplied you with that layer to correct it then, that would be my suggestion
Jul 13 09:59:50 <marek__> bluelightning: thanks for help
Jul 13 09:59:56 <marek__> bluelightning: definitely
Jul 13 09:59:57 <bluelightning> the only other thing I can think of is if you could perhaps undo and redo the operation that the errant _append is doing
Jul 13 10:00:08 <bluelightning> that's a messy hack though
Jul 13 10:00:32 <bluelightning> and assumes it isn't actually failing or doing something destructive
Jul 13 10:40:49 <em|fb> hi JaMa I have a question regarding meta-qt5, fido branch: i built qt5 for beaglebone and want to try qtwebengine. Everything else runs fine (qteverywheredemo, qtwebkit) but I have problems with the qtwebengine examples
Jul 13 10:41:14 <em|fb> even the most simple website is not rendered
Jul 13 10:41:35 <em|fb> I only see a gray frame
Jul 13 10:42:49 <em|fb> do you have a hint, what could be the causing this. The engine spawns a lot of processes and I find it hard to debug
Jul 13 10:44:17 <JaMa> em|fb: last time I've tried example browser it was working for me, but I didn't test or use it any further
Jul 13 10:45:00 <em|fb> do you remember the configuration of your image? perhaps there's a missing runtime dependency
Jul 13 10:48:21 <JaMa> em|fb: something like: https://github.com/webOS-ports/meta-webos-ports/commit/28d9d018d1b074aa2b439f73e4b7763ce369d932
Jul 13 10:49:51 <em|fb> ok thanks, that doesn't really include something additional to my image
Jul 13 10:50:07 <em|fb> so I'll try to debug it further
Jul 13 11:27:45 <Hauke___> I am getting this error when applying a patch in a recipe: "can't find file to patch at input line 3"
Jul 13 11:28:05 <Hauke___> it should apply to this file: build/tmp/work/core2-poky-linux/auto-eas/git+master-r0/auto-eas-git+master/eas/gen2/csr_gen2_expbus.c
Jul 13 11:29:01 <Hauke___> and the patch contains this line to which it should apply: b/eas/gen2/csr_gen2_expbus.c
Jul 13 12:25:09 <Hauke___> is there a way to get to know on which directory yocto tries to apply a patch?
Jul 13 12:29:13 <bluelightning> Hauke___: it will be applied from ${S}
Jul 13 12:29:40 <bluelightning> Hauke___: check if S is set correctly to point to where the source is being unpacked
Jul 13 15:29:20 <dasabhi> sup
Jul 13 17:33:34 <khem`> rburton: I could not get to bottom of the glibc issue you reported yet
Jul 13 17:33:49 <khem`> it seems there is misundersranding of return value of rpcgen in recipe
Jul 13 17:33:58 <khem`> but need to confirm
Jul 13 18:17:28 <kergoth> Anyone know offhand if oe-selftest supports pulling tests from either specific external locations or BBPATH?
Jul 13 18:18:56 <bluelightning> kergoth: I didn't reply but I did look in response to your comment, I thought it did support that but I couldn't see anywhere in the code where it explicitly was looking in BBPATH, so I suspect we don't support it yet
Jul 13 18:19:12 <bluelightning> kergoth: we should change it so it does though I agree
Jul 13 18:19:22 <bluelightning> the runtime tests do support it, FWIW
Jul 13 18:19:24 <kergoth> ah, thanks. i haven't had a chance to look at it yet
Jul 13 18:19:27 <kergoth> nice
Jul 13 18:21:24 <kergoth> there, fixed it so we don't have to pointlessly re-create the argparse parser. now going to look at devtool
Jul 13 18:35:01 <mtetreault> Does anyone got xsltproc working? I have some host path reference when I try to launch it.
Jul 13 18:36:50 <kergoth> hrmph, devtool doesn't do tinfoil setup in the main tool, only in the individual commands, that's problematic since we don't want to initialize a cooker more than once. will have to fix that before we can load plugins from bbpath, since we need config metadata to get BBPATH
Jul 13 19:22:32 <kergoth> there, https://github.com/openembedded/openembedded-core/compare/master...kergoth:yocto-bug-7625 covers recipetool, devtool, and oe-selftest
Jul 13 19:42:18 <kergoth> Hmm, wonder why oeqa stuff has one method for loading tests and devtool/recipetool use an entirely different mechanism to load plugins
Jul 13 19:42:32 <kergoth> yet both essentially do the same sort of thing, just with slightly different hooks
Jul 13 19:43:55 <kergoth> Hmm, just realized I never added selftests specifically for the recipetool create python buildsystem support, that might be worthwhile
Jul 13 20:48:06 <kergoth> Hmm, oe-selftest should use imp.get_suffixes() rather than hardcoding `.py`
Jul 13 20:50:17 <wto> Has there been a recent change in the way autotools work in Yocto since daisy? I get these kinds of errors suddenly with fido: configure.ac:73: error: possibly undefined macro: AC_MSG_RESULT
Jul 13 21:18:02 <rburton> wto: recent? no.  since daisy? yes.  you probably are missing build dependencies.
Jul 13 21:18:38 <rburton> pkgconfig-native is a good one to miss (inherit pkgconfig) and leads to really odd errors when autoconf can't expand macros
Jul 13 21:21:09 <wto> That might just have been it, because it failed for a completely different reason now. Thanks!
Jul 13 23:29:43 <gabrbedd> Suppose a project normally builds an intermediate tool that it intends to execute. For example, it compiles generate-coefficients.c and then executes ./generate-coefficients > filter-table.h or something like that.
Jul 13 23:30:04 <gabrbedd> Is there a good way to enable that in a bitbake recipe?
Jul 13 23:30:28 <gabrbedd> Or do I need to split the package into a -native version so that I can get the tool?
Jul 13 23:34:19 <kergoth> just ensure that it's compiled with BUILD_CC & BUILD_CFLAGS & BUILD_LDFLAGS rather than CC & CFLAGS & LDFLAGS.
Jul 13 23:34:31 <kergoth> unless it links against a lib from that same project, of course
Jul 14 00:04:21 <gabrbedd> kergoth: ok, thanks!
Jul 14 00:09:23 <felipealmeida> hello, how do I make my image to have libgcc_s.so*
Jul 14 00:10:17 <felipealmeida> I've tried CORE_IMAGE_EXTRA_INSTALL and IMAGE_INSTALL_append, neither work
Jul 14 00:12:45 <felipealmeida> libgcc worked
**** ENDING LOGGING AT Tue Jul 14 02:59:58 2015