**** BEGIN LOGGING AT Wed Aug 30 03:00:00 2017 Aug 30 03:03:28 I made 7 custom recipes for python packages that seem to be OK for now. If I have a recipe that has a dependence on, python3-flask, for example, do I need to add IMAGE_INSTALL_append = " python3-flask" (which is already part of the yocto default recipes seemingly), or will it automatically fetch and install it form e? Aug 30 03:05:29 for me* Aug 30 03:05:58 you'll most likely want to add to RDEPENDS_${PN} Aug 30 03:06:06 that becomes the runtime dependencies of the binary package Aug 30 03:06:16 DEPENDS = build time, RDEPENDS_ = runtime Aug 30 03:27:34 But if you do RDEPENDS, doesnt that mean that you could potentially build it onto a device and it not work, due to missing dependencies? Aug 30 03:33:27 you just said it has a dependency on it Aug 30 03:33:47 if it doesn't need it, then no, rdepends wouldn't be appropriate. if it's optional, use RRECOMMENDS instead — that'll install it by default, but it can be uninstalled afterward Aug 30 03:33:54 (or excluded via BAD_RECOMMENDATIONS) Aug 30 06:24:19 What exactly is ${WORKDIR}? Aug 30 06:24:26 I cant seem to find that... Aug 30 06:52:58 tcpdump: http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#var-WORKDIR Aug 30 11:46:21 I am trying to build my first image for a orangepi zero. I have got the "quick start" build to work. I added the .conf file for the orangepi and the files it asked for to the /include directory. Getting the following error when I run bitbake. Any ideas? https://pastebin.com/VQYS34Kf Aug 30 11:59:23 Willy--: are you using matching git branches for your layers? Aug 30 12:01:47 I was using the current poky release, but the orangepi stuff was from https://github.com/linux-sunxi/meta-sunxi Aug 30 12:04:19 Willy--: and you followed the kernel uboot config advice in that layers readme? Aug 30 12:05:05 hmm, it ddoesn't actually say it's required... Aug 30 12:05:11 jku: I did not see a layers readme, so no Aug 30 12:06:50 jku: I did nothing other than update my locale.conf, copy the orange_pi_zero.conf over, the /include directory and the /classes. Aug 30 12:07:51 Willy--: why did you copy stuff? checkout the layer, add it to bblayers, set machine in local.conf Aug 30 12:10:59 does anyone knows a package wich provides swh ladspa plugins? Aug 30 12:11:11 rburton: when I check out the layer, where should it sit in the directory structure? Aug 30 12:13:10 Willy--: wherever you want, as you update bblayers to point at it Aug 30 12:13:16 alongside the other layers is a fairly good suggestion Aug 30 12:22:33 checkout the layer and edited bblayers.cong. I tried with core-image-sato argument and got https://pastebin.com/1kask31H However with core-image-minimal it is currently building. Aug 30 12:30:52 Willy--: those errors are because the bsp needs updating (or just doesn't support EGL, not used it before) Aug 30 12:31:31 rburton: oh yes, ok Aug 30 12:31:35 ty Aug 30 14:18:46 I have had my build for the Orangepi-zero fail (after a few hours of building), details https://pastebin.com/r3r6rtVK Any suggestions as to cause? Aug 30 14:19:30 Willy--: tempted to say run bitbake again and see what happens Aug 30 14:20:01 rburton: done. But are you saying that because by the time it fails again you won't be here? LOL Aug 30 14:20:37 oh.. it failed again with the same message Aug 30 14:21:20 never seen that. sort of blame the bsp if it worked with a qemu machine earlier. Aug 30 14:22:00 any ideas for a solution? Aug 30 14:22:07 where I have seen that type of error is when a package being build specifies a license file, but it doesn't actually exist.. Aug 30 14:22:17 that should not be possible to get this far, but I've seen it before do that Aug 30 14:22:46 looks like it's hte u-boot recipe.. based on the 'no such file or directory'.. Aug 30 14:23:38 check that a LICENSE and LIC_FILES_CHKSUM is defined in the u-boot recipe being used Aug 30 14:23:47 (and that whatever it is defined as is reasonable) Aug 30 14:32:48 I went into the boot/tmp/deploy/licenses directory, and there is no u-boot directory, only a u-boot-mkimage-native Aug 30 14:39:32 cd .. Aug 30 14:39:38 oooops Aug 30 14:42:29 it would only get copied there if the recipe is setup properly.. so I suspect it's a recipe problem. the BSP probably provides a custom version of u-boot and something is broken there Aug 30 14:44:29 I am just looking under recipes-bsp/u-boot now Aug 30 14:44:43 in which layer? Aug 30 14:46:08 assuming this is what you have enabled (based on the pastebin) Aug 30 14:46:09 https://github.com/linux-sunxi/meta-sunxi/blob/master/recipes-bsp/u-boot/u-boot_2017.03.bb Aug 30 14:46:26 I'd verify that each of the LIC_FILES_CHECKSUM references files do indeed exist in your system.. Aug 30 14:46:28 yes, that is the layer I was looking in Aug 30 14:47:22 those files would be in the extracted source code unde Licenses.. 'I think' Aug 30 14:47:31 been a while since I tried to debug this kind of issue Aug 30 14:51:38 It says in u-boot-sunxi.bb, "require recipes-bsp/u-boot/u-boot.inc" which I dont have Aug 30 14:51:53 that is coming (most likely) from 'meta' (oe-core) Aug 30 14:52:29 require and include are included from the path. The current (recipe) directory is searched first, and then it falls back to the other system defined directories.. each layer is usually listed in that path search Aug 30 14:52:37 so look at meta/recipes-bsp/u-boot/u-boot.inc Aug 30 14:53:35 oh, yup I did not think of that.. that is there Aug 30 14:53:59 so the only file in the LIC_FILES_CHKSUM is file://Licenses/gpl-2.0.txt Aug 30 14:56:20 So what path would it be searching for license files under? gpl-2.0.txt is in a couple of different build directorier Aug 30 14:56:32 the source code path.. Aug 30 14:56:43 bitbake -c devshell look around.. (you might have to go up one directory) Aug 30 15:07:51 well it would appear as if I have had success.. will let you know in a few hours, or maybe in a few seconds. Gotta love this building stuff Aug 30 15:17:45 Morning everyone Aug 30 15:18:08 cd ${ROOT_HOME} I did that in my recipe and I get this error: temp/run.do_install.63530: 149: cd: can't cd to /home/root Aug 30 15:18:13 Im not sure I understand why... Aug 30 15:18:18 Anyone have any ideas. Aug 30 15:18:57 Im trying to get to the right directory so I can do a tar -xvcf in the right location. Aug 30 15:19:11 Should I skip CD and just do a fully qualified tar command with the full output path? Aug 30 15:20:31 tcpdump: becayse you're trying to cd to /home/root on your *host* Aug 30 15:20:44 cd ${D}${HOME_ROOT}, assuming you've mkdir'd it first. Aug 30 15:55:13 thanks rburton so {D} i presume is something like remote device? Aug 30 15:55:38 tcpdump: no, its the path to the staging directory where the package is constructed Aug 30 15:56:07 you've a function called do_install() whose one job is to put files inside ${D} so that they can be packaged Aug 30 15:56:50 ${HOME_ROOT} ${prefix} etc are paths on the target so inside do_install need to be prefixed with ${D} so they go to the right place. Aug 30 15:57:07 yea, that makes sense now. It obviously worked. Aug 30 15:57:19 I was just trying to understand what that variable was. Aug 30 15:57:52 How do I get bitbake to generate `tmp/work-shared`? Aug 30 15:58:00 I want to see the kernel-source that was used Aug 30 16:00:00 the same way you'd get the source for any recipe? Aug 30 16:00:05 bitbake -c patch virtual/kernel Aug 30 16:00:19 it's still unpacked and patched with the same tasks as non-shared recipes Aug 30 16:02:45 Thanks kergoth. That would have taken me a long time to figure out Aug 30 16:03:28 the official docs cover the basic tasks, afaik, but http://www.aosabook.org/en/yocto.html does as well Aug 30 16:11:05 is it permissible to run two yocto operations at once, as long as they are in different build dirs? Aug 30 16:11:51 yes Aug 30 16:14:41 ok, thanks Aug 30 16:14:52 ERROR: recipe linux-variscite is already in your workspace Aug 30 16:16:17 why am i getting this? Aug 30 16:16:29 i've done the same thing a dozen times without this error.. Aug 30 17:00:41 ok i guess i never did a "devtool finish" of a previous "devtool modify". my bad. Aug 30 17:05:40 in case of a successful build of a recipe - are there any logs kept from the build process? Aug 30 17:22:38 hey, on a clean poky/morty, building core-image-sato fails during the 'rpmjs.lo' step, but i don't have the knowledge to debug the error or understand what has gone wrong? Aug 30 19:08:34 I dont see python3 defined in any of my recipes, however, it appears to be broken out of the box but present. Can I just offically add IMAGE_INSTALL_append = " python3" to my main recipe and hopefully that just makes it work? Aug 30 19:09:27 would that "reinstall" it (of sorts)? Aug 30 19:09:59 you could do that via image recipe yes Aug 30 19:11:21 crazy_imp: yes logs are generally in tmp/log/cooker Aug 30 19:11:47 tcpdump: for master yes, but for older releases you'll need to install python3-modules to get the entire python3 Aug 30 19:12:20 ah Aug 30 19:12:24 makes sense. Aug 30 19:12:25 tcpdump: otherwise you get the bits you need to run everythign in the image which may not be a full install (and in older releases was fairly broken as we didn't do py3 out of the box) Aug 30 19:12:44 latest code has python3 be "all of python", so it does what you expect Aug 30 19:13:30 rburton: Morty Aug 30 19:13:43 So looks like 2.2 Aug 30 19:14:30 khem: ok Aug 30 19:18:27 https://www.irccloud.com/pastebin/4n5G4xn0/ Aug 30 19:18:37 Thats th error im getting.. dont have python3-modules yet. Aug 30 19:18:47 That seem to line up Aug 30 19:18:47 ? Aug 30 19:20:27 Is there YP document that maps kernel version to project (or possibly poky) version? Aug 30 19:20:53 https://wiki.yoctoproject.org/wiki/Linux_Yocto Aug 30 19:21:50 @khem thx dood ... not sure how I missed that. Aug 30 19:24:49 "* Migrated BitBake and python functions in the OE metadata to Python 3" - looks like thats in 2.2 Aug 30 19:24:58 So thats good. Aug 30 19:29:12 Hmm, so I've added python3 and python3-modules and still get the error. WIll I need to do a completely clean build? Aug 30 19:29:39 or should doing a repo sync and bitbake build-my-image be sufficient? Aug 30 20:04:24 how do i abort if i was in the middle of a devtool modify procedure? Aug 30 20:04:26 zeddii: I am working with QEMU a9 emulation and I am using linux-yocto KMACHINE as "qemuarma9" Aug 30 20:04:44 zeddii: I am getting some warnings of missing config settings Aug 30 20:04:55 devtool reset ? Aug 30 20:06:09 zeddii: is it possible for you to take a look on this or give me a hint how to fix it myself? Aug 30 20:12:06 otavio: IIRC qemu wasnt compatible with arm > a6 Aug 30 20:15:21 yates: right. AFAIK, devtool reset just cleans up the bb part, but your changes in source code remains Aug 30 20:15:48 tcpdump: idk what youre using, but we dont use repo sync, python3-modules should have solved not finding encodings, although the previous error is what actually caughts my attention, it looks like an error during build time on which you specify where your modulea are going to be, hence why it cant find encodings Aug 30 20:17:28 tcpdump: it seems to me that your python build is corrupt, at first sight it looks like some of the patches we apply to python so we can cross compile it are not being applied, but I cant be sure without loioking at your recipe' Aug 30 20:26:29 caught* Aug 30 20:30:15 otavio: I can have a look at it tomorrow. I didn’t boot it in this uprev cycle, but can do that as an extra test. Aug 30 21:33:40 If I wanted to copy my directory and subs to /home/root I could do this? cp ${WORKDIR}/git/api ${D}${ROOT_HOME} and that would give me /home/root/api ? Aug 30 21:34:04 cp -a? Aug 30 21:36:43 only if ${D}${ROOT_HOME} already existed. mkdir -p ${D}${ROOT_HOME} first. Aug 30 21:36:54 this is basic linux commands and scripting now, see the man pages Aug 30 21:38:05 yea, it does, I made that earlier in my recipe. Aug 30 21:39:16 the other issue is that path is almost certainly not packaged by default, you'll get a warning about unpackaged files, unless you do a FILES_${PN} += "${ROOT_HOME}" Aug 30 21:54:16 Does yocto force using absolute paths for native binaries (e.g. curl) within a package task (I am on pyro)? Aug 30 21:56:45 I am unable to use binaries from /usr/bin but binaries from /bin are found without specifying the absolute path Aug 30 21:58:04 mtahmed: it prunes down PATH to only include things listed in HOSTTOOLS. You likely need a DEPENDS += "curl-native" Aug 30 22:00:32 mtahmed: you should use the ones provided by yocto (native recipes) since they're the ones tested for compilation Aug 31 02:33:16 Woot woot just 172 mph Aug 31 02:33:24 Sorry, wrong Channel **** ENDING LOGGING AT Thu Aug 31 03:00:01 2017