**** BEGIN LOGGING AT Wed Jul 30 03:00:01 2014 Jul 30 09:58:47 morning all Jul 30 09:59:22 hi bluelightning Jul 30 09:59:27 hey woglinde Jul 30 10:20:44 woglinde: I just realised I didn't answer your question last night - sorry about that Jul 30 10:20:53 did you figure it out in the mean time? Jul 30 10:33:00 JaMa: so are you going to apply your patch to do recipes-python -> recipes-devtools? Jul 30 10:44:41 bluelightning: waiting for opinions from others Jul 30 10:45:20 I'm OK with it FWIW, but I think we need to do it sooner rather than later Jul 30 10:45:56 ok, I'll push it today (it was in master-next since behining Jul 30 10:49:28 ok, great - thanks Jul 30 10:51:47 not sure if I mentioned btw, but in case anyone is interested I am working on an update for mariadb to 5.5 Jul 30 10:52:03 it hasn't been entirely straightforward, but I'm getting there Jul 30 10:52:45 cool thanks Jul 30 11:16:09 bluelightning no see my Email Jul 30 11:43:19 bluelightning: why not to mariadb 10? Jul 30 12:19:35 hrw: good question... not being much of a mariadb user I don't have a feel for the differences Jul 30 12:22:37 bluelightning: can you please check my last comment in https://bugzilla.yoctoproject.org/show_bug.cgi?id=4790 Jul 30 12:22:57 bluelightning: not sure if it should be reopened or new ticket created Jul 30 12:25:33 JaMa: hmm, I must be missing something - the patch is deleted but the recipe still refers to it, so the warning looks legitimate to me unless there is another step in between... Jul 30 12:26:32 ah sorry, my fault Jul 30 12:26:42 I haven't noticed that it still references it Jul 30 12:26:57 it might have been easier to tell if the sender had used -M Jul 30 12:28:09 right, I've sent comments to ML Jul 30 17:29:16 ERROR: Nothing PROVIDES 'xbmc' Jul 30 17:29:21 ERROR: xbmc was skipped: Recipe is blacklisted: /usr/include/c++/ctime:70:11: error: '::gmtime' has not been declared Jul 30 17:29:21 can can i solve this? Jul 30 17:30:21 i c: PNBLACKLIST[xbmc] = "/usr/include/c++/ctime:70:11: error: '::gmtime' has not been declared" Jul 30 17:31:30 in your local conf.. Jul 30 17:31:34 PNBLACKLIST[xbmc] = "" Jul 30 17:31:39 try to build it, fix it, submit a patch Jul 30 17:31:53 these types of things get blacklisted because nobody has stepped up to fix the items Jul 30 17:36:12 xbmc has long history of build issues nobody steapped up to fix, this was only last drop Jul 30 17:37:18 yup.. I strongly encourage anyone who wants to use it to fix the issue and submit back the fix Jul 30 17:37:37 ok Jul 30 17:37:38 thanks Jul 30 17:38:31 agreed, fixes are always very welcome Jul 30 17:44:03 that gmtime error needs patching its configury mostly Jul 30 17:45:45 probably its conflicting with gnulib Jul 30 17:46:04 and is confused when crosscompiling Jul 30 17:47:17 and it's using ctime from host instead of sysroot Jul 30 20:03:21 anyone trie dto build a SDK recently with Qt5 included? Jul 30 20:10:38 I'm seeing it fail due to qtquickcontrols-qmlplugins package missing Jul 30 20:10:45 see http://pastebin.com/uHdCLv4k Jul 30 20:10:57 Want to check before I submit a patch Jul 30 20:12:18 darknighte: you're missing icu or accessiblity in qtbase PACKAGECONFIG Jul 30 20:12:53 JaMa, I noticed the comment in qtbase.inc about accessibility, but explicitly enabling it did not seem to fix it. Jul 30 20:13:18 FWIW: I would accept patch to make it RRECOMMENDS instead of RDEPENDS, because many people are hit by this Jul 30 20:13:19 do I need to enable both icu and accessibility explicitly? Jul 30 20:13:26 yes Jul 30 20:14:19 ahhh, k. makes sense now. perhaps qtbase.inc comment should be updated as well? Jul 30 20:14:51 darknighte: it's with daisy, right? Jul 30 20:15:02 it's already RRECOMMENDS only in master (see 7dd1fcdecb4c20156fa88edf8d3f090b9b8692cd) Jul 30 20:15:03 JaMa: correct Jul 30 20:15:30 I'll cherry-pick it to daisy Jul 30 20:16:24 thx JaMa. Jul 30 20:16:28 a94c35bdad832861474a87852dad9000ee0d0c8b is in daisy too Jul 30 20:16:36 can you check what revision do you have? Jul 30 20:16:44 stand by Jul 30 20:17:05 go! Jul 30 20:17:08 :) Jul 30 20:17:41 7a8f5fe098c4a553249710f6869c01bac888d398 Jul 30 20:18:27 time to update :) Jul 30 20:18:30 ahhh, looks like I'm a bit out of date... Jul 30 20:18:50 hehe... if only it was that easy... Jul 30 20:19:08 I have to roll the change to the entire team and that won't happen quickly. Jul 30 20:19:38 if you figure out which PACKAGECONFIG options you were missing, then improved comment in qtbase.inc and/or packagegroup-qt5-toolchain-target would be welcome Jul 30 20:21:43 * darknighte nods Jul 30 20:21:55 I can say that accessibility by itself was not enough Jul 30 20:22:03 I will fiddle with it a bit Jul 30 21:11:00 RP, "binutils-cross-canadian: Explicitly DEPEND on nativesdk-flex, we require it anyway" Jul 30 21:11:39 RP, I'm having problems building nativesdk-flex with meta-mingw Jul 30 21:14:49 Not sure I understand why nativesdk-flex is needed Jul 30 21:37:09 kroon: for mingw we need to remove the dependency Jul 30 21:37:20 kroon: it was "floating" in that it was linking to it Jul 30 21:37:46 RP, aha, one of those again.. Jul 30 21:37:56 kroon: fray_ was going to send a patch for that afaik Jul 30 21:39:07 RP, ok Jul 30 22:21:48 RP, fray_, although I'd argue that ar/ranlib from binutils shouldn't link with libfl.so to begin with if they aren't needed Jul 30 22:22:40 ar and ranlib are definitely needed.. Jul 30 22:23:28 fray_, sorry, typo, I mean if they don't need to link with libfl.so, they shouldn't Jul 30 22:23:49 I agree Jul 30 22:28:44 As I understand it, libfl.so provides stub implementations for yylex()/yywrap(). But most projects seem to implement them themselves, but still link with libfl.so Jul 30 23:02:17 JaMa: otavio: the commits to remove example.pro on the meta-qt5 daisy branch appear to be broken Jul 30 23:04:06 JaMa: otavio: in that the source archive (on my system at least) doesn't have that file **** ENDING LOGGING AT Thu Jul 31 03:00:00 2014