**** BEGIN LOGGING AT Tue Sep 13 02:59:58 2016 Sep 13 06:34:56 Is there any hardware that can do: linux host --> target image file --> usb --> !pseudo micro sd! --> target device micro sd card slot ? Sep 13 06:36:07 to actually boot from host machine via sdcard not over ethernet Sep 13 06:57:57 Dear All, Sep 13 06:57:58 I've got some question regarding removing packages from images (e.g. core-image-sato, core-image-minimal). Sep 13 06:57:58 I would like to avoid creating my own distro (and hence stick to core-image-sato for example). Sep 13 06:57:58 I've created my own layer (poky/meta-my-layer) and I'm able to build packages and create images. Sep 13 06:57:58 How could I change core-image-sato to rid off ofono or bluetooth? Do I need to create poky/meta-my-layer/recipies-sato/images/core-image-sato.bbappend ? Sep 13 06:58:11 How can I remove the ofono and bluetooth? Sep 13 06:58:43 To what variable should I _remove add? Sep 13 06:59:12 To put it short - I do want to use core-image-sato, but remove some packages from this particular image Sep 13 07:04:18 lukma1: you can black list those packages Sep 13 07:10:52 qt-x: So I create core-image-sato.bbappend and there blacklist unwanted packages? Sep 13 07:11:20 qt-x: How can I see the list of all packages which are going to be installed in core-image-sato? Sep 13 07:18:15 lukma1: IMAGE_INSTALL controls what packages get installed. see http://www.yoctoproject.org/docs/2.2/ref-manual/ref-manual.html#var-IMAGE_INSTALL. Sep 13 07:18:44 the packages that those packages depend on will also get installed Sep 13 07:20:05 bitbake -g core-image-sato.bb view pn-buildlist Sep 13 07:21:57 lukma1: to view a list of packages issue `bitbake -g core-image-sato` the output list will be stored in pn-buildlist Sep 13 07:24:49 qt-x: pn-buildlist is a list of recipes though. i added some documentation at http://www.yoctoproject.org/docs/2.2/ref-manual/ref-manual.html#usingpoky-viewing-dependencies-between-recipes-and-tasks. Sep 13 07:25:06 it might give an idea of what will go into the image though Sep 13 07:25:42 Is there any IMAGE_INSTALL_remove ? Sep 13 07:26:26 I'm trying to get my touchscreen to work with wayland/weston but they don't seem to play nice to each other. Can somebody give me a hand trying to get them to work please? evtest nicely reports the touch events with correct x and y. When I've run weston-calibrator the values seem way off to me: Calibration values: 0.000000 -316.131226 -nan 0.000000 -142.259048 -nan Sep 13 07:26:49 When not using weston, the touch is working perfectly in Qt5 when using tslib or libinput, evdevtouch doesn't Sep 13 07:27:41 lukma1: it won't work if IMAGE_INSTALL uses packagegroups Sep 13 07:28:22 if e.g. some package foo is in packagegroup-bar, and IMAGE_INSTALL = "... packagegroup-bar ...", then IMAGE_INSTALL_remove = "foo" will do nothing Sep 13 07:29:08 Ulfailizer: With pn-buildlist I've found the package - ofono Sep 13 07:29:14 try to trace out what the base poky distribution does, and do something that fits with the model. i'm not very familiar with it. Sep 13 07:33:18 Ulfalizer: I'm now trying to use DISTRO_FEATURES_remove = "bluetooth ofono" Sep 13 07:33:59 but I'm not sure if this is the correct way to proceed? I mean it might happen that other images (like core-image-minimal) don't have those packages and the build fail Sep 13 07:34:07 lukma1: looking at meta/recipes-core/packagegroups/packagegroup-base.bb, removing 3g from DISTRO_FEATURES might be the right thing to do Sep 13 07:35:17 MACHINE_FEATURES also adds it if it contains "phone" Sep 13 07:36:46 so maybe DISTRO_FEATURES_remove = "phone 3q" does the trick? Sep 13 07:40:01 yeah, might work. 3g though, not 3q. Sep 13 07:40:44 :) Sep 13 07:46:27 lukma1: urr... "phone" is a MACHINE_FEATURES thing, not a DISTRO_FEATURES thing, so removing it from DISTRO_FEATURES makes no sense Sep 13 07:47:08 check what those variables default to too with bitbake -e Sep 13 07:52:46 and http://www.yoctoproject.org/docs/2.2/ref-manual/ref-manual.html#ref-features Sep 13 07:52:52 good morning Sep 13 07:58:44 Ulfalizer: Thanks for support, I will go through documentation Sep 13 08:00:04 lukma1: np. look up meta/conf/machine/ and meta/conf/distro/ too. Sep 13 08:00:29 things usually go smoother later if you try to follow the model in place Sep 13 08:00:43 though it can be a bit of work to figure out... Sep 13 08:05:19 I'm still discovering how things work in yocto Sep 13 08:05:45 For me it is natural that I have core-image-sato and on top of that I would like to do some tunning Sep 13 08:05:54 but it seems like it is not so easy.... Sep 13 08:06:46 Hey guys, I've got an issue with interrupt handling. I tried at kernelnewbies irc channel but I'm getting no response. Is any of you experienced with GPIO interrupt handling in a kernel module on arm, specificly omapl138? Sep 13 08:10:59 hello guys, Im getting the issue "requested data beyond end of section" using a linux.sb file generated from yocto (bb imx-bootlets virtual/kernel) ? Sep 13 08:11:07 I did the update using flash_erase /dev/mtd0 0 0 && kobs-ng -f linux.sb Sep 13 08:13:21 Im working with a imx28evk Sep 13 08:19:19 lukma1: the 2.2 version of the manuals clarifies quite a lot of stuff btw, in case you're reading 2.1 Sep 13 08:19:51 to create an sdk, i define an image with all the packages that i want to be includes and then run bibtbake my-sdk-image -c do_populate_sdk, right? Sep 13 08:26:09 fragfutter: just 'bitbake my-sdk-image' ought to be enough Sep 13 08:26:40 populate_sdk.bbclass has 'addtask populate_sdk after do_install before do_build' Sep 13 08:27:51 so i inherit populate_sdk inside the recipe my-sdk-image.bb Sep 13 08:28:48 can't remember the details off the top of my head. i've mostly used a weird sdk setup. Sep 13 08:29:41 you need to use TOOLCHAIN_HOST_TASK and TOOLCHAIN_TARGET_TASK to select packages for the host and target parts of the SDK at least Sep 13 08:30:54 anyway, sleepy time Sep 13 08:31:01 Ulfalizer: good night Sep 13 08:31:09 gn Sep 13 10:53:24 hello Sep 13 10:54:27 i've got a problem building the extensible SDK when i use paths relative to TOPDIR in conf/bblayers.conf Sep 13 10:54:41 building images works but not the sdk Sep 13 10:54:51 is it expected or a bug ? Sep 13 10:56:34 the line from bblaers.conf which causes this problem: ${TOPDIR}/../poky/meta Sep 13 10:57:19 generally BBLAYERS etc needs to be absolute paths anyway Sep 13 10:58:32 thanks, it cost me 2 days to find the problem, error messages are very cryptic Sep 13 10:58:37 rburton: yeah... that's a bit problematic when sharing bblayers.conf :( Sep 13 10:59:10 right Sep 13 10:59:39 sure Sep 13 10:59:52 only sdk seems to have the problem with relative paths Sep 13 11:00:11 standard sdk builds too Sep 13 11:05:13 iskander_work: it sounds like a bug, but the standard SDK and images don't try to package up the build system like the eSDK does and hence why they don't suffer from this issue Sep 13 11:37:07 yeah, i thought so too Sep 13 11:40:02 i figured out where it occurs but couldn't fix it properly, although i have a patch fixes it but not a clean one Sep 13 12:00:38 rburton: have you a set of patches ready for mut? Sep 13 12:06:46 i have a set of patches, let me subset it for the AB :) Sep 13 12:06:59 i think i just broke your m4 patch though sorry Sep 13 12:08:56 rburton: hmm, broke how? Sep 13 12:09:27 Hello Sep 13 12:09:38 RP: WARNING: matchbox-desktop-2.1-r0 do_configure: /data/poky-master/tmp-glibc/sstate-control/manifest-x86_64-wayland-native.populate_sysroot not found Sep 13 12:10:25 rburton: was this with wipe-sysroot? I suspect that is probably broken somehow. Let me try this on a clean tmp Sep 13 12:11:45 rburton: hmm, you're right Sep 13 12:12:36 rburton: could you just fix the patch? :) Sep 13 12:25:56 rburton: I think I have the logic backwards :/ Sep 13 12:26:49 JaMa: Do you know who should be responsible for the integration of Qt5.8 in meta-qt5? I might be interrested as I'm also preparing the package of Qt5.8 in OpenIndiana. Sep 13 12:34:57 running "bitbake core-image-sato -c testsdkext" fails in devtool test http://pastebin.com/MT8KRDtS Sep 13 12:35:30 it's trying to copy a symlink /home/jku/src/poky/meta/lib/oeqa/sdkext/files/myapp/oe-workdir that points to a non-existant directory Sep 13 12:36:15 alimon, alimon1 ^ any ideas? Sep 13 12:45:10 RP: see ross/for-next Sep 13 12:45:36 a pruned mut, i'll shuffle the bad bits of mut out in a moment) Sep 13 13:34:24 rburton: new version of the patch in testing is finding metadata bugs :/ Sep 13 13:35:44 hi guys, I wonder if you know the solution to my toaster problem. I followed the manual for a local webhost, but the webpage only displays "Toaster has not recorded any builds yet. Run a build from the command line to see it here." I understand it cannot display builds yet, but i'm looking how to start the build, not the report. Thank you! Sep 13 13:35:46 RP: that's good right? Sep 13 13:38:08 jonver_: what version of yocto project are you using? Sep 13 13:38:10 rburton: probably Sep 13 13:38:18 @belen jethro Sep 13 13:42:15 jonver_: sorry, had to look at what the jethro version included. If you want to start your builds with toaster, you need to make sure you are running it in "build" mode as explained here http://www.yoctoproject.org/docs/2.0.2/toaster-manual/toaster-manual.html#starting-toaster-for-local-development Sep 13 13:43:53 jonver_: without sourcing the build environment script and from the poky directory run $ bitbake/bin/toaster Sep 13 13:45:04 belen: i see, i did the instructions for analysis instead of build. that will help, thanks! Sep 13 13:45:23 jonver_: no worries. Any other questions, let us know Sep 13 13:50:47 rburton: new version of the patch passes the -desktop test at least Sep 13 13:50:58 great Sep 13 13:51:19 if i need to package a python library with the sdk, create a recipe, recipe inherits setuptools and inherits native? Sep 13 14:08:29 hi! could someone enlighten me what this error means? https://gist.github.com/jomag/c4e439cfd3ddf16c55099b545832e1f0 Sep 13 14:08:38 i got it when i switched to another kernel recipe Sep 13 14:09:10 Another question :) are there any tools available to convert an "FSL Build Enviroment Setup Script" and load it in toaster? Sep 13 14:09:44 it seems to still look for the old kernel (4.6.7-amun-bbg). the new kernel is 4.4.9-amun-ti-bbg. Sep 13 14:13:39 jonver_: I am going to say … no? :) Can you tell me a bit more about what you are trying to do / build? Sep 13 14:15:11 belen: i have this build script for my HW https://github.com/varigit/meta-variscite-mx6ul-mx7/blob/imx_4.1.15_ga-var01/scripts/var-setup-release.sh . Now, I try to use toaster instead of this script so i can modify and add more layers. But I need to 'import' these settings first. Sep 13 14:15:49 present: nobody is responsible as it's community project and I haven't seen anyone volunteering yet, I was told yesterday that Samuli is probably preparing 4.8 in Qt Company meta-qt5 fork Sep 13 14:26:09 jonver_: right, big caveat here, I have never tried to build that layer with toaster, and I am not sure what the custom script is doing. But you can set MACHINE, DISTRO, IMAGE_INSTALL_append and add layers to bblayers.conf using toaster. You will have to do it manually using the UI though: there is no way of importing configuration from a custom script like the fsl one Sep 13 14:27:13 belen: ok thanks, that's what i expected, but now i'm sure :) manually it is. Sep 13 14:36:04 JaMa: Thanks! I'll try to get in touch with him then. Sep 13 14:39:25 JaMa: Otavio Salvador is still on the github page also. Sep 13 14:39:58 I'll be glad to get in touch with Samuli then. Sep 13 14:52:11 JaMa: By the way Qt5.8 seems to be far from compiling smoothly now. It's may be too early to work on the integration already. Sep 13 15:15:10 jku: no ideas, i'm wondering why the oe-logs folder is on test data fixture folder Sep 13 15:24:17 hi! I am getting this sanity check error on a .pc file and it looks like there is an absolute path looking like this: Libs.private: -L/path/to/qemux86-64/usr/lib Sep 13 15:24:33 my question is: how did that path get in there? Sep 13 15:33:41 JaMa: gcc5 cant compile Qt. => gcc49 seems ok Just had to remove xcb for now. Sep 13 15:36:24 I have a recipe which fails parsing (because the layer is really for a newer version of poky), is there a quickfix where I can disable parsing of that specific recipe from local.conf or bblayers.conf? Sep 13 15:36:49 present: what about gcc6? Sep 13 15:37:04 that's the default in current oe-core Sep 13 15:37:05 I've just built qt4e with gcc6 Sep 13 15:37:10 sveinse: don't use layers with mismatched branches. beyond that, you can use BBMASK if you absolutely have to Sep 13 15:37:56 kergoth: thanks. my use-case warrants it for now. and it's my layer :P Sep 13 15:38:09 i tried building python-scons-native. Bitbake runs and completes but it creates no package (rpm)? Sep 13 15:38:22 native recipes are for the host, for the build process. they aren't packaged, ever Sep 13 15:38:33 if you want host binaries for an sdk, use nativesdk recipes and add them to TOOLCHAIN_HOST_TASK Sep 13 15:39:00 nativesdk, ok. Sep 13 15:39:51 JaMa: Ouch... I'll have to make it work on gcc49 and gcc6 then. gcc49 for OpenIndiana and gcc6 for Yocto... really gcc6 as default?!? Sep 13 15:39:57 any example for a python nativesdk package? (adding an additional module) Sep 13 15:40:46 JaMa: It's not far too early to use gcc6 as default?! Sep 13 15:42:01 anyone built pyqt5 Sep 13 15:42:04 jmesmon: Thanks for the information! Did you try Qt58 also? Sep 13 15:42:54 JaMa: A friend just told me that aarch64 is weel supported with gcc6 Sep 13 15:43:22 *well Sep 13 15:43:29 present: not on gcc6. I've built qt5 on gcc5, though. Sep 13 15:43:36 I'd expect it to work. Sep 13 15:43:54 jmesmon: 5.7 then because I can't anything with Qt58 and gcc5 Sep 13 15:44:18 idk. This was back when poky master was using gcc5 as the default. Sep 13 15:44:47 I'd recommend just using gcc6 Sep 13 15:44:51 jmesmon: Internal compiler error with c++11 and c++1z Sep 13 15:45:23 k I'll install gcc6 then :) Sep 13 15:47:20 Hmm, BBMASK can be used in local.conf as well, right? Sep 13 15:48:09 sveinse: bitbake doesn't care what file a variable happens to be defined in, as long as it's set Sep 13 15:48:11 so yes Sep 13 15:48:17 BBMASK += "/meta-lm-sp/recipes-packages/networkmanager/ " still gets ParseError at /srv/builds/can-image/src/meta-lm-sp/recipes-packages/networkmanager/networkmanager_1.2.0.bb Sep 13 15:48:22 now, if your distro sets it with = and not ?= or +=, then it'll override it Sep 13 15:48:36 are you using a recent enough bitbake to support a space-separated BBMASK? Sep 13 15:48:39 that's a recent feature Sep 13 15:48:43 before that, it was a single regex Sep 13 15:49:29 1.28.0 it seems Sep 13 15:50:06 no idea what version it was added in, offhand Sep 13 15:53:01 sveinse: try BBMASK ?= "(?!)" BBMASK .= "|/meta-lm-sp/recipes-packages/networkmanager/" , or something. Sep 13 15:55:42 jmesmon: Yep. BBMASK.="|.*/path" <-- and no trailing / did it. Thanks Sep 13 15:57:03 Building consistent configuration management when building on top of other's cm-systems is not easy! Sep 13 15:59:00 I understand repo is gaining traction in the community Sep 13 16:17:54 present: new qt releases are always pain to get working with all the meta-qt5 patches we need, more so when they are in alpha phase like 5.8 now Sep 13 16:18:00 `repo` as in google's multi-git-repository-source thing for android? Sep 13 16:18:07 yes Sep 13 16:18:34 i quite like repo. i do wish it used something other than xml, but that's fairly minor, really. Sep 13 17:40:23 Hi, I'm having problems with raspberrypi3 and pulseaudio, I need alsa-plugins-pulseaudio-conf but its not provided Sep 13 17:40:31 I guess its bsp specific? Sep 13 17:44:33 apparently its used to redirect alsa devices to pulseaudio server first? Sep 13 17:44:46 I meant alsa applications Sep 13 17:49:15 I cant seem to find any alsa-plugins-pulseaudio-conf Sep 13 17:49:49 is it possible its provided under alsa-plugins_1.1.0.bb? Sep 13 18:02:18 are there any pulseaudio guides for yocto? Sep 13 18:03:20 I need it because I use ympd Sep 13 18:03:25 which needs mpd Sep 13 18:11:31 fenrig: look in meta/recipes-multimedia/alsa/alsa-plugins_1.1.1.bb. looks like "pulseaudio" needs to be in DISTRO_FEATURES. Sep 13 18:12:22 DISTRO_FEATURES in local.conf? Sep 13 18:13:17 I tried setting it in local.conf :D lets check if its fixed Sep 13 18:13:20 might work, but probably not the intended way. look up meta/conf/distro/ and the like. Sep 13 18:18:11 fenrig: it's a good idea to set things up so that you can easily search recursively for stuff by the way Sep 13 18:18:59 https://dpaste.de/FmYf there's the bash helper i use. can use it like 'g FOO', 'g -i case_insensitive', 'g -w wholeword', etc. Sep 13 18:19:59 I'll take a look later Sep 13 18:20:05 local.conf fixed it by the way :D Sep 13 18:20:16 but I have to go, thx for your help :D Sep 13 18:20:38 np... if this is longterm, try to get a feel for what the "intended" way is though. saves pain down the road. Sep 13 18:21:22 openembedded is quite odd to get the "intended way" im still playing with it Sep 13 18:21:33 adding my own recipes trying to set up a rpi3 Sep 13 18:21:36 yeah, some stuff could be better documented Sep 13 18:21:44 and an rpi1 using the same image bb recipe Sep 13 18:21:45 :D Sep 13 18:22:23 Ulfalizer: your help was very welcome, thx Sep 13 18:37:03 RP: any objections to breaking up parseBaseConfiguration() at some point? not a priority, but it's currently not possible for bitbake-layers to only parse bblayers/layer.confs, it's forced to parse bitbake.conf even if it doesn't need it, which means you can't use bitbake-layers to remove a problematic layer if that layer broke parsing of the metadata. Sep 13 18:37:23 not possible without duplicating internal code, anyway Sep 13 19:38:03 rburton: out of curiosity, where is this buildstats-diff script, is it available outside oe-core? Sep 13 19:39:54 kergoth: oe-contrib, marquiz/buildstats-diff or something Sep 13 19:40:33 ah, there it is. http://git.openembedded.org/openembedded-core-contrib/log/?h=marquiz/buildstat-compare Sep 13 19:40:35 cool, thanks Sep 13 20:24:49 hello! Sep 13 20:26:58 I am still trying to debug this sanity test error: failed sanity test (tmpdir) in path [pkgconfig] Sep 13 20:27:38 I noticed that the .pc file has a config like this: Libs.private: -L/path/to/qemux86-64/usr/lib Sep 13 20:28:19 I'm not sure how the absolute path gets in the config as I don't have a reference to it in the .bb file Sep 13 20:41:50 nisha: fetch the source code that's being built and check how it generates the .pc file Sep 13 20:43:13 it probably has some template that's used to generate the .pc file, and it might be substituting the wrong path in that Lib.private line Sep 13 20:43:51 it probably "just happens" to work when not cross-compiling Sep 13 21:21:14 kergoth: no objection Sep 13 21:53:27 hi Sep 13 21:54:03 is there anybody out there? Sep 13 22:02:50 just nod if you can see me Sep 13 22:08:18 *nod* Sep 13 22:09:05 so, i've been trying to install gfortran on my intel galileo with yocto Sep 13 22:09:30 but the gcc recipe doesnt generate any gfortran binary Sep 13 22:10:09 i'm actually using ostro-project as my base image Sep 13 23:09:02 dangpzanco: i was (mis)quoting some lyrics. not sure about gfortran. :) Sep 13 23:14:35 hahah, pink floyd <3 Sep 13 23:14:56 well, actually I need to install scipy in there Sep 13 23:15:15 scipy needs a BLAS/LAPACK package Sep 13 23:15:23 which needs fortran Sep 13 23:15:25 so Sep 13 23:15:43 scipy->libatlas->gfortran Sep 13 23:30:56 dangpzanco: meta-poky/conf/local.conf.sample.extended has a note about fortran. not sure if it's up-to-date though. Sep 14 00:15:16 bit obfuscating that a lot of code uses stuff like foo[0], foo[1], etc., for fields instead of assigning them to meaningful names. have to trace backwards to see what they actually are. Sep 14 00:15:40 since they're used multiple times, assigning to name probably wouldn't affect performance either Sep 14 00:15:44 *whine* Sep 14 00:15:56 *assigning to names Sep 14 00:16:27 is there a cmake via bitbake expert that I can help with some questions? Sep 14 02:40:34 Ulfalizer: thanks for your help, I tried uncommenting the lines on local.conf.sample.extend and tried what was decribed on this post http://www.jumpnowtek.com/yocto/Add-Fortran-support-to-a-Yocto-build.html Sep 14 02:40:47 it did not work Sep 14 02:40:55 fortran was compiled Sep 14 02:41:01 but the tests failes Sep 14 02:41:04 falied* Sep 14 02:41:13 failed** Sep 14 02:41:34 checking whether the GNU Fortran compiler is working... no Sep 14 02:50:44 dangpzanco: is that while configuring the program you're trying to build with it? Sep 14 02:51:43 you could check if the fortran compiler got built at least. http://www.yoctoproject.org/docs/2.2/ref-manual/ref-manual.html might be helpful to check package contents. Sep 14 02:51:53 urr Sep 14 02:52:04 http://www.yoctoproject.org/docs/2.2/ref-manual/ref-manual.html#viewing-package-information-with-oe-pkgdata-util Sep 14 02:52:31 it'll appear inside tmp/ then as well, e.g. in the gcc ${WORKDIR} Sep 14 02:57:21 might have more luck on the mailing lists **** ENDING LOGGING AT Wed Sep 14 02:59:58 2016