**** BEGIN LOGGING AT Thu Mar 08 03:00:03 2018
Mar 08 05:11:42 <silviof> I have a problem with the command 'wic list source-plugins' I get following error message: https://paste.ofcode.org/32eT6mGDGtCsNv2YRVepBVG ... what I'm doing wrong or what is the problem?
Mar 08 07:07:23 <guenni90> hello fellows, currently i am trying to work with layers and trying to overlay hardly some .inc files. It seems to me like hard overlaysing, so that the inc file from the lower layer is not used, is not possible
Mar 08 07:07:27 <guenni90> is that true?
Mar 08 07:43:36 <LetoThe2nd> guenni90: without verifying it, i think that the includes are actually not meant to be overridden
Mar 08 09:29:50 <JoseBravo> I'm having a hard time compiling a receipt due this error: "checking for jansson >= 2.6... no configure: error: Could not find jansson library - please install jansson >= 2.6"
Mar 08 09:30:11 <JoseBravo> But it's already on my DEPENDS
Mar 08 09:30:36 <JoseBravo> It's installing the version 2.9 but it can't locate it
Mar 08 09:31:14 <LetoThe2nd> JoseBravo: well then see how it checks for the dependency. maybe it uses some hardcoded paths or magic
Mar 08 09:31:55 <LetoThe2nd> at a first glance, it seems to come with pkg-config, so it should basically use that.
Mar 08 09:32:01 <JoseBravo> LetoThe2nd, PKG_CHECK_MODULES(JANSSON, jansson >= 2.6, [AC_DEFINE(HAVE_JANSSON, 1, [Define if you have jansson >= 2.6])], [AC_MSG_ERROR([Could not find jansson library - please install jansson >= 2.6])])
Mar 08 09:32:52 <JoseBravo> And I have in my recipe: inherit autotools pkgconfig
Mar 08 09:33:18 <LetoThe2nd> that seems to be right
Mar 08 09:34:34 <LetoThe2nd> then i guess you need to dig deeper in config.log, sorry.
Mar 08 09:35:14 <JoseBravo> I tried to define HAVE_JANSSON, it passed that PKG_CHECK_MODULES.... but it died in the compilation process due missing stuff
Mar 08 09:36:11 <LetoThe2nd> and you have verified that jansson really gets built? e.g. that the dependency is honoured?
Mar 08 09:41:24 <JoseBravo> LetoThe2nd, yes
Mar 08 09:41:51 <JoseBravo> I just ran bitbake -f -c cleans state jansson and then bitbake jansson...
Mar 08 09:42:11 <JoseBravo> It finished w/o any warning or error
Mar 08 09:42:21 <LetoThe2nd> um. that does not tell you anything about the dependency.
Mar 08 09:42:34 <JoseBravo> How can I check that?
Mar 08 09:42:39 <LetoThe2nd> clean jansson, and then build *YOUR* recipe
Mar 08 09:43:41 <LetoThe2nd> if bitbake realizes that you need jansson and it is not yet available (because cleaned), then you should see it being built before bitbake attempts to build your stuff.
Mar 08 09:45:07 <JoseBravo> I just did what you said, it does configure/compilte/package jansson
Mar 08 09:45:26 <JoseBravo> And then the same error again
Mar 08 09:45:52 <LetoThe2nd> then, really look at your config.log whats going on.
Mar 08 10:05:56 <tasslehoff> what is the proper way to add support for libstdc++fs in my image?
Mar 08 10:20:24 <bertrik> hi, I'm a bit desperate trying to make yocto do what I want and I need some help
Mar 08 10:21:10 <rburton> ask away
Mar 08 10:21:14 <bertrik> I have a pre-existing yocto project that I want to modify, in particular I want to enable a kernel config option
Mar 08 10:22:25 <bertrik> I tried creating a .cfg kernel configuration fragment with my kernel option and adding it in a .bbappend file to SRC_URI, I couldn't make that work
Mar 08 10:23:03 <rburton> not all kernel recipes use and support fragments, what is the kernel recipe?
Mar 08 10:23:15 <bertrik> I also tried specifying it with "kernel_conf_variable" in my .bbappend file and that actually seems to work if I run the 'configure' task
Mar 08 10:23:48 <bertrik> rburton: mine is called linux-variscite, this is on an iMX6 board
Mar 08 10:25:47 <rburton> pretty sure those kernels don't support config fragments (only kernels using the linux-yocto tooling do)
Mar 08 10:25:59 <LetoThe2nd> rburton: yep
Mar 08 10:26:00 <rburton> i guess you just need to provide a new defconfig
Mar 08 10:26:00 <LetoThe2nd> https://github.com/varigit/meta-variscite-fslc/blob/morty/recipes-kernel/linux/linux-variscite_4.1.15.bb
Mar 08 10:26:31 <rburton> would be nice if more BSPs used the magic tooling but i guess they have reasons not to
Mar 08 10:27:33 <LetoThe2nd> well on many arm platforms the mix-and-match we all know from x86 doesn't really apply, imho.
Mar 08 10:28:46 <LetoThe2nd> plus, if you're a board vendor, you have technically no interest at all in handing out kernels that add custom options, because your buyer will moan at you even more (this does not work - well did you actually configure it?)
Mar 08 10:28:55 <rburton> still, the ability to enable a few config options without having to write a new config is useful
Mar 08 10:29:18 <LetoThe2nd> i did not say it is not useful :)
Mar 08 10:29:57 <rburton> but yeah there's a good argument for why its in a vendors interest to ship a single defconfig that is tested, as then any changes are the user's responsibility
Mar 08 10:31:26 <bertrik> rburton: ok, I'll forget about configuration fragments for now
Mar 08 10:32:20 <tasslehoff> bertrik: I resorted to kernel_conf_variable on variscite as well.
Mar 08 10:34:52 <bertrik> tasslehoff: if I run 'bitbake linux-variscite -c configure' I do actually find a kernel .config in tmp/work/.../<etc>/build that contains my desired changes, but when I finally build it with 'bitbake linux-variscite' the .config appears to get overwritten again
Mar 08 10:35:11 <bertrik> (I'm a yocto newbie)
Mar 08 10:38:18 <bertrik> Can I perhaps figure out which step resets my config? What steps are there? like fetch, unpack, patch, configure ...?
Mar 08 10:51:51 <tasslehoff> bertrik: check this out http://variwiki.com/index.php?title=Yocto_Linux_logo
Mar 08 10:52:11 <tasslehoff> That "sticks" for my build
Mar 08 10:57:41 <bertrik> thanks, I'll look into that
Mar 08 10:58:09 <tasslehoff> there are lots of libstdc++fs.a files in recipe-sysroot and nativesdk-$PN, but how do I add support to my image/sdk?
Mar 08 10:59:35 <rburton> tasslehoff: https://www.yoctoproject.org/docs/current/sdk-manual/sdk-manual.html#sdk-adding-individual-packages
Mar 08 10:59:46 <lukma> Is this required to use "nativesdk-" prefix when I intent to have a recipe to be installed on SDK?
Mar 08 10:59:51 <lukma> or is it only now a convention ?
Mar 08 10:59:59 <lukma> for example "nativesdk-foo"
Mar 08 11:00:08 <lukma> or just "foo" and require nativesdk ?
Mar 08 11:00:24 <rburton> i'd consider it a requirement
Mar 08 11:00:46 <rburton> calling a recipe foo that is only for nativesdk is just confusing
Mar 08 11:02:31 <LetoThe2nd> can a recipe provide different systemd units for different packages?
Mar 08 11:02:58 <tasslehoff> hm. the file can be found in libstdc++-staticdev I see
Mar 08 11:05:53 <rburton> LetoThe2nd: yes
Mar 08 11:06:27 <LetoThe2nd> rburton: kay, thanks.
Mar 08 11:16:20 <lukma> Is there anybody who can help me with runqemu scripts ?
Mar 08 11:18:24 <lukma> Because I'm wondering why there is tunctl compiled in?
Mar 08 11:18:41 <lukma> as qemu-system-arm calls /dev/net/tun with some ioctls
Mar 08 11:19:07 <lukma> and then tapX is created by system.....
Mar 08 11:20:34 <tasslehoff> rburton: I know how to add packages, I'm just very unsure what to add in this case :)
Mar 08 11:23:00 <tasslehoff> the file originates from gcc-runtime, and can be found in image/usr/lib and packages-split/libstdc++-staticdev/usr/lib
Mar 08 11:45:47 <rburton> tasslehoff: so add nativesd-libstdc++-staticdev to your sdk
Mar 08 11:48:55 <tasslehoff> rburton: yeah. that worked well. and after a coffee I remembered what a static library does and stopped looking for stuff to add to my image :)
Mar 08 12:02:52 <bertrik> I had added a line like "kernel_conf_variable CONFIG_RTC_DRV_PCF2127 y", turns out this translates into a kernel option CONFIG_CONFIG_RTC_DRV_PCF2127 y (so twice "CONFIG")
Mar 08 12:06:14 <bertrik> ok, it appears that was the problem ...
Mar 08 12:07:04 <bertrik> not sure whether to laugh or cry, spent about 6 hours on this :/
Mar 08 12:35:48 <dzen> hi there.
Mar 08 12:36:16 <dzen> I've been watching a lots of docs since a few days.I want to see if it's possible to
Mar 08 12:36:42 <dzen> create a recipe to use python 3.6 as the default python version on a final image
Mar 08 12:36:46 <dzen> is there some caveats ?
Mar 08 15:03:35 <lukma> Lets suppose I do want to add foo package to nativesdk.
Mar 08 15:03:35 <lukma> One solution would be to create foo_%.bbappend with BBCLASSEXTEND = "nativesdk" in it.
Mar 08 15:03:35 <lukma> (and then add it to nativesdk-package-group)
Mar 08 15:03:35 <lukma> Is there any other, better way to do it?
Mar 08 15:07:02 <kergoth> the bbappend is the best way to get it available, but you can append to TOOLCHAIN_HOST_TASK rather than mucking with the existing packagegroup
Mar 08 15:07:55 <lukma> kergoth: I did something like: TOOLCHAIN_HOST_TASK_append = "nativesdk-my-packages"
Mar 08 15:08:06 <lukma> this is done in my distro.conf
Mar 08 15:08:19 <kergoth> that's right, other than the missing leading space
Mar 08 15:08:37 <lukma> kergoth: Yes.
Mar 08 15:09:59 <lukma> kergoth: So if I do have "foo"
Mar 08 15:10:31 <lukma> then it is enough to have TOOLCHAIN_HOST_TASK_append = " nativesdk-foo"
Mar 08 15:10:42 <lukma> without the need of bbappend ?
Mar 08 15:11:07 <lukma> the nativesdk- prefix would be resolved to provide native version of the package ?
Mar 08 15:16:04 <LetoThe2nd> i have a recipe that provides two packages, and therefore SYSTEMD_SERVICE_${PN} and SYSTEMD_SERVICE_${PN}-foo. yet i have to add it manually to FILES_${PN}-foo, and it does not get auto-enabled, the one without -foo does. any trick i'm missing?
Mar 08 15:19:12 <lukma> LetoThe2nd: Maybe some "split" magic has been done in the recipe ?
Mar 08 15:19:33 <lukma> and you need to explicitly add some version of the package to be installed?
Mar 08 15:20:20 <LetoThe2nd> lukma: there is magic for sure. the question is, which and where.
Mar 08 15:21:47 <lukma> I had similar issue with libgles in mesa
Mar 08 15:21:55 <lukma> this recipe did the split
Mar 08 15:22:12 <lukma> and then by default it installs only libglesv2
Mar 08 15:22:37 <lukma> and I had to manually add libglesv1-mesa manually to packagegroup....
Mar 08 15:23:52 <LetoThe2nd> lukma: the split itself is not the problem, all is well. just the additional systemd magic doesn't get applied to the split out package.
Mar 08 15:38:03 <rburton_> lukma: a better way would be to add that class extend to the recipe itself
Mar 08 15:38:37 <LetoThe2nd> for the record: one needs to extend SYSTEMD_PACKAGES
Mar 08 16:07:00 <lukma> rburton: And how to extend nativesdk rootfs? ${SDKTARGETSYSROOT}/ is not the correct directory
Mar 08 16:14:40 <lukma> Probably it is sbindir_nativesdk
Mar 08 16:17:38 <yocti> New news from stackoverflow: Booting linux on imx6 sabrelite Bad Data CRC ERROR: can't get kernel image <https://stackoverflow.com/questions/49177323/booting-linux-on-imx6-sabrelite-bad-data-crc-error-cant-get-kernel-image>
Mar 08 16:20:21 <armpit> RP, nightly-x86-64-lsb passed with new kernel changes.
Mar 08 16:20:35 <armpit> the is the one that hung with kvm enabled on 4.1
Mar 08 16:22:22 <rburton_> lukma: https://www.yoctoproject.org/docs/current/sdk-manual/sdk-manual.html#sdk-adding-individual-packages
Mar 08 16:22:37 <rburton_> lukma: in the recipe you don't have to do anything
Mar 08 16:22:59 <rburton_> bbclasextend does the magic for you, renaming prefix_nativesdk to prefix etc etc
Mar 08 16:25:36 <lukma> rburton: There are some issues, though
Mar 08 16:26:12 <lukma> for example - my SDK rootfs has <patch to SDK rootfs>/usr/bin
Mar 08 16:26:29 <lukma> but it lacks <patch to SDK rootfs>/usr/sbin
Mar 08 16:26:51 <lukma> and the package to which I've bbappended the BBCLASSEXTEND = "nativesdk"
Mar 08 16:27:02 <rburton_> sbindir = "${bindir}" <-- from nativesdk.bbclass
Mar 08 16:27:21 <lukma> wants to install its tools to /usr/sbin
Mar 08 16:27:59 <lukma> So it requires:   FILES_${PN} += " /opt/misio/2.4.2/sysroots/x86_64-pokysdk-linux/usr/sbin/*"
Mar 08 16:28:17 <rburton_> the tool is broken as its not listening to the paths about where to install
Mar 08 16:28:29 <lukma> The  ${sbindir_nativesdk} is not working
Mar 08 16:28:38 <lukma> {bindir} also
Mar 08 16:28:40 <rburton_> it is, the problem is your makefile isn't listening
Mar 08 16:28:53 <rburton_> presumably this is a closed source tool i can't look at the makefile for?
Mar 08 16:29:23 <lukma> rburton: it is the iotop
Mar 08 16:29:30 <lukma> from poky
Mar 08 16:29:54 <rburton_> s/poky/meta-oe/
Mar 08 16:30:10 <lukma> poky/meta-openembedded/meta-oe/recipes-extended/iotop
Mar 08 16:30:26 <lukma> ach , yes I put them all.....
Mar 08 16:30:48 <rburton_> http://repo.or.cz/iotop.git/blob/HEAD:/setup.py <-- hardcodes sbin
Mar 08 16:31:57 <lukma> The fix would be to FILES_${PN} += " /opt/misio/2.4.2/sysroots/x86_64-pokysdk-linux/usr/sbin/*"
Mar 08 16:32:04 <lukma> and then the compilation proceeds
Mar 08 16:32:33 <lukma> But this is (/opt/misio/2.4.2/sysroots/x86_64-pokysdk-linux) the default path of SDK on host machine
Mar 08 16:32:49 <lukma> Can it be changed with some predefined stuff ?
Mar 08 16:36:12 <vladzouth> hi, i am newbie for embedded linux. I build an embedded linux with yocto and use mfgtool to burn uboot kernel and rootfs on my imx6 sabrelite. But after booting i have an error: Bad CRC , can't get kernel image. How can i fix this?
Mar 08 16:49:47 <lukma>  vladzouth: Do you see bootloader prompt?
Mar 08 16:50:58 <vladzouth> what do you mean about it?
Mar 08 17:01:50 <lukma> Bad CRC may come from fitImage (kernel image) loading
Mar 08 17:02:00 <lukma> my question is if you can see the bootloader?
Mar 08 17:10:27 <rburton_> lukma: i'd be doing a mv in a do_install_append_class-nativesdk
Mar 08 17:10:51 <armpit> RP, stable/pyro-next build clean
Mar 08 17:11:51 <lukma> rburton: Could you be more specific?
Mar 08 17:11:59 <lukma> rburton: I cannot follow....
Mar 08 17:12:19 <lukma> I assume that I need to create do_install_append_class-nativesdk
Mar 08 17:12:28 <lukma> and then move something to proper location ?
Mar 08 17:12:32 <rburton_> lukma: do_install_append_class-nativesdk() { mv ${D}${prefix}/sbin ${D}${sbindir} }
Mar 08 17:12:56 <lukma> rburton: This is very specific :)
Mar 08 17:13:44 <rburton_> append to do_install only for nativesdk builds a mv from the hardcoded prefix/sbin to what we think sbin should be
Mar 08 17:13:49 <rburton_> add a comment saying why, obviously
Mar 08 17:14:48 <lukma> rburton: Thanks for explanation :)
Mar 08 17:16:24 <rburton_> context is that distutils is rubbish and you can't control where files go beyond a prefix
Mar 08 17:19:48 <vladzouth> <lukma> , I can see the bootloader, i have execute this command (setenv bootcmd 'run bootargs; mmc dev 1;mmc read ${loadaddr} 0x800 0x3000;bootm') and now it loading the kernel fine but it is blocked at: Starting Kernel...
Mar 08 17:39:14 <RP> armpit: nice!
Mar 08 18:16:54 <dreyna> uff..)
Mar 08 18:43:01 <RP> armpit: merged thanks
Mar 08 19:48:18 <yocti> New news from stackoverflow: ABI mismatch when building go project with a yocto recipe <https://stackoverflow.com/questions/48626090/abi-mismatch-when-building-go-project-with-a-yocto-recipe>
Mar 08 21:08:22 <armpit> RP, thanks
Mar 08 21:48:37 <yocti> New news from stackoverflow: suppress RPM install warning: "warning: group pulse does not exist - using root" <https://stackoverflow.com/questions/49182758/suppress-rpm-install-warning-warning-group-pulse-does-not-exist-using-root>
Mar 09 00:49:16 <RP> armpit: the selftest did fail for pyro :(
Mar 09 00:49:24 <RP> armpit: looks like our APIC hang :(
Mar 09 00:49:41 <RP> armpit: trying a new version of the gcc 6 patch on morty
Mar 09 01:03:26 <JoseBravo> inherit autotools automatically call autogen.sh ?
Mar 09 02:26:34 <jbravo> I'm getting this error: Unable to recognise the format of the input file `/home/user1/poky/build/tmp/work/i586-poky-linux/pydaemon/1.0-r0/package/var/pydaemon/lib/libgpio.so'
Mar 09 02:26:50 <jbravo> How do I disable that check?
**** ENDING LOGGING AT Fri Mar 09 03:00:00 2018