**** BEGIN LOGGING AT Fri Jun 02 03:00:02 2017 Jun 02 07:32:59 RP: is there an existing mechanism that can declared that the signature of a function depends on the content of some file on disk? Jun 02 07:33:36 For example do_foo () { } calling a ${MYLAYERROOT}/scripts/helper-bar.sh script? Jun 02 07:34:03 do_foo must re-execute each time helper-bar.sh gets edited (no matter what the change is). Jun 02 07:35:15 I know that this would work automatically if the helper script was turned into embedded shell methods, but that's how it is at the moment. Jun 02 07:35:35 Probably because there was a desire to have some easy way to call the helper code outside of bitbake. Jun 02 07:36:17 The approach that I know would work is to calculate a hash of the file in anonymous python, store the result in a variable, and add that variable to do_foo's vardeps. Jun 02 08:20:28 pohly: there is Jun 02 08:20:35 Hi , I would like to ask, how difficult is it of upgrading a yocto project from one branch to another branch? Yeah I know it depends of what we do, but is it something like painful ? Jun 02 08:21:07 pohly: base.bbclass:do_fetch[file-checksums] = "${@bb.fetch.get_checksum_file_list( Jun 02 08:21:21 pohly: grep for file-checksums, the format isn't quite as simple as you might first think Jun 02 08:21:41 pohly: we also list files which don't exist but we searched for so the checksum changes if they then do exist Jun 02 08:21:57 ChrysD: very variable from experience Jun 02 08:22:26 CTtpollard : if I use gstreamer / Qt shouldn't be that difficult right? Jun 02 08:22:31 ChrysD: there is a migration section in the manual, take a look and see if you think the issues mentioned will affect you? Jun 02 08:22:38 ChrysD: there is no other answer than "it depends". it can be totally smooth, with mabye two or three appends changing to a new version - and it can be super painful if specific compiler revision/libraries are needed. Jun 02 08:23:02 RP: ah, now I remember that you told me about that once before. It's not in the bitbake manual - intentionally, because it is too "internal"? Jun 02 08:23:23 pohly: no, it should be documented and if not, it should be, its public api Jun 02 08:23:33 ChrysD: if you had for example a stack of specific gstreamer patches and we changed the underlying gstreamer version that would be harder Jun 02 08:23:41 pohly: I suspect that was something else Jun 02 08:24:07 LetoThe2nd : Imagine if i come to thesituation which a specific revisionL/libraries, does disabling the actual version and adding the one in our custom meta is a good way of doing it? Jun 02 08:24:29 another popular thing is kernel compilation breaking with older/newer gcc versions. so if your kernel version is hard locked, you might be in for some fun too. Jun 02 08:24:46 RP, LetoThe2nd : ok thanks ! Jun 02 08:24:55 ChrysD: "it depends". on the number of libraries, their scale, etc. Jun 02 08:25:05 LetoThe2nd : as usual. Jun 02 08:25:54 ChrysD: you can also make use of preferred version etc Jun 02 08:26:03 LetoThe2nd : When you say hard locked, you mean that the kernel part can't be upgraded on some board? Jun 02 08:26:49 ChrysD: well there are things like *gasp* vendor kernels, that come only in a specific version, with a bunch of patches on them Jun 02 08:27:34 ChrysD: personally, I'd probably just try it and see... Jun 02 08:27:39 RP: ++ Jun 02 08:30:51 RP, LetoThe2nd, CTtpollard : Thanks BTW. Jun 02 09:23:31 im facing issue with ERROR: Task (/home/root123/work/yocto/poky/meta/recipes-devtools/cdrtools/cdrtools-native_3.01.bb:do_install) failed with exit code '1' Jun 02 09:23:59 why it is coming any idea!!1 Jun 02 09:25:41 without the log: no!!1!!one!1!ELEVEN Jun 02 09:27:40 root123@p:~/work/yocto/poky/intel$ bitbake core-image-sato Loading cache: 100% |##############################################################################################################| Time: 0:00:00 Loaded 1341 entries from dependency cache. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "1.32.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x8 Jun 02 09:28:27 ERROR: cdrtools-native-3.01a31+really3.01-r0 do_install: Function failed: do_install (log file is located at /home/root123/work/yocto/poky/intel/tmp/work/x86_64-linux/cdrtools-native/3.01a31+really3.01-r0/temp/log.do_install.27070) Jun 02 09:28:36 ERROR: Logfile of failure stored in: /home/root123/work/yocto/poky/intel/tmp/work/x86_64-linux/cdrtools-native/3.01a31+really3.01-r0/temp/log.do_install.27070 Jun 02 09:28:45 naik: usually when the build fails, it gives you the path of the log that should contain the corresponding errors/messages. so put that one onto a pastebin (not here), and then we can see. Jun 02 09:28:49 Log data follows: | DEBUG: Executing shell function do_install | ==> MAKING "install" ON SUBDIRECTORY "SRCROOT/conf" | make[1]: Entering directory '/home/root123/work/yocto/poky/intel/tmp/work/x86_64-linux/cdrtools-native/3.01a31+really3.01-r0/cdrtools-3.01/conf' | ==> MAKING DIRECTORY "/home/root123/work/yocto/poky/intel/tmp/work/x86_64-linux/cdrtools-native/3.01a31+really3.01-r0/image/home/root123/work/yocto/poky/intel/tmp/sysroots/x8 Jun 02 09:30:08 sorry but where i have to put it? Jun 02 09:30:22 pastebin? Jun 02 09:30:30 pastebin Jun 02 09:30:39 google one that you like :-) Jun 02 09:33:03 i paste it ,what next? Jun 02 09:33:14 you give us the resulting link Jun 02 09:34:51 how i can genarate link? Jun 02 09:34:59 naik : most of time there is a button Jun 02 09:35:30 naik: in the most pastebins, you drop your stuff in there, click submit, and then are redirected to the binned stuff. just paste the link of the binned stuff here. Jun 02 09:35:30 naik : in pastebin.com => Create new paste in the bottom Jun 02 09:37:49 https://pastebin.com/embed_js/CMLAzinQ Jun 02 09:38:52 is that this ? Jun 02 09:39:37 fine at a first glance Jun 02 09:41:39 naik: which version of poky is this? Jun 02 09:42:47 Morty Jun 02 09:43:27 there has been one later patch, but no idea if it is realted: http://cgit.openembedded.org/openembedded-core/commit/meta/recipes-devtools/cdrtools?id=a6816d62ae37506c8ab7a1294be23da82a2e9d6e Jun 02 09:45:00 actually i hvae been copied that {cc} line in to .bb file Jun 02 09:45:09 is that right ? Jun 02 09:45:19 or i have to patch it Jun 02 09:45:23 that pastebin looks like a run.do_install, not a log.do_install Jun 02 09:45:41 joshuagl: ++ (that would have been the next question) Jun 02 09:47:00 ohh sorry its run.do iinstall file Jun 02 09:48:14 https://pastebin.com/embed_js/BT1EuCsP Jun 02 09:52:31 line 8, it seems to be Jun 02 10:01:22 i dident get it Jun 02 10:01:28 how to resolve? Jun 02 10:01:44 line no 8 right? Jun 02 10:02:05 the install script seems to try a chgrp that fails Jun 02 10:05:35 ya ,im looking for schily this directory but its not there Jun 02 10:05:48 Any ideas how to get libbacktrace.a installed? Jun 02 10:06:53 its present Jun 02 10:07:18 no,,and why its requried? Jun 02 10:08:26 jose__: fotran, right? :-) Jun 02 10:08:36 jose__: unfortunately its totally borken at the moment. Jun 02 10:09:05 sorry ,im not getting anything Jun 02 10:09:12 naik: i guess its something by the developer that leaked in Jun 02 10:09:58 naik: so it sounds like the install script itsell is buggy, basically. Jun 02 10:11:49 ok Jun 02 10:12:10 LetoThe2nd: G++ Jun 02 10:13:10 but how to resolve ,basically when im bitbake 1st time for Qemo then its work file and its get build Jun 02 10:13:32 when im trying to build for intel H/W it gives error !! Jun 02 10:13:36 jose__: i've only seen libbacktrace being mentioned (and broken) when trying to build libgfortran, which depends on it Jun 02 10:14:19 In Debian/Ubuntu is part of libgcc-6-dev Jun 02 10:14:31 jose__: if you're using poky then that will disable all static libraries, so if you really need the .a then that's an issue Jun 02 10:14:34 maybe is libgcc 6.3.0 Jun 02 10:15:02 what to do now? Jun 02 10:15:04 ! Jun 02 10:16:43 what to do with this 1 !! Jun 02 10:17:04 naik: stop repeating, with pointless exclamation marks, please. Jun 02 10:17:05 how topatch and where i have to add this Jun 02 10:17:07 http://cgit.openembedded.org/openembedded-core/commit/meta/recipes-devtools/cdrtools?id=a6816d62ae37506c8ab7a1294be23da82a2e9d6e Jun 02 10:18:10 naik: that patch is probably not the problem. and if nobody responds the second time you ask, probably nobody has the time or knowledge to assist you at the moment. put together a concise desciption and send it to the mailing list, maybe Jun 02 10:18:53 ok thanks for help Jun 02 10:25:21 rburton: I enabled static libraries with staticdev-pkgs Jun 02 10:34:22 jose__: thats not what i meant, poky *disables* them entirely. Jun 02 10:34:31 (not relevant if you're not using poky) Jun 02 10:37:27 rburton: I using poky 2.3 building my image with bitbake Jun 02 10:52:30 jose__, poky (the distribution) disbales staticdev-pkgs, if you want them, you need to create your own distribution config and not use pky Jun 02 10:52:53 (How) can I change the compression level of my tar.bz2 image? Jun 02 10:53:47 hmm Jun 02 10:54:13 rburton, I assume this is the line that kill statsidev? Jun 02 10:54:22 http://git.yoctoproject.org/cgit/cgit.cgi/meta-yocto/tree/meta-poky/conf/distro/poky.conf#n104 Jun 02 10:54:42 but no matching file? Jun 02 10:54:43 http://git.yoctoproject.org/cgit/cgit.cgi/meta-yocto/tree/meta-poky/conf/distro/include Jun 02 10:56:02 no-static-libs.inc is in oe-core Jun 02 10:56:19 remember the mantra: poky is an example. make your own. Jun 02 10:56:34 gah Jun 02 10:56:46 no-static-libs shows what you need to undo to revert it for a specific recipe, or dynamically link instead Jun 02 10:56:47 I forgot about that path thing :) Jun 02 10:57:46 jose__, final piece of the puzzlie is in oe-ciore layer: https://github.com/openembedded/openembedded-core/blob/master/meta/conf/distro/include/no-static-libs.inc Jun 02 11:00:24 rburton : using the meta in poky repo doesn't mean that the distro is based on poky right? It's if we use the meta-poky layer no? Jun 02 11:00:52 ChrysD: you're only using poky if you have DISTRO=poky Jun 02 11:01:10 rburton : so it's more about the distro conf file, Jun 02 11:01:15 rburton : ? Jun 02 11:01:25 its all about what DISTRO you select in your configuration Jun 02 11:01:36 (or if you distro then includes poky.conf) Jun 02 11:01:46 the meta-poky layer on its own shouldn't do anything Jun 02 11:02:13 rburton : ok right. Jun 02 11:02:29 yeah even the psplash bbappend to change the splash screen is guarded with an override Jun 02 11:02:45 so adding the layer to bblayers but not using DISTRO=poky is a no-op Jun 02 11:02:53 for example that : require conf/distro/poky.conf Jun 02 11:04:47 it menas that the distro is based on poky Jun 02 11:48:25 hi, i'm trying to build qtbase accesibility for qt quick support. but when i buid i get this error: Jun 02 11:48:27 recipe for target 'egl-x11.o' failed make: *** [egl-x11.o] Error 1 EGL-X11 disabled. No QPA platform plugin enabled! Jun 02 12:58:38 pohly: I replied about the dangling appends with a counterproposal Jun 02 13:13:02 ed2: around? Jun 02 13:13:19 rburton: here Jun 02 13:14:22 | DEBUG: Executing shell function efi_bootfs_populate Jun 02 13:14:22 | install: cannot stat ‘/data/poky-master/tmp/deploy/images/intel-corei7-64/systemd-bootx64.efi’: No such file or directory Jun 02 13:14:22 ERROR: Task (/home/ross/Yocto/poky/meta/recipes-core/images/core-image-base.bb:do_prepare_wic_build) failed with exit code '1' Jun 02 13:14:30 its not wrong, that file doesn't exist Jun 02 13:14:41 with current mut which should have all your patches in Jun 02 13:15:28 rburton: ok, will look at that. Last time we both tried it worked afair. Jun 02 13:15:48 yeah Jun 02 13:16:50 which meta-intel commit do you use? Jun 02 13:30:41 Hi, is there some wiki other other pages which state how yocto supports releases? E.g. latest stable release gets one year of security etc. Jun 02 13:32:31 https://www.yoctoproject.org/downloads has a list of 'latest, active' releases, but is jethro really still supported... Jun 02 13:36:57 ther isn't a simple way to find what targets my bitbake installation currently supports, is there? that would be too easy :) Jun 02 13:43:08 berndhs: what do you mean by 'supports'? bitbake has no knowledge of what is or isn't "supported", it's a tool, not a distribution or a company. if you want to know what recipes/targets exist, just run bitbake -s Jun 02 13:44:47 berndhs: bitbake-layers show-recipes Jun 02 13:53:50 how can I set the default locale in yocto? Jun 02 14:04:37 pohly: everyone seems in agreement with the counterproposal, can I assume you might write a patch? Jun 02 14:06:12 ;-} I was hoping that you would know how to write one in five minutes and do that this afternoon. Jun 02 14:06:21 But yeah, I can have a look. Jun 02 14:15:03 rburton: I was going to add my yes, but I think you took the possibility away :) Jun 02 14:15:08 RP: ^^^ Jun 02 14:15:52 (http://lists.openembedded.org/pipermail/openembedded-architecture/2017-June/000625.html) Jun 02 14:16:45 * fray notes he doesn't have any concerns with the proposal.. but I'll refrainf rom the 'me too' on the mailing list for now Jun 02 14:18:26 kanavin: that is a different one :) Jun 02 14:19:44 RP: different? was there something else? Jun 02 14:20:31 kanavin: sorry, crossed conversations here with pohly and a patch on the bitbake list :) Jun 02 14:33:02 pohly: I can probably do it, just won't be today Jun 02 14:52:31 Hi guys, I'm having trouble compiling protobuf-c with the 6.2 linaro toolchain (recommanded choice for arago distro). sounds like an error in the path library ( can't find libstdc++.la). Did someone has seen this error before? Jun 02 14:56:23 rburton: can't reproduce that error on the latest meta-intel. Which commit do you use? Jun 02 15:02:10 ed2: i can't replicate it either right now :( Jun 02 15:02:14 rburton: did you get to bottom of why linux-4.1/mips was still failing with gcc7 Jun 02 15:02:15 i shall continue trying Jun 02 15:02:19 khem: no Jun 02 15:02:31 rburton: irrespective kernel changes can be merged without gcc7 Jun 02 15:02:48 have you added themto your consolidated pu Jun 02 15:04:36 khem: will suck them into the next batch, what's the branch? Jun 02 15:10:26 maudat: .la files are not really used during oe/yocto builds, afaik. external-linaro-toolchain packages them into *-dev package for possible SDK use Jun 02 15:11:38 maudat: but you might want to check if you have that .la file in your sysroot and if it's correct... not sure why protobuf-c requires it though Jun 02 15:18:54 denix: Indeed I have it in my sysroot. But instead of of appending lib/mlibstdc++.la after the sysroot path, what is given is /home/tcwg-buildslave/workspace/tcwg-make-release/label/docker-trusty-amd64-tcwg-build/target/arm-linux-gnueabihf/_build/builds/destdir/x86_64-unknown-linux-gnu/arm-linux-gnueabihf/lib/libstdc++.la Jun 02 15:19:33 Which is a path from linaro builder slave Jun 02 15:27:31 maudat: correct. try removing that .la file from sysroot... Jun 02 15:51:36 denix: still the same issue after removing the lib. Jun 02 16:00:38 denix: looks like dependency_libs is set with the path: dependency_libs=' -L/opt/linaro/arm-linux-gnueabihf/lib -lpthread -lz =/home/tcwg-buildslave/workspace/tcwg-make-release/label/docker-trusty-amd64-tcwg-build/target/arm-linux-gnueabihf/_build/builds/destdir/x86_64-unknown-linux-gnu/arm-linux-gnueabihf/lib/libstdc++.la' Jun 02 16:12:13 RP: I'm done for today and will return on Tuesday. If you find some time to do the BBFILES_DYNAMIC patch in the meantime, that would be appreciated. Jun 02 16:45:22 khem: all of my gcc7 branch has been merged apart from the gcc7 upgrade itself Jun 02 16:45:34 rp must have picked bits Jun 02 16:45:58 khem: where's your latest gcc7 branch? Jun 02 17:04:55 rburton: cherry pick http://git.openembedded.org/openembedded-core-contrib/commit/?h=kraj/master&id=f6bf87c048aa6fe6c9ee81f020c7da1007247bd0 Jun 02 23:01:02 hi folks, me again, having solved some of the problems Jun 02 23:01:20 i'm left iwthout wifi on the raspi3 today Jun 02 23:01:36 had some of it working, but did not survive a reboot Jun 02 23:19:20 make sure you have the funky firmware files on your rootfs. Jun 02 23:23:00 everyting is on my rootfs :) there are 2 wireless devices, the builtin and a usb dongle Jun 02 23:27:29 Confused: I have DISTRO_FEATURES pam set, but I find --disable-pam in the configure log. In fact only --enable-split-usr --enable-xz and --enable-nls are set. None of these are set through PACKAGECONFIG. What am I doing wrong? Jun 02 23:27:52 So, it looks inverted.. Jun 02 23:32:55 That is when building systemd with morty Jun 02 23:42:40 And everything that is set through PACKAGECONFIG is --disabled... Jun 02 23:52:03 Nobody? Yeah is late. I'll post on the list. Jun 03 00:44:46 how can i build qt5 without wayland? I don't want wayland, and the build fails because of it Jun 03 01:57:33 does anyone know if I can use Google Cloud Platform as a build server for yocto? Jun 03 02:53:34 berndhs: qt5 builds fine without wayland what error do u see Jun 03 02:55:07 and what distro you run on GCP ? it should fine on any cloud **** ENDING LOGGING AT Sat Jun 03 03:00:01 2017