**** BEGIN LOGGING AT Tue Jun 02 02:59:58 2015
Jun 02 07:55:15 <ericbutters> any meta-mono guys here?
Jun 02 08:31:13 <ericbutters> how to disable was skipped: incompatible with license GPLv3
Jun 02 08:32:12 <neverpanic> not blacklist GPLv3, I guess?
Jun 02 08:33:15 <ericbutters> neverpanic: thanks, i found INCOMPATIBLE_LICENSE = "GPLv3" in my local.conf
Jun 02 09:16:51 <ionte> hi. i once again try to add a custom device tree for meta-raspberrypi, but i do not really understand how to start. anyone familiar with meta-raspberrypi?
Jun 02 09:17:37 <imrehg> bluelightning: thanks for the help yesterday re:hwclock
Jun 02 09:17:44 <imrehg> The trick was that I needed to delete the sstate-cache as well, not just tmp, then it was all built correctly
Jun 02 09:17:56 <lpapp> ionte: custom device tree?
Jun 02 09:18:21 <ionte> lpapp: well, i need to add a device to the device tree
Jun 02 09:18:39 <lpapp> why, isn't that up to the layer that already provides that?
Jun 02 09:18:50 <lpapp> ah, I see.
Jun 02 09:19:04 <lpapp> you use the raspberry pi with some extra ic of some sort.
Jun 02 09:19:11 <ionte> lpapp: yes
Jun 02 09:19:11 <imrehg> ionte: create it as a patch onto the kernel recipe? (patch the raspberry kernel)
Jun 02 09:19:18 <lpapp> ionte: I think config framents are your friend there.
Jun 02 09:19:36 <lpapp> or just a .bbappend with the patch you need.
Jun 02 09:19:44 <lpapp> that is how you modify the kernel in general.
Jun 02 09:20:02 <lpapp> but perhaps that is not raspberry pi anymore then, so it should reside in another layer? Is it some custom raspberry pi?
Jun 02 09:21:13 <ionte> imrehg: perhaps, if there's no better support to just add another device tree file, on top of the existing... not very familiar with device tree either, though I *have* used it before ona freescale computer
Jun 02 09:21:58 <ionte> lpapp: i have a layer for this "machine", so i try to setup the device tree from there
Jun 02 09:22:16 <ionte> that layer depends on meta-raspberrypi though
Jun 02 09:22:28 <lpapp> ok, so .bbappend in meta-ionte
Jun 02 09:23:33 <ionte> yes, i have .bbappend for the kernel already. but i'm not sure what to put in there... should i patch the device tree that is supplied with the kernel, or add another device tree file, and if the later, how do i get the build system to use it...?
Jun 02 09:25:10 <lpapp> ionte: http://www.yoctoproject.org/docs/1.8/dev-manual/dev-manual.html#using-bbappend-files
Jun 02 09:25:11 <ionte> on the freescale computer i used before i just patched arch/arm/boot/dts/imx23-olinuxino.dts, but i'm not sure if that's the preferred way to handle it. there *is* some support for specifying device tree in meta-raspberrypi (KERNEL_DEVICETREE)
Jun 02 09:27:56 <lpapp> ionte: I would just create a patch.
Jun 02 09:28:04 <ionte> ok
Jun 02 09:28:27 <lpapp> (this is what we did with the board files - pre-dt)
Jun 02 09:32:19 <ionte> i have already got the device working on previous kernels, before there was device tree support in the raspberry pi kernel. i used to patch a arch/arm/mach-bcm2708/bcm2708.c. but since there is not device tree support i thought i should do it properly.
Jun 02 09:35:43 <lpapp> properly is always relative :-)
Jun 02 09:36:01 <ionte> ;)
Jun 02 10:56:32 <lpapp> bluelightning: are you aware of SDK related changes going from dylan to daisy? It seems that I need to specify the subprocess python module explicitly now, whereas this was not necessary before.
Jun 02 10:56:41 <lpapp> (I cannot seem to find this in the migration guide either as a note)
Jun 02 10:57:02 <lpapp> Although, hmm, I needed to specify the "json" module.
Jun 02 10:58:15 <bluelightning> lpapp: specify where?
Jun 02 10:58:39 <lpapp> e.g. in the distro config: -TOOLCHAIN_HOST_TASK_append = " nativesdk-python-json"
Jun 02 10:58:40 <lpapp> +TOOLCHAIN_HOST_TASK_append = " nativesdk-python-json nativesdk-python-subprocess"
Jun 02 10:59:00 <lpapp> and we have always used subprocess in our application that has been built on top of the SDK.
Jun 02 10:59:22 <bluelightning> python dependencies are not automatic, so without an explicit statement they would only have been coming in by accident before...
Jun 02 11:00:10 <bluelightning> the other alternative is to install python-modules (or nativesdk-python-modules in this context), then you get everything from the standard python distribution
Jun 02 11:02:27 <lpapp> I thought this was changed after the discussion on the mailing list
Jun 02 11:02:35 <lpapp> not to bring modules in by default.
Jun 02 11:04:23 <lpapp> hmm, maybe not, I am not sure. OK, thanks, so it worked by accident (bug).
Jun 02 11:10:00 <ericbutters> hey.. which packages provides tcpdump??
Jun 02 11:10:40 <ericbutters> also ltrace?
Jun 02 11:10:43 <bluelightning> lpapp: ah right yes I recall the discussion & bug - the fix did not get backported to daisy, only dizzy
Jun 02 11:11:56 <bluelightning> ericbutters: tcpdump and ltrace, the recipes that produce them are in meta-networking and meta-oe respectively
Jun 02 11:12:09 <ericbutters> thanks
Jun 02 11:12:18 <bluelightning> ericbutters: for future reference, http://layers.openembedded.org/layerindex/branch/master/recipes/ is your friend ;)
Jun 02 11:12:47 <ericbutters> bluelightning: that is good to know! :D
Jun 02 11:46:57 <jaeckel> bluelightning: did you see my question on bash of last week? https://www.yoctoproject.org/irc/%23yocto.2015-05-29.log.html#t2015-05-29T09:42:10
Jun 02 11:47:11 <jaeckel> sorry to repeat again, but I got no reply yet ;)
Jun 02 12:31:46 <DanielAdolfsson> Hi all you experts, I have run into a small issue that might be related to me updating a relatively old yocto install to 1.7. It might also be that I have not been able to find the correct piece of documentation.
Jun 02 12:32:18 <DanielAdolfsson> Ever since i updated whenever I build a sdk none of the extra libraries are included. Eg. boost
Jun 02 12:34:42 <DanielAdolfsson> the libraries seem to be included in the platform image itself
Jun 02 12:34:59 <DanielAdolfsson> but only the basic os headers and libraries are included in the sdk.
Jun 02 12:36:05 <DanielAdolfsson> Do anyone recognize this kind of error or have an idea what could be wrong.
Jun 02 12:40:24 <DanielAdolfsson> or... correction it seems like the .so files are included but not the headers (.h files)
Jun 02 12:51:49 <bluelightning> jaeckel: it's not a known issue to me I'm afraid... the question would be is it a known issue upstream?
Jun 02 12:53:06 <bluelightning> DanielAdolfsson: FWIW, that functionality would be controlled by SDKIMAGE_FEATURES I think - that should include "dev-pkgs" by default
Jun 02 12:58:06 <DanielAdolfsson> hmm I think you might just have found the issue.. I dont recognize that variable.. maybe it is "new"
Jun 02 12:58:59 <bluelightning> it shouldn't need to be set, it has a reasonable default
Jun 02 12:59:35 <DanielAdolfsson> would that be defined in local.conf?
Jun 02 13:00:03 <bluelightning> the default is set in meta/classes/populate_sdk_base.bbclass
Jun 02 13:00:41 <DanielAdolfsson> since i merged an old version with git pull something might have gone bad.. I will take a look
Jun 02 13:00:41 <bluelightning> bitbake -e | less can be used to determine whether it's set or not
Jun 02 13:00:49 <DanielAdolfsson> thank you for the input
Jun 02 13:01:02 <bluelightning> well potentially that could have resulted in any number of issues
Jun 02 13:03:07 <DanielAdolfsson> I reviewed the changes and did not see any obvious oddities but i might end up re-trying with a clean checkout. thanks again.
Jun 02 13:06:07 <bluelightning> DanielAdolfsson: no problem, let us know if you're not able to resolve thie issue
Jun 02 13:23:44 <_4urele_> Hi everyone
Jun 02 13:24:30 <bluelightning> hi _4urele_
Jun 02 13:25:35 <jaeckel> can someone of you who has bash installed try it out if it behaves the same as described here? https://www.yoctoproject.org/irc/%23yocto.2015-05-29.log.html#t2015-05-29T09:42:10
Jun 02 13:25:54 <_4urele_> I started to use systemd days ago and something is bothering me... on the serial console when i'm using some keys (del, insert, start, end), it is not well understood and it prints a "~". If someone knows something about this
Jun 02 13:31:15 <_4urele_> another strange thing is that it works in vi (called in the serial console)....
Jun 02 13:37:21 <_4urele_> ok I found it (I searched it for a long time) sry for flooding
Jun 02 13:38:49 <_4urele_> If anyone cares it is the TERM env variable which was set to "TERM=xterm" (on other versions I had "TERM=linux")
Jun 02 14:09:51 <AlexVaduva> hello guys is there a smart related problem in poky Bugzilla. I am referring here to something similar to this:
Jun 02 14:10:49 <AlexVaduva> https://bugs.launchpad.net/smart/+bug/1238492
Jun 02 14:11:15 <AlexVaduva> I identified the bug as smaprt package internal error, but I wanted to ask your advice
Jun 02 14:11:28 <AlexVaduva> how should we proceed with this one
Jun 02 14:12:53 <AlexVaduva> try and interact with the package developers?
Jun 02 14:14:18 <AlexVaduva> did anyone from Yocto experience this bug which might behave differently but in essence seems to guide towards the same problem
Jun 02 14:14:21 <AlexVaduva> ?
Jun 02 14:58:15 <sjolley> YPTM:   Ready-Access Number:    8007302996  Access Code:    2705751
Jun 02 14:58:26 <armpit> YPTM: armin is on
Jun 02 14:58:26 <sjolley> YPTM: Stephen is on
Jun 02 14:59:13 <AlexVaduva> YPTM: AlexV. on
Jun 02 15:00:33 <zeddii> YPTM: Bruce is on, but has to stay muted.
Jun 02 15:01:08 <vmeson> YPTM: Randy joined.
Jun 02 15:02:43 <halstead> YPTM: Michael joined
Jun 02 15:03:06 <joseppc> YPTM: josep
Jun 02 15:03:53 <dlerner> dlerner joined
Jun 02 15:04:17 <bavery> YPTM: Brian Avery
Jun 02 15:04:32 <prsdhall> YPTM: good morning, Dennis Hall is on the call
Jun 02 15:04:36 <vmeson> dlerner: is Dave akusterLerver sjolley
Jun 02 15:04:43 <vmeson> oops
Jun 02 15:04:48 <dlerner> dlerner is Dave Lerner
Jun 02 15:05:01 * ulf` is on the bridge
Jun 02 15:09:20 <AlexVaduva> YPTM AlexV. here I have some problems with the kype connection I want to bring up some team sharing
Jun 02 15:09:31 <AlexVaduva> one related smart and one related meta-cgl
Jun 02 15:12:20 <halstead> I didn't catch the name of the person at WindRiver who wants to help with test coverage.
Jun 02 15:14:35 <halstead> If you know who that was please tell me. Thanks.
Jun 02 15:15:15 <sjolley> I think it was Randy MacLeod.
Jun 02 15:15:23 <vmeson> https://labix.org/smart
Jun 02 15:15:29 <vmeson> fyi^^^
Jun 02 15:16:01 <halstead> Thanks!
Jun 02 15:19:28 <sjolley> YPTM is over
Jun 02 15:19:38 <prsdhall> quit
Jun 02 15:19:40 <prsdhall> exit
Jun 02 15:33:15 <balam_> Hi All! Greetings!
Jun 02 16:17:12 <vmrod25> sgw_: hi question regarding to cpio
Jun 02 16:18:22 <sgw_> vmrod25: sure I will see what I can do
Jun 02 16:19:52 <vmrod25> I was checking you submit a patch for a http://patchwork.openembedded.org/patch/88251/
Jun 02 16:20:08 <vmrod25> in latest version of cpio there are some fixes regarding to that
Jun 02 16:20:15 <vmrod25> http://git.savannah.gnu.org/cgit/cpio.git/commit/?id=f6a8a2cbd2d5ca40ea94900b55b845dd5ca87328
Jun 02 16:20:33 <vmrod25> but now when I try to build from scratch
Jun 02 16:20:51 <vmrod25> it fail in the test: 5: symlink-bad-length                              FAILED (symlink-bad-length.at:46)
Jun 02 16:21:06 <vmrod25> in the begining I had the idea it was gcc 5
Jun 02 16:21:10 <vmrod25> but is the same with 4.8
Jun 02 16:21:12 <vmrod25> :(
Jun 02 16:23:04 <vmrod25> I am really tempted to submit the bug to upstream
Jun 02 16:23:25 <vmrod25> I just find your name on the csv and wanted your advise
Jun 02 16:34:01 <sgw_> vmrod25: Not sure why my name is on that patch as it seems someone from Fujitsu actually submitted it, are you saying that it's failing it's own self test?
Jun 02 16:38:41 <vmrod25> lolz
Jun 02 16:38:51 <vmrod25> yea .. they are failing ath teh build time test
Jun 02 19:47:58 <skfax> Are there easy ways to explore the contents of filesystems resulting from yocto builds? i.e. is there a folder containing the files before they are packaged as an "tar.bz2"? Or is it easiest just to unpack this file?
Jun 02 19:55:37 <zeddii> skfax. yep.
Jun 02 19:56:07 <zeddii> cd build/tmp/<your bsp>/<your image type>/<version>/rootfs
Jun 02 19:58:18 <paulg_> you can also go into the pkg itself and explore there, if you know what pkg it comes from and do_rootfs hasn't completed yet.
Jun 02 19:59:07 <paulg_> i.e  tmp/work/<bsp-name>/<pkg-name>/<version>/image/
Jun 02 19:59:23 <paulg_> a real world example: tmp/work/genericx86_64-poky-linux/base-files/3.0.14-r89/image/
Jun 02 19:59:35 <skfax> This seems to be it: poky/build/tmp/work/zx3_pm3_zynq7-poky-linux-gnueabi/zx3-image/1.0-r0/rootfs
Jun 02 20:00:09 <paulg_> co-op:~/poky/build$ cat tmp/work/genericx86_64-poky-linux/base-files/3.0.14-r89/image/etc/issue
Jun 02 20:00:09 <paulg_> Poky (Yocto Project Reference Distro) 1.8+snapshot-20150602 \n \l
Jun 02 20:00:09 <paulg_> co-op:~/poky/build$
Jun 02 20:00:14 <skfax> is that not the final root filesystem?
Jun 02 20:00:32 <zeddii> skfax. it is.
Jun 02 20:00:35 <skfax> ok great
Jun 02 20:01:10 <skfax> are there ways to track how a specific file in the filesystem has been made? i.e. through what packages?
Jun 02 20:01:42 <paulg_> many ways
Jun 02 20:02:00 <paulg_> on a deployed system you can do "rpm -qf /path/to/file"
Jun 02 20:02:40 <paulg_> on the build you can do sth as simple as wildcard expansion on tmp/work/*/*/*/image/path/to/my/file
Jun 02 20:03:26 <skfax> ok will try that
Jun 02 20:03:52 <paulg_> there are installer logs and lots of other ways too ; folks more bitbake savvy than I am can make alternate (i.e. smarter) suggestions
Jun 02 20:04:04 <skfax> also, what is the deal with build/tmp/deploy/rpm ? are the rpms found here already installed into the prepared filesystems?
Jun 02 20:04:13 <paulg_> some, but not all
Jun 02 20:04:47 <paulg_> you can do bitbake somepackage
Jun 02 20:05:23 <paulg_> that will generate an rpm for it, but unless there is something like an RDEPENDS on it, or it is explicitly called out in your filesystem pkglist, it won't be in the rootfs.
Jun 02 20:05:40 <skfax> ok makes sense
Jun 02 20:33:58 <rburton> otavio: fsl is still appending gstreamer recipes that don't exist in oe-core...
Jun 02 20:34:29 <otavio> rburton: i know; I am awaiting for them to look at the recipes
Jun 02 21:06:33 <skfax> when using "bitbake -c menuconfig"; which file am i actually editing?
Jun 02 21:07:56 <skfax> ah, think i found it :) ".config" file in tmp/work/...
Jun 02 21:36:52 <skfax> I'm trying to understand how the /etc/network/interfaces file is modified in a build
Jun 02 21:38:41 <skfax> "meta-xilinx-community/recipes-core/init-ifupdown" has the recipe "init-ifupdown_1.0.bbappend" with content "FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}/:""; and there is the file "meta-xilinx-community/recipes-core/init-ifupdown/init-ifupdown-1.0/interfaces".
Jun 02 21:39:53 <skfax> How does the process of finding this "interfaces" file work? What if there are different kinds of "interfaces" files placed in the FILESEXTRAPATHS variable lookup? How do you avoid a name collision?
Jun 02 22:12:19 <nochum> Hi
Jun 02 22:13:29 <nochum> Is there any eclipse plugin tlfor straight yocto packaging?
**** ENDING LOGGING AT Wed Jun 03 02:59:58 2015