**** BEGIN LOGGING AT Thu Aug 17 03:00:00 2017 **** BEGIN LOGGING AT Thu Aug 17 04:44:25 2017 Aug 17 07:22:16 Hi, should exporting environement variables work also in jethro by adding it to BB_ENV_EXTRAWHITE and exporting it from local.conf as described in https://www.yoctoproject.org/docs/latest/bitbake-user-manual/bitbake-user-manual.html#passing-information-into-the-build-task-environment ? It sounds like an old feature but isn't working for me when trying to use eatmydata via LD_PRELOAD to host tools. Aug 17 09:10:58 1. Anyone know how to setup u-boot fw_utils for sd card on mx7dsabresd. 2. is there a freescale/nxp/imx channel on freenode? Aug 17 11:24:48 hi o/ Aug 17 11:24:57 I'm looking where the "strip" machinery is Aug 17 11:25:59 I have some 'extern "C" __attribute__ ((visibility(default))) int foo();' which are removed Aug 17 11:37:04 hmm, what to do about mc breaking in meta-gplv2 due to ncurses changes :/ Aug 17 11:54:16 'Noon Aug 17 11:56:46 Can anyone tell me what Im missing when adding a recipe for a python utility? (bearing in mind Im not a python expert) - I've copied python-enum34_1.1.6.bb as an example, but the python files don't seem to end up in the image in the path for the interpreter to find. Am I missing something obvious? Aug 17 12:05:47 pev: does something put the correct package onto the image (either you in image or local configuration or another recipe using RDEPENDS)? Aug 17 12:06:39 jku: Thats what I dont see - the recipes Ive looked at dont do this explicitly, so wondering how the mechanism works... Aug 17 12:11:30 pev: so do you need an example of one of the options I mentioned? "git grep python-enum" will show you a couple of other recipes runtime depending on python-enum Aug 17 12:14:12 jku: Ah, OK, that inherits pypi - that looksl like it does some implicit magic... Aug 17 12:17:53 pev: no magic for runtime dependencies as far as I know... if you want a module installed in your image, something needs to explicitly say so Aug 17 12:48:21 Could someone please help me work out why a version of a recipe is being used from meta-openembedded/meta-oe/recipes-connectivity rather than my lovingly created one under meta-/recipes-connectivity/ser2net ? Aug 17 12:51:39 `bitbake-layers show-recipes ser2net` shows the v2.9.1 version from meta-oe and the v3.1 version from meta-. `bitbake -s | grep ser2net` shows :3.1r0 listed after :2.9.1. Aug 17 12:53:27 TafThorne: IIRC layer priority matters more than recipe version number Aug 17 12:54:17 meta-oe layer BBFILE_PRIORITY is 6 whereas my layer priority is 5. I guess that is the issue. Aug 17 12:54:46 So I need to either bump my layer priority up (should be fine) or set a prefered version somewhere. Aug 17 12:55:03 yes, sounds correct Aug 17 12:55:05 jku: thank you. Aug 17 12:57:00 Can I get a bitbake-layer priority list somehow? Ah yes `bitbake-layers show-layers` does that. I can see some things are 5,6,7,8 and 8 in my setup. My layer is relatively low it seems. Aug 17 12:58:29 jku: so if I set the layer priority equally (both to 6) would the version then be enough to tip the balance? I'll try it out. Aug 17 12:58:29 Is there a way to see which recipie is going to get used? Is that what the orderign in bitbake -s means? Aug 17 13:00:43 Ah yes. Now I made the layer priorities even `bitbake -s` only shows the 3.1 version. The overlayed is still shown under `bitbake-layers show-overlayed`. Thank you for the help. Aug 17 13:49:24 does anybody happen to know how to exit the bitbake ncurses ui? (ran a bitbake command with the -u ncurses flag) Aug 17 13:59:05 heycot: Ctrl+ c? Aug 17 13:59:34 heycot: or possibly d, z (and then end the backgroudned job) Aug 17 13:59:51 I am guessing though Aug 17 14:21:29 Hi, does anyone has experience with static linking of a qt program with yocto and meta-qt5? i am trying to get my qt application build static. I constantly get an installed-vs-shipped error on qt5 plugins Aug 17 14:24:51 installed-vs-shipped means that the install target of the build system of whatever recipe fails installs files that the recipe doesn't put into a package Aug 17 14:25:08 On linking Qt statically, you should make sure you understood the licensing consequences of that. Aug 17 14:29:58 i am aware of the licensing consequences. The qtbase recipes failes on plugins like libqico.a but i dont understand why i receive the shipped-vs-installed error, because i dont want these files to be included in the filesystem because the application should be linked statically Aug 17 14:39:40 but maybe the way i compile the qt5base receipe is wrong. I changed the qt5base_git.bb QT_CONFIG_FLAGS from -shared to -static Aug 17 14:46:44 timon_: I'd guess there's probably a line somewhere that would package libqico.so into a -plugins package Aug 17 14:47:05 But now that this is a static library, the expression lib*.so probably used for this no longer matches and that's why you see the installed-vs-shipped error Aug 17 14:47:20 Although I'm not quite sure how to deal with Qt's plugins when linking statically Aug 17 16:03:11 RP: I fixed the musl/mesa/llvm case as well as rootfs selfcheck errors. But I am not able to reproduce the x32 errors, I was able to build sato image and boot it into qemu for x32 successfully Aug 17 16:07:47 khem: ok, I'll try and retest but I have that many failures and infrastructure issues, test cycles are limited atm Aug 17 16:10:25 RP: yeah no problem. Aug 17 16:13:28 khem: and thanks for the fixes btw, I appreciate then! Aug 17 16:42:23 RP: thx, sent another patch for systemd-boot, which makes clang build oe-core world cleanly on x86 now Aug 17 17:01:53 * sgw hello Aug 17 17:02:54 *hello* Aug 17 17:23:49 hello Aug 17 17:24:00 is it possible to get the compiler version in a recipe ? Aug 17 17:24:11 and enable compiler options based on that ? Aug 17 17:30:20 anyone working on this? ERROR: No recipes available for: Aug 17 17:30:20 /home/mattsm/lgi/oe-rpi3-master/meta-raspberrypi/recipes-multimedia/gstreamer/gstreamer1.0-omx_1.10%.bbappend Aug 17 17:33:27 just rename it to 1.12%.bbappend Aug 17 17:39:39 JaMa sure i can build that, but not sure if gstreamer omx is working (i'm not even building that) Aug 17 17:41:01 I've renamed it to at least keep my world builds going, I also don't use it in runtime Aug 17 17:41:50 i guess i can try to build this and see if it at least builds Aug 17 17:42:02 or a general BB_MASK until it's fixed.. Aug 17 18:10:04 if a "devtoop modify" a recipe then do some kernel source changes, thenshouldn't i then be able to "devtool build-image " ? Aug 17 18:10:55 correction, do a "devtool build" successfully first after the source tree changes, THEN shouldn't i then be able to "devtool build-mage "board-image>" Aug 17 18:13:32 i am getting an error, pxp_lib.h:19:30: fatal error: linux/pxp_device.h: No such file or directory: #include Aug 17 18:13:54 i've not touched anything remotely connected to that file Aug 17 18:14:28 and the project builds the image successfully via a normal bitbake Aug 17 18:15:19 i am following the procedure in the middle of the graphic in section 2.4.2 here: http://www.yoctoproject.org/docs/2.2/sdk-manual/sdk-manual.html#using-devtool-in-your-sdk-workflow Aug 17 18:16:08 "devtool build " works fine. Aug 17 18:19:04 or is this going to be another useless day posting questions here? Aug 17 18:58:41 top22: no, and I would rather say dont look for version but instead probe for option Aug 17 18:58:51 or feature you need Aug 17 18:59:09 mattsm: I have it in works Aug 17 19:00:47 yates: keep in mind that devtool expects a recipe to work properly in externalsrc env, some recipes are not friendly to externalsrc Aug 17 19:01:02 yates: which package you are building using devtool modify ? Aug 17 20:02:58 khem is it more than the rename? Aug 17 20:03:04 the rename built, but untested by me Aug 17 21:05:03 khem: thank you for responding. Aug 17 21:05:29 khem: i don't understand what "externalsrc" is. i've googled and read but i don't get it. Aug 17 21:06:15 i was building the kernel recipe Aug 17 21:11:44 mattsm: it would need testing, if you can play youtube on wpe then you have tested it Aug 17 21:12:16 yates: its an external directory where you extract sources for a componnet and use it from there in OE build Aug 17 21:14:25 khem i have no rpi3's with video, eww ;) Aug 17 21:34:37 mattsm: ok. no worries Aug 17 22:31:19 khem: where and how is it defined? in the build/conf/local.conf? Aug 17 22:41:27 yates if you read about devtool in manuals you will get the accurate info **** ENDING LOGGING AT Fri Aug 18 03:00:01 2017