**** BEGIN LOGGING AT Wed Apr 19 03:00:04 2017
Apr 19 07:15:33 <hamdy> how can I add Python or dependencies to a yocto image ?
Apr 19 07:21:47 <hamdy> Can someone help me please ?
Apr 19 07:32:17 <hamdy> how can I add Python or dependencies to a yocto image ?
Apr 19 07:32:19 <hamdy> Can someone help me please ?
Apr 19 07:32:43 <theben> I'm trying to compile a barebone image for a Raspberry Pi, how can I set the MACHINE var in order to keep compatibility with all the board versions (0/1/2/3) ? When I set it to "raspberrypi" I'm not able to boot the image on a RPiv3 board, same goes when I set the var to "raspberrypi3" on a RPi B (v1) machine. Has someone had the same issue ? Any hints ?
Apr 19 07:43:44 <Maximusk> Hi all. I'd like to know if there is a way to override a python function using a bbappend file.
Apr 19 07:47:30 <mckoan> hamdy: add in local.conf IMAGE_INSTALL_append = " python"
Apr 19 07:50:13 <Maximusk> theben: I don't know if that's possible. The Rasberry pi 3 has a 64bits CPU while the 1/2 have 32 bits
Apr 19 07:52:25 <theben> @Maximusk I'd like to compile a 32bit compatible image to be able to use it on boards from RPi1 to RPi3, just like what raspbian does, I don't know if yocto (or the meta-raspberrypi layer) permits it
Apr 19 07:53:39 <hamdy> thanks
Apr 19 07:54:54 <mckoan> theben: if you look in machine directory you can see that RPI2 and 3 are the same tune-cortexa7
Apr 19 07:55:38 <mckoan> theben: but RPI1 and 0 are tune-arm1176jzf-s
Apr 19 07:55:57 <theben> mckoan: that's right
Apr 19 07:56:36 <mckoan> theben: also the kernels have different defconfigs in the two cases
Apr 19 08:04:15 <Maximusk> So, there is no way to override a python function using a bbappend ? I have a recipe with python populate_packages_prepend () made for a different bitbake version, and I'd like to replace the function by on that is compatible with my bitbake version
Apr 19 08:19:03 <jku> I'm building an image for intel-corei7-64 with meta-intel. "hwcodecs" ends up in in IMAGE_FEATURES, "va-impl-intel" ends up in MACHINE_FEATURES but still libva-intel-driver is not on the image
Apr 19 08:19:09 <jku> what am I doing wrong?
Apr 19 08:23:26 <jku> based on "bitbake -e", va-intel RDEPENDS on libva-intel-driver. But libva-intel-driver is not on the image
Apr 19 08:56:53 <LocutusOfBorg> hello fray do you have any news?
Apr 19 08:57:00 <LocutusOfBorg> seems that package.bbclass is never called
Apr 19 09:12:19 <hamdy> how can I add a text editor like nano when I want to bitbake a yocto image please ?
Apr 19 09:22:15 <bluelightning> hamdy: https://wiki.yoctoproject.org/wiki/Technical_FAQ#How_do_I_control_what.27s_in_the_final_image.3F
Apr 19 09:23:14 <bluelightning> FYI you'll need a recipe to build a nano package to include - one exists in meta-oe
Apr 19 09:23:15 <bluelightning> http://layers.openembedded.org/layerindex/branch/master/recipes/?q=nano
Apr 19 09:27:44 <mckoan> hamdy: same as before IMAGE_INSTALL_append = " nano"
Apr 19 09:27:54 <hamdy> bluelignting thanks
Apr 19 09:30:46 <LocutusOfBorg> bluelightning, did you see above the weird bug I found?
Apr 19 09:31:04 <hamdy> I still don't know how to install nano
Apr 19 09:31:08 <LocutusOfBorg> if $PN contains upper case letters, the package.bbclass doesn't work at all
Apr 19 09:31:15 <bluelightning> LocutusOfBorg: no, I did wonder what your comment above was about though
Apr 19 09:31:20 <LocutusOfBorg> it doesn't substitute the variables, e.g. SYSTEMD_STUFF*
Apr 19 09:31:29 <LocutusOfBorg> read some hours before
Apr 19 09:31:50 <LocutusOfBorg> [20:03:57] <LocutusOfBorg> SYSTEMD_SERVICE_${PN} is not replaced in the postinst call
Apr 19 09:31:50 <LocutusOfBorg> [20:04:12] <LocutusOfBorg> you can see "systemctl $OPTS enable $SYSTEMD_SERVICE"
Apr 19 09:32:19 <LocutusOfBorg> systemd.bbclass is feeding that variable, but the postinst script doesn't have the content
Apr 19 09:32:46 <LocutusOfBorg> I'm trying to debug it further, but I'm failing
Apr 19 09:33:01 <LocutusOfBorg> I think I'll open a serious bug later today if nothing new happens
Apr 19 09:34:06 <bluelightning> LocutusOfBorg: FWIW we tend to observe a convention of lower case characters only in recipe names and hence package names
Apr 19 09:34:29 <bluelightning> historically some package managers didn't like them, that's probably not an issue anymore
Apr 19 09:34:45 <bluelightning> actually I think I know what the problem is
Apr 19 09:34:51 <hamdy> how can I add a text editor like nano when I want to bitbake a yocto image please ?
Apr 19 09:34:59 <bluelightning> hamdy: I answered your question above
Apr 19 09:35:16 <hamdy> bluelightning : It don't help me
Apr 19 09:35:27 <bluelightning> hamdy: what part are you stuck with?
Apr 19 09:36:39 <hamdy> I don't see the information thant I need on this web page
Apr 19 09:37:59 <bluelightning> hamdy: you've clicked through to http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#usingpoky-extend-customimage ?
Apr 19 09:38:10 <LocutusOfBorg> bluelightning, not a problem, but in case, raise a warning such as "hey folk, please lower case your recipe name, or be prepared to something bad"
Apr 19 09:38:41 <LocutusOfBorg> I did spent a lot of time trying to get why some of my systemd scripts weren't started automatically
Apr 19 09:38:45 <LocutusOfBorg> same code, same content
Apr 19 09:38:49 <LocutusOfBorg> and different recipe name :p
Apr 19 09:39:07 <bluelightning> LocutusOfBorg: a release or two ago we changed bitbake such that overrides must be lower case in order to gain a significant performance improvement
Apr 19 09:39:45 <hamdy> bluelightning : I'm reading it now
Apr 19 09:40:48 <bluelightning> LocutusOfBorg: because recipe names (and thus the main package name) is used often in overrides, uppercase characters will prevent any such overrides from working
Apr 19 09:41:00 <bluelightning> e.g. SYSTEMD_SERVICE_${PN}
Apr 19 09:41:20 <bluelightning> LocutusOfBorg: you're absolutely right though, we do need a warning
Apr 19 09:43:37 <LocutusOfBorg> so, just avoid upper case recipes and live happy?
Apr 19 09:43:45 <LocutusOfBorg> fray, ^^^
Apr 19 09:47:15 <LocutusOfBorg> do you want a bug for that?
Apr 19 11:12:02 <hamdy> where can I find the package list of possiblities to install with local.conf with this command  IMAGE_INSTALL_append = " software"
Apr 19 11:14:01 <CTtpollard> hamdy: https://layers.openembedded.org/layerindex/branch/master/recipes/
Apr 19 11:15:00 <hamdy> <CTtpollard> I'm looking for nano but I still can't find it
Apr 19 11:15:35 <CTtpollard> https://layers.openembedded.org/layerindex/recipe/998/
Apr 19 11:17:24 <hamdy> <CTtpollard> I saw this page but how can I add it to my config ?
Apr 19 11:18:41 <CTtpollard> hamdy: the way you stated :)
Apr 19 11:21:21 <hamdy>  <CTtpollard>  IMAGE_INSTALL_append = " nano" ?
Apr 19 11:21:32 <CTtpollard> yes
Apr 19 11:21:36 <CTtpollard> the rebuild your image
Apr 19 11:23:29 <hamdy> <CTtpollard> Error : missing or unbuildable dependencies 'nano'
Apr 19 11:25:50 <CTtpollard> hamdy: can you try bitbake-layers show-recipes | grep nano
Apr 19 11:29:42 <hamdy> <CTtpollard> the result if a white space, nothing
Apr 19 11:31:04 <CTtpollard> hamdy: bitbake -s nano ?
Apr 19 11:31:25 <CTtpollard> if that doesn't work it looks like bitbake doesn't have access to a nano recipe
Apr 19 11:31:40 <CTtpollard> I would suspect you have meta-oe layer though
Apr 19 11:31:53 <JoiF> nrossi: I'm still a bit confused about what the difference is between zybo-zynq7 and zybo-linux-bd-zynq7 .. the first one seems to be a subset of the other (where linux-bd has some hdmi encoder stuff)?
Apr 19 11:32:56 <nrossi> JoiF: so zybo-linux-bd-zynq7 is just a zybo with a configured fpga, which has some devices including a hdmi encoder
Apr 19 11:33:25 <JoiF> nrossi: Ah, ok
Apr 19 11:34:55 <hamdy> <CTtpollard>  with bitbake -s nano I have a long list of results, more than 1300. I have git clone meta-openembedded
Apr 19 11:35:51 <CTtpollard> hamdy: does bitbake-layers show-layers list meta-openembedded
Apr 19 11:35:54 <JoiF> nrossi: Just out of curiosity, where does the bitstream for the linux-bd come from?
Apr 19 11:36:16 <nrossi> JoiF: i guess you might be confused by the fact it is not just extending the existing zybo device tree. But thats just because the device trees were generated from the vivado project. And the project is here: https://github.com/Digilent/ZYBO/tree/master/Projects/linux_bd
Apr 19 11:36:43 <JoiF> nrossi: This linux-bd business is nothing that I'll pursue, I'm just wondering
Apr 19 11:36:46 <JoiF> nrossi: Ahhh, I see.
Apr 19 11:37:12 <hamdy> <CTtpollard> no it don't
Apr 19 11:37:34 <ChrysD> hamdy : Have you ever change the file bblayers in build/conf ?
Apr 19 11:38:55 <hamdy> <ChrysD> No I don't know what to change in it.. I'm new in yocto
Apr 19 11:39:50 <JoiF> nrossi: It all makes a lot more sense to me now.  ;)  Thanks!
Apr 19 11:40:42 <nrossi> JoiF: No problems, for reference the zybo-linux-bd-zynq7 is the only zynq machine in meta-xilinx with an actual bitstream :)
Apr 19 11:52:06 <hamdy> when I add the layer meta-oe I have an error with meta-oe/recipes-support/zile/zile_2.4.11.bb
Apr 19 11:54:21 <ChrysD> hamdy : Which error ?
Apr 19 11:55:26 <rburton> hamdy: if you're not using oe-core master then you'll want to check out the right branch of meta-oe, such as morty
Apr 19 11:57:59 <hamdy> <rburton>  I'm on morty
Apr 19 11:58:31 <hamdy> <ChrysD> ExpansianError during parsing
Apr 19 11:59:32 <hamdy> I added the link layer meta-oe and now I can't bake
Apr 19 12:01:16 <luneff> Is there a proper way to start Weston with Qt app fullscreen and disallow screen drag? After some random clicks I managed to move my fullscreen app and I would not like to be able to do that
Apr 19 12:01:26 <ChrysD> hamdy : you have added meta-oe or meta-openembedded/meta-oe ?
Apr 19 12:04:06 <hamdy> <ChrysD> meta-openembedded/meta-oe
Apr 19 12:06:21 <ChrysD> hamdy : Do you have all the meta's in the same version ? Like all krogoth or all morty etc... Do you have all basic layers needed ?
Apr 19 12:07:50 <hamdy> <ChrysD> yes all is in the same version, I have the layers : meta, meta-poky, meta-yocto-bsp, meta-openembedded/meta-oe
Apr 19 12:08:35 <ChrysD> hamdy : which image are you trying to bitbake ?
Apr 19 12:09:20 <rburton> hamdy: did you definitely checkout morty branch of meta-oe
Apr 19 12:10:09 <hamdy> <rburton> yes it's checked out
Apr 19 12:10:34 <hamdy> <ChrysD> bitbake core-image-minimal
Apr 19 12:11:09 <ChrysD> hamdy : which version ?
Apr 19 12:11:24 <ChrysD> hamdy : I mean like krogoth, etc
Apr 19 12:16:59 <hamdy> <ChrysD> Morty the last version, I just downloaded it from git
Apr 19 12:23:36 <mckoan> hamdy: go into meta-openembedded and run git branch
Apr 19 12:24:23 <hamdy> <mckoan> the resulte is : * master
Apr 19 12:24:38 <mckoan> hamdy: it is not morty, it's master
Apr 19 12:25:12 <hamdy> <mckoan> maybe the error come from there. How can I add it to morty ?
Apr 19 12:26:24 <mckoan> hamdy: you can try following this replacing jethro with morty http://wiki.kaeilos.com/index.php/Yocto_Project_my_own_quick_start#Development_Code_.28branch_jethro_2.0.29
Apr 19 12:26:52 <mckoan> git clone git://git.yoctoproject.org/poky -b morty
Apr 19 12:27:01 <mckoan> git clone git://git.openembedded.org/meta-openembedded -b morty
Apr 19 12:30:57 <hamdy> <mckoan>  thanks now they are both in the branch morty, I try to bitbake it again
Apr 19 12:37:48 <hamdy> <mckoan>thanks for the help, it works and now I know how to install new softwares :)
Apr 19 12:38:09 <ChrysD> hamdy : Be sure of having all layers in the same verison
Apr 19 13:46:56 <hamdy> home can I delete the cache of bitbake ?
Apr 19 13:47:12 <hamdy> I mean how can I bitbake an image from the begining a second time ?
Apr 19 13:49:00 <theben> hamdy: remove tmp and ccache dir
Apr 19 13:49:02 <mivond> http://i.imgur.com/xVzH4X0.jpg <-- Any ideas?
Apr 19 13:49:28 <mivond> The raspberry pi 3 hangs at this point.
Apr 19 13:50:06 <theben> mivond: what have you set in MACHINE var ?
Apr 19 13:50:59 <mivond> theben: Build Configuration: BB_VERSION        = "1.33.4" BUILD_SYS         = "x86_64-linux" NATIVELSBSTRING   = "universal" TARGET_SYS        = "arm-poky-linux-gnueabi" MACHINE           = "raspberrypi3" DISTRO            = "poky" DISTRO_VERSION    = "2.2+snapshot-20170418" TUNE_FEATURES     = "arm armv7ve vfp thumb neon vfpv4 callconvention-hard cortexa7" TARGET_FPU        = "hard" meta               meta-poky          meta-yocto-bsp
Apr 19 13:51:10 <mivond> raspberrypi3
Apr 19 13:52:17 <mivond> theben: I am using meta-mender-raspberrypi layer as well
Apr 19 13:52:31 <mivond> Not sure if that's causing this.
Apr 19 13:53:02 <mivond> https://github.com/mendersoftware/meta-mender/tree/master/meta-mender-raspberrypi
Apr 19 13:54:00 <theben> I'm not using mender layer just the meta-raspberry. Are you using uboot ?
Apr 19 13:54:32 <theben> from your image it seems to be you're using it
Apr 19 13:55:22 <theben> that's the big difference from mine, don't know if this might be the problem or if the mender layer uses additional features
Apr 19 13:56:17 <mivond> yes, it uses uboot
Apr 19 13:56:27 <mivond> I haven't used mender before, so it could be the issue
Apr 19 13:56:51 <mivond> Wouldn't surprise me, their documentation on building for the pi was already wrong...
Apr 19 13:57:08 <mivond> theben: I can also get to the U-Boot command prompt.
Apr 19 13:58:34 <theben> I have used http://www.jumpnowtek.com/rpi/Raspberry-Pi-Systems-with-Yocto.html and this is a good start
Apr 19 13:59:02 <mivond> thanks
Apr 19 13:59:06 <mivond> I'll check it out.
Apr 19 13:59:39 <theben> andrei layer (meta-raspberry pi) is the only one I'm using, I'm not even using QT stuff ('cause I don't need it now)
Apr 19 14:01:39 <theben> BTW I'm facing weird compatibility troubles between various board versions (as you might read from previous chats). I'm not able to generate an universal image cross compatible with all boards (RPi 0/1/2/3) Now I'm building with raspberrypi2 to see what happens. I guess I'll post something on the ML to get some help from there... I'm stuck
Apr 19 14:09:00 <_arthur_> Hi. I'm having some trouble convincing yocto to post-process an image file. Specifically, I'm trying to run a tool to sign the file (prepending a header with the signature).
Apr 19 14:09:25 <_arthur_> I thought the way to do this would be to introduce a new IMAGE_TYPE, but I've failed to get that to work so far.
Apr 19 14:10:01 <_arthur_> Is there any documentation/example on how to do something like this? I can't imagine this is a unique thing to want to do.
Apr 19 14:13:10 <hamdy> I can't connect to my yocto build on qemu with ssh. The sshd is running. Nano is installed and the confing in /etc/ssh/ is correct. Someone can help me ?
Apr 19 14:14:53 <majuk> Are you able to ping the build?
Apr 19 14:15:00 <majuk> hamdy: ^
Apr 19 14:15:31 <hamdy> <majuk>no and the build can't ping me
Apr 19 14:15:51 <hamdy> <majuk> it was working before then now with the same config it don't works
Apr 19 14:16:46 <majuk> Well something changed. If you can't ping, there's likely a network issue.
Apr 19 14:29:42 <Ox4> hello guys
Apr 19 14:30:11 <Ox4> how can I get IMAGE_BASENAME variable in the bbappend file where I define my own shell function?
Apr 19 14:40:12 <geoffrey_l> Hi, I want to be sure, what is the correct way to append to ROOTFS_POSTPROCESS_COMMAND ?
Apr 19 14:41:10 <geoffrey_l> I have ROOTFS_POSTPROCESS_COMMAND_append = "install_overlay ; " but somebody tell me it should be ROOTFS_POSTPROCESS_COMMAND_append = " ; install_overlay"
Apr 19 14:57:16 <gjohnson> Hello All, so I am trying to set my DISTRO_VERSION based on the following statement, DISTRO_VERSION := "${@os.popen('git describe --tag').read().rstrip()}"  is this appropriate?  I am getting the warning "WARNING: <string>:1: ResourceWarning: unclosed file <_io.TextIOWrapper name=20 encoding='UTF-8'>"
Apr 19 14:58:08 <rburton> gjohnson: thats because you never close() the pipe
Apr 19 14:58:26 <rburton> use subprocess.check_output("git describe —tag")
Apr 19 15:03:17 <gjohnson> rburton: so I have tried using subprocess but it isn't available in my distro conf file.  Is there a way to import it?
Apr 19 15:03:56 <rburton> write a function and call that
Apr 19 15:04:52 <joshuagl> or use one of the oe wrappers?
Apr 19 15:05:01 <joshuagl> oe.utils.getstatusoutput() ?
Apr 19 15:06:21 <gjohnson> joshuagl: I tried getstatusoutput but I was having trouble getting just the stdout and not stdout and return code.
Apr 19 15:16:51 <_arthur_> Okay, I'm starting to get somewhere with my custom IMAGE_TYPES += "foo", but IMAGE_DEPENDS_foo = "mkfoo-native" doesn't seem to install the mkfoo tool. Am I missing something obvious?
Apr 19 15:25:28 <gjohnson> rburton: Do you know of an example I can use for creating my own python function and then including it into my distro conf file?
Apr 19 15:27:54 <rburton> gjohnson: bb.process.run("git describe —tags")[0] should do what you want
Apr 19 16:02:45 <gjohnson> rburton: So why doesn't this work DISTRO_VERSION := "${@bb.process.run('git describe --tag')[0]}" ?
Apr 19 16:03:00 <mivond> theben: I'm trying this now https://www.raspberrypi.org/forums/viewtopic.php?f=29&t=180366
Apr 19 16:14:20 <rburton> gjohnson: 	dunno, define doesn't work i guess
Apr 19 16:14:59 <gjohnson> rburton: k, I got it working by just using = instead of :=.  Thanks for you help.
Apr 19 16:20:37 <theben_> mivond: nice to have it, I'll test uboot too real soon
Apr 19 16:21:32 <mivond> theben: Thanks, I'll let you know if it works. It's currently flashing to the sd
Apr 19 17:27:23 <mivond> theben: It booted!
Apr 19 17:28:25 <mivond> I had to change fdt_addr_r to fdt_addr in meta-mender/meta-mender-raspberrypi/recipes-bsp/rpi-u-boot-scr/files/raspberrypi3/boot.cmd
Apr 19 17:28:56 <mivond> both load and bootm lines
Apr 19 17:29:19 <mivond> I'd raise an issue on github if they hadn't disabled it. Maybe someone will come across this irc log with the same issue.
Apr 19 18:17:40 <gdg> hi guys, I am used Yocto for few days, I am kind of impressed of it :-)
Apr 19 18:18:24 <gdg> I want to integrate my own device on a Xilinx FPGA and thus update the DTS/DTB
Apr 19 18:19:15 <gdg> what is the standard flow for doing that? I can manually dct a modified DTS file, but I am assuming that there is a Yocto based flow for that
Apr 19 18:19:26 <gdg> do you have any suggestion or reference?
Apr 19 18:28:34 <Crofton|work> gdg, using meta-xilninx?
Apr 19 18:28:40 <Crofton|work> meta-xilinx
Apr 19 18:29:02 <gdg> yeah, but I do not know exactly how to edit and what to edit
Apr 19 18:29:15 <gdg> I am familiar with DTS but not with the Yocto flow for DTS
Apr 19 18:29:38 <gdg> or the Yocto/Xilinx flavor of it
Apr 19 18:29:50 <Crofton|work> maybe send an email to the meta-xilinx list
Apr 19 18:30:06 <gdg> ok, I will try then
Apr 19 20:54:00 <MikeAtMT> Greetings, all. Looks like fedorahosted.org has been deprecated, which breaks the fetch for logrotate on morty oe-core.  Looks like pyro and master have the recipe patched to use the new github repo on fetch.  I've come up with a few ideas for how to handle this for our morty build, but most of these seem like one-offs that I'll have to pay for later (add the recipe in our higher priority proprietary layer).  Is there a de-facto way to
Apr 19 21:45:56 <armpit> MikeAtMT, there was a patch for morty sent to the mailing list and is in the patchwork
Apr 19 21:45:58 <armpit> https://patchwork.openembedded.org/patch/139233/
Apr 19 21:46:22 <armpit> its been pulled into the my morty staging repo for testing
Apr 19 21:46:30 <MikeAtMT> excellent :) gracias!
Apr 19 21:47:14 <armpit> there are a few more that are in master that have not yet made it into morty
**** ENDING LOGGING AT Thu Apr 20 03:00:01 2017