**** BEGIN LOGGING AT Fri Feb 26 02:59:58 2016 Feb 26 04:37:41 Hi , i'm building yocto fido branch with that i'm getting do_configure error for gcc https://paste.kde.org/pxdjjnezy, can anyone please help Feb 26 10:09:32 JaMa: regarding ne10: Feb 26 10:09:41 $ eu-findtextrel libNE10.so.10 -> modules/dsp/NE10_fir.neon.s modules/dsp/NE10_iir.neon.s modules/dsp/NE10_fft_float32.neon.s modules/dsp/NE10_fft_int32.neon.s modules/dsp/NE10_fft_int16.neon.s not compiled with -fpic/-fPIC Feb 26 10:09:56 so it seems to be in the asm code itself Feb 26 10:15:38 then at least add INSANE_SKIP Feb 26 10:25:18 yeah. still need to experiment with it a bit though. what's strange is that apparently opus 1.1.2 is *slower* than 1.1 , at least with ne10, which is surprising. might be an error in the measurements, but I need to be sure. Feb 26 16:07:38 | NOTE: qmake prevar substitution: ' --disable-static CONFIG+=OE_BLUEZ_ENABLED' Feb 26 16:07:38 | ***Unknown option --disable-static Feb 26 16:07:45 know issue ? Feb 26 16:07:50 known Feb 26 16:08:17 sounds like you need to set DISABLE_STATIC = "" in that recipe Feb 26 16:08:39 or not pass in EXTRA_OECONF.. Feb 26 16:09:23 that's qtsystems_git.bb Feb 26 16:09:49 so I'd pretty much prefer not touching it without my emergency bucket Feb 26 16:10:22 might be something you want to move to the qmake class, unless some people using qmake can support that Feb 26 16:10:28 literally know nothing about qmake Feb 26 16:12:33 I think we need to establish a policy -- either EXTRA_OECONF is meant for autoconf, or it's meant for anything with configuration. If the latter, we can probably remove a bunch of extra vars that people added for other systems, and if the former, then we should stop abusing it everywhere and add a variable to control what variable PACKAGECONFIG manipulates Feb 26 16:12:40 currently we're a hodgepodge of the two Feb 26 16:13:16 agreed Feb 26 16:34:35 kergoth: yes it's abused by qmake bbclasses, introducing separaate variable just for PACKAGECONFIG would be nice and clean Feb 26 16:36:30 abelloni: did you include the new .inc file for disabling static in your distro? Feb 26 16:38:35 no, I just switched the branches from jethro to master and started the build Feb 26 16:40:05 should I do anything ? Feb 26 16:40:32 there is new meta/conf/distro/include/no-static-libs.inc Feb 26 16:40:46 but that's not included in default oe-core nodistro setup Feb 26 16:41:50 if you use other configuration you need to check where it includes this .inc and undo it or fix all issues caused by it as suggested by rburton and kergoth Feb 26 16:45:19 abelloni: maybe you're using poky DISTRO which enables it by default now.. Feb 26 16:45:38 indeed Feb 26 16:45:48 that's what I'm testing Feb 26 16:46:36 see, your fault for choosing wrong DISTRO :) Feb 26 16:47:03 patches for meta-qt5 are welcome Feb 26 16:47:35 I was thinking the reference distribution was sort of tested Feb 26 16:48:38 well, I'll do build without poky now Feb 26 16:48:46 only with oe-core Feb 26 16:48:46 but only with some layers Feb 26 16:49:36 abelloni: read this thread http://lists.openembedded.org/pipermail/openembedded-core/2016-February/117515.html Feb 26 16:51:39 abelloni: non-core layers are still catching up Feb 26 16:51:50 which is a situation you'd better get used to if you're going to track master :) Feb 26 16:52:13 ok, thanks for the pointer Feb 26 16:53:19 what's funny is that buildroot has an option to only use static libraries and remove all the dynamic ones Feb 26 16:54:27 that's a good point for my elc talk ;) Feb 26 16:54:50 let us know if you need help bashing buildroot :) Feb 26 16:56:26 I could see having both eventually. shared are best for 90% of cases, but there are folks who want static for certain things Feb 26 17:00:23 abelloni: poky is basically a qa test engine for oe-core, if you use it for anything else then you need to follow what it does Feb 26 17:00:50 mel is poky-based, mainly so i don't have to copy and paste a ton of it, but we closely monitor what changes in it Feb 26 17:01:05 and override a few things Feb 26 17:01:53 should some of this be moved to nodistro? Feb 26 17:02:24 rburton: yeah, I'm using poky to test meta-atmel, usually, I'm using nodistro for real projects Feb 26 17:02:57 JaMa: there's very little in poky apart from enabling some pieces we want to see tested, but will likely get hatemail for enabling in oe-core ;) Feb 26 17:03:12 if theres something you see that should be enabled by default send a patch :) Feb 26 17:03:40 that was just reaction for "copy and paste a ton of it" Feb 26 17:03:53 Crofton|work: I'll probably ask for clarifications around some features Feb 26 17:04:04 I don't use poky anywhere Feb 26 17:04:47 but if at least half ton can be considered useful for everybody.. **** BEGIN LOGGING AT Fri Feb 26 17:11:54 2016 Feb 26 17:18:21 JaMa: i doubt thats the case Feb 26 18:12:14 if I build an image without debug-tweaks, what is the password? Feb 26 18:56:22 BTW, if anyboady has ideas for my elc talk, don't hesitate to contact me Feb 26 18:56:34 the goal is to be factual ;) Feb 26 18:58:38 facts are overrated Feb 26 19:47:25 abelloni, add enough cute animal pictures Feb 26 19:50:25 JaMa: I have a failure in WTF::AtomicString in qtwebkit and I want to say WTF?! :) **** ENDING LOGGING AT Sat Feb 27 02:59:58 2016