**** BEGIN LOGGING AT Fri Jun 10 02:59:59 2016
Jun 10 09:14:40 <Cubi1> How can I disable the serial console of my device? set SERIAL_CONSOLE to ""?
Jun 10 10:11:05 <bbiojho> is their any libnfc recipe for yocto
Jun 10 10:13:02 <rburton> bbiojho: layers.openembedded.org is your friend
Jun 10 10:40:07 <bbiojho> ok I couldn't find any libnfc recipe. Anyone tried installing libnfc in yocto
Jun 10 10:41:00 <rburton> bbiojho: just assume its going to work fine and use recipetool to make a starting recipe for it
Jun 10 10:58:22 <darkhorse_> I have a few custom packages that I would like to include into my host SDK. without BBCLASSEXTEND = "native native-sdk" it seems to be generating the SDK - BBCLASSEXTEND seems redundant?
Jun 10 10:58:58 <tiq> hi, i have a problem with bitbake
Jun 10 10:59:08 <tiq> the sdcard file it creates seems to be bogus
Jun 10 10:59:33 <tiq> if i manually create an image using the kernel image, u-boot and the filesystem, everything is fine
Jun 10 10:59:53 <tiq> how can i troubleshoot?
Jun 10 11:02:49 <LetoThe2nd> tiq: image fstype 'sdcard' is absolutely fsl specific. the error you're seeing is pretty sure located in your setup or the layers you use, not in bitbake
Jun 10 11:03:59 <LetoThe2nd> tiq: so the first step would be to check the classes in the fsl layer that you use if your machine is even supported for that image type.
Jun 10 11:04:13 <tiq> LetoThe2nd: i see, so i should be looking at the layers? anything specific that tells bitbake how to create the sdcard file
Jun 10 11:04:33 <tiq> ok
Jun 10 11:04:49 <LetoThe2nd> tiq: something along http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/tree/classes/image_types_fsl.bbclass
Jun 10 11:05:29 <rburton> yeah sdcard is part of the fsl bsp, so you need to speak to them.  they have a mailing list, or trying pinging otavio :)
Jun 10 11:05:41 <LetoThe2nd> tiq: line 88 ff. give a pretty good hint which targets are supported :)
Jun 10 11:06:04 <LetoThe2nd> rburton: they've done a really good job in making everybody believe that its an OE builtin :-)
Jun 10 11:12:12 <tiq> thanks guys. looks like it just created a sparse file (IMAGE_CMD_sdcard()) and didn't do anything after that
Jun 10 13:13:35 <darkhorse_> bluelightning: can you help me with some sdk issues, please?
Jun 10 13:14:41 <bluelightning> darkhorse_: what's up?
Jun 10 13:18:39 <darkhorse_> bluelightning: http://pastebin.com/xbjetMH7
Jun 10 13:19:44 <bluelightning> darkhorse_: er... can't satisfy a dependency for libc6? that's a bit of a problem....
Jun 10 13:20:10 <bluelightning> I'm not sure what would cause that to be honest...
Jun 10 13:21:14 <darkhorse_> bluelightning: could it be because I am using poky-tiny may be..?
Jun 10 13:22:15 <darkhorse_> bluelightning: the trouble is, I can't see the dependency chain using depexp or dot files
Jun 10 13:40:46 <bluelightning> darkhorse_: ah, well, yes that might have something to do with it
Jun 10 13:41:23 <bluelightning> darkhorse_: depexp and dot files generated by bitbake -g are only bitbake's idea of dependencies, that does not include runtime dependencies determined at packaging time (it can't)
Jun 10 13:42:07 <bluelightning> darkhorse_: you didn't change DISTRO to poky-tiny while keeping the same TMPDIR by any chance?
Jun 10 13:48:06 <bluelightning> gotta go I'm afraid, g'night
Jun 10 15:55:04 <joshuagl> fray: ping? was wondering if you'd had any time to investigate/think about RPM & package managers?
Jun 10 16:08:16 <kergoth> Anyone seen this running wic on 2.7: *** buffer overflow detected ***: python terminated ?
Jun 10 16:29:11 <nerdboy> kergoth: pax kernel maybe?
Jun 10 16:29:40 <nerdboy> anyone tried the new santana yet?  https://www.youtube.com/watch?v=JV1ntPBh03Y
Jun 10 16:30:59 <kergoth> good idea, but don't think so, looks like stock 14.04, but i've never seen this on my own 14.04 builds, only here on the jenkins vm
Jun 10 17:00:29 <nerdboy> they use apparmor by default i think
Jun 10 17:00:47 <nerdboy> tomoyo might also be enabled
Jun 10 17:01:16 <kergoth> glibc was built with FORTIFY_SOURCE, it's something in the uuid module's use of libuuid, according to the stack trace
Jun 10 17:01:20 <kergoth> hmm
Jun 10 17:02:04 <nerdboy> there are things under kernel hacking too
Jun 10 17:02:28 <nerdboy> dump the config yet?
Jun 10 17:03:33 <kergoth> i'd rather fix the bug it's finding than disable the checking :) but no, not yet
Jun 10 17:03:44 <kergoth> checked the python bts, no luck there
Jun 10 17:04:00 <kergoth> could be in e2fsprogs rather than python, though
Jun 10 17:05:52 <Circuitsoft> Hello - I'm trying to move a file in a do_unpack_append, but I'm getting a very long error from bitbake. It seems like it's executing my shell code as python.
Jun 10 17:06:49 <Circuitsoft> In psplash_git.bbappend, I have: "do_unpack_append() {"\n"mv ${S}/psplash-colors.h ${S}/git/"\n"}"
Jun 10 17:06:52 <kergoth> do_unpack is a python function, and _append/_prepend concatenate
Jun 10 17:06:55 <kergoth> so you appended shell to python
Jun 10 17:06:59 <Circuitsoft> Okay.
Jun 10 17:07:09 <Circuitsoft> Is there an available function to move a file?
Jun 10 17:07:14 <kergoth> instead, create a new shell function, and do_unpack[postfuncs] += "your_function"
Jun 10 17:07:30 <kergoth> that's equivalent to _append, just as a separate function run after the main function
Jun 10 17:08:24 <Circuitsoft> Since I'm just moving one file, would it be easier to just do it in python?
Jun 10 17:09:25 <kergoth> not sure i'd call that "easier". you'd have to either use movefile, which isn't perfect, or call out to mv with subprocess anyway, and you'd have to call d.expand() or d.getVar() to get the value of ${S}, since the contents of python functions aren't expanded
Jun 10 17:09:29 <kergoth> :)
Jun 10 17:09:47 <Circuitsoft> Ok.
Jun 10 17:10:24 <Circuitsoft> What's wrong with movefile? And, would I even need ${S} in there?
Jun 10 17:13:05 <Circuitsoft> Okay.
Jun 10 17:13:14 <Circuitsoft> movefile worked, without needing to expand anything.
Jun 10 17:13:23 <Circuitsoft>     bb.utils.movefile("psplash-colors.h", "git")
Jun 10 17:16:22 <kergoth> cool
Jun 10 18:20:03 <berte> hello everyone, I'm trying to bitbake fsl-image-gui however I'm getting "ERROR: User requested feature sdl" error, how can I handle this issue ?
Jun 10 18:31:48 <berte> my mistake, I executed old script ^^
Jun 10 18:32:07 <berte> now everything works
Jun 10 18:32:10 <berte> have a nice day
Jun 10 19:10:21 <kergoth> Hmm, why is wic using uuid.uuid1() for swap but uuid.uuid4() for the user enabled partition uuids?
Jun 10 19:10:26 <kergoth> Anyone know?
Jun 10 19:28:55 <kergoth> Anyone know offhand if wic's plugin loading from layers is done in a way to let the layer versions override plugins in the base, or can they only add?
Jun 10 20:55:19 <snouto> rburton, gergoth, are you there
Jun 10 20:55:32 <snouto> kergoth , are you there my friend
Jun 10 20:55:44 <snouto> rburton, are you there my friend ?
Jun 10 20:55:53 <kergoth> if you have a question, just ask it. don't pester individuals. anyone may well have an answer
Jun 10 20:56:09 <snouto> how can i make the console logs during booting linux image quiet
Jun 10 20:56:14 <snouto> i have added it in local.conf
Jun 10 20:56:35 <snouto> APPEND += "rootfstype=ext4 quiet"
Jun 10 20:56:42 <snouto> but i think it has no effect
Jun 10 20:56:51 <snouto> sorry kergoth , but you are always helpful guys
Jun 10 20:57:36 <snouto> quiet there , i think it has no effect , the black scree with logs still appear , and i think when i changed to x86-64 with syslinux , the logs become apparent and even more
Jun 10 20:58:00 <kergoth> APPEND isn't obeyed everywhere. syslinux and grub-efi will obey it, generally, and even then only if you aren't using wic
Jun 10 20:58:08 <kergoth> check /proc/cmdline on target to see if it includes quiet
Jun 10 20:58:50 <snouto> nope
Jun 10 20:59:54 <snouto> kergoth , nope , it is not there brother
Jun 10 21:01:49 <snouto> kergoth, any idea !
Jun 10 21:03:03 <kergoth> what's your IMAGE_FSTYPES set to?
Jun 10 21:03:31 <kergoth> APPEND is only used when you're building a disk image with live/hddimg/vm/etc, not when directly using a kernel image and rootfs
Jun 10 21:03:35 <snouto> liv
Jun 10 21:03:42 <snouto> live
Jun 10 21:03:54 <kergoth> first, make sure append is what you think it is, i.e. the image dind't overwrite it
Jun 10 21:03:59 <kergoth> bitbake -e your-image | grep APPEND=
Jun 10 21:05:09 <snouto> does not show anything
Jun 10 21:05:17 <snouto> let me copy the whole local.conf in pastebin
Jun 10 21:05:52 <kergoth> change your APPEND += "rootfstype=ext4" to APPEND_append = " quiet" and check bitbake -e again
Jun 10 21:06:02 <snouto> http://pastebin.com/gwwrsbwx
Jun 10 21:06:37 <snouto> nothing
Jun 10 21:06:39 <snouto> returned
Jun 10 21:06:47 <kergoth> that's not possible. you must have something very broken
Jun 10 21:06:58 <kergoth> is your bitbake -e returning anything at all, without the grep?
Jun 10 21:07:19 <snouto> ERROR: Only one copy of bitbake should be run against a build directory
Jun 10 21:08:00 <kergoth> you can't run bitbake twice in the ame build dir
Jun 10 21:08:05 <kergoth> kill your existing bitbake first
Jun 10 21:08:19 <snouto> yes i did this , i am running it now
Jun 10 21:08:54 <snouto> your-image here is qemux86-64
Jun 10 21:09:02 <snouto> or "build"
Jun 10 21:09:06 <snouto> or core-image-minimal
Jun 10 21:09:31 <snouto> it is core-image-minimal
Jun 10 21:09:46 <snouto> here is the output
Jun 10 21:09:47 <snouto> ELF_APPEND="ramdisk_size=32768 root=/dev/ram0 rw console="
Jun 10 21:09:47 <snouto> APPEND=" rootfstype=ext4 quiet rootfstype=ext4 quiet quiet"
Jun 10 21:09:47 <snouto> TCLIBCAPPEND=""
Jun 10 21:10:02 <kergoth> qemux86-64 is a machine, not an image
Jun 10 21:10:18 <kergoth> good, so append is correct for the image
Jun 10 21:11:19 <snouto> now bitbake it
Jun 10 21:11:21 <snouto> ?
Jun 10 21:15:12 <snouto> still , i see the same logs
Jun 10 21:27:40 <snouto> kergoth, do you know of any video courses for yocto project for beginners
Jun 10 21:27:59 <snouto> any complete video courses online , video trainings ...etc
Jun 10 21:28:40 <snouto> is there anybody here knows anything related to video trainings for yocto project
Jun 10 22:36:49 <snouto> kergoth, please how can i prevent bootloader from showing the choice screen to boot in linux during the booting process
Jun 10 22:37:20 <snouto> i managed to install the live iso image into vbox , and each time i boot the vm , it shows me the bootloader choice screen to click and boot in linux , i don't want that
Jun 10 22:37:29 <snouto> i just want it to directly boot into the login screen
Jun 10 22:37:36 <snouto> how can i manage to do that ?
Jun 10 23:09:58 <snouto> kergoth: i am unable to use bridged adapter in vbox when i installed the iso live image into a vbox vm
Jun 10 23:10:18 <kergoth> i know less than nothing about our vm or live support
Jun 10 23:10:36 <kergoth> that said, you'd be better off using the vm image type than live, as then the userland tools should be installed
Jun 10 23:10:51 <kergoth> afaik anyway
Jun 10 23:11:03 <kergoth> but i've never used our live isos or vm support
Jun 10 23:11:03 <snouto> i think , it is something related to connman
Jun 10 23:11:54 <kergoth> there's a vboxguestdrivers recipe in meta-oe that sounds promising.
Jun 10 23:12:19 <snouto> kergoth: this would be your first lesson from me :)
Jun 10 23:12:28 <snouto> you spent more than two weeks teaching me , now , let me teach you
Jun 10 23:12:40 <kergoth> i have zero interest in our live cd or virtual machine support
Jun 10 23:12:57 <snouto> when i added connman connman-client connman-conf connman-plugins-ethernet to image_install_append
Jun 10 23:13:06 <snouto> i got connmanctl program
Jun 10 23:13:18 <snouto> installed onto /usr/bin/connmanctl
Jun 10 23:13:22 <snouto> from where i can enable wifi
Jun 10 23:13:26 <snouto> and ethernet ...etc
Jun 10 23:13:30 <snouto> let me confirm this to you
Jun 10 23:13:36 <snouto> let me boot the iso into vbox and install it
Jun 10 23:13:43 <snouto> and tell you the experiment result :)
Jun 10 23:15:19 <kergoth> as i said, i have no real interest in virtualbox support. connman should work fine if you configure it appropriately
Jun 10 23:15:40 <snouto> kergoth: how can i disable this bootloader choice screen
Jun 10 23:16:11 <snouto> yes , when i added connman-client to the image_install_append
Jun 10 23:16:18 <snouto> the internet eth0 interface was up and running
Jun 10 23:16:29 <snouto> and it took an IP address on my lan network successfully
Jun 10 23:16:38 <snouto> i can see the outside world from my image now
Jun 10 23:20:42 <snouto> kergoth: why are you not interested in live image , so how do you install your final linux image onto an appliance ?
Jun 10 23:21:14 <kergoth> I work on development boards that boot from sd or internal flash, so an installer is less than useless
Jun 10 23:22:40 <snouto> kergoth: this question is a bit very difficult for you
Jun 10 23:22:47 <snouto> or might be difficult :)
Jun 10 23:23:40 <snouto> now i discovered that /etc/apt/sources.list file is not found on my image , when i copied all the contents of my host ubuntu sources.list onto the vm that runs my qemux86-64 image , i can't install anything from ubuntu repository , since , my host machine is amd64
Jun 10 23:23:46 <snouto> i tried to do this
Jun 10 23:23:54 <snouto> sudo apt-get install python-pip
Jun 10 23:24:39 <snouto> it discovered all packages and dependencies for this package but at the end , when installing , it gaves me weird errors , i think because the ubuntu repository packages listed in sources.list is not compatible with the yocto linux or qemux86-64 image i have built
Jun 10 23:25:14 <snouto> so how can i download packages using apt-get install command for qemux86-64 image
Jun 10 23:25:37 <kergoth> that really doesn't make any sense
Jun 10 23:25:46 <kergoth> why would you have ubuntu feeds in sources.list on a yocto image?
Jun 10 23:25:56 <kergoth> you should not be doing that
Jun 10 23:26:03 <kergoth> packages from one distro are not going to work on another
Jun 10 23:26:14 <snouto> :( , i found this
Jun 10 23:26:15 <kergoth> that's true even among desktop distros (don't use opensuse packages on fedora), even more so with embedded
Jun 10 23:26:33 <snouto> :( petty my ignorance sir
Jun 10 23:26:44 <kergoth> either set up a package feed using your yocto build output, or add the packages to your image with IMAGE_INSTALL and rebuild the image, or copy the packages from tmp/deploy/ to your device and install them locally
Jun 10 23:26:45 <snouto> so how can i install python-pip
Jun 10 23:26:57 <kergoth> see above
Jun 10 23:27:20 <snouto> can i do one thing
Jun 10 23:27:40 <kergoth> i just gave you three options, pick one
Jun 10 23:27:46 <snouto> i am thinking of building an online repository on the cloud , and letting all running images at customers pointing to this repository
Jun 10 23:28:03 <snouto> then i can push packages and recent updates to all running embedded devices
Jun 10 23:28:06 <snouto> can i do this ?
Jun 10 23:28:19 <neverpanic> yes
Jun 10 23:28:25 <kergoth> what's what i just said, "set up a package feed using your yocto build output"
Jun 10 23:28:31 <snouto> oh i was about to panic , believe me
Jun 10 23:28:37 <snouto> neverpanic: thanks , good name
Jun 10 23:28:53 <snouto> using my build output ?
Jun 10 23:28:58 <snouto> what do you mean
Jun 10 23:29:08 <snouto> can you refer me some documentation in yocto websites
Jun 10 23:29:13 <snouto> to read more about this
Jun 10 23:30:44 <neverpanic> sounds like you want http://layers.openembedded.org/layerindex/branch/master/recipes/?q=python-pip to get a package for python-pip built
Jun 10 23:31:49 <snouto> exactly
Jun 10 23:32:02 <neverpanic> snouto: http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#package-feeds-dev-environment
Jun 10 23:33:05 <snouto> neverpanic: Thank you so much , this is all what i need
Jun 10 23:33:22 <snouto> you know guys what is weird in this yocto build system
Jun 10 23:33:41 <neverpanic> A lot of things, but I guess you have a specific idea?
Jun 10 23:33:42 <snouto> is that meta-python is included already in meta
Jun 10 23:33:50 <ant_home> kergoth: hi. Can you please confirm this is a python3 change fallout? http://pastebin.com/ug1EKqcq
Jun 10 23:34:08 <kergoth> snouto: meta is one layer, meta-python is a completely different layer
Jun 10 23:34:11 <kergoth> so no
Jun 10 23:34:38 <snouto> it is not in meta yes , it is in openembedded
Jun 10 23:34:42 <kergoth> ant_home: yep, that's definitely python 3 fallout
Jun 10 23:34:51 <kergoth> it's a layer in the meta-openembedded repository, yes
Jun 10 23:35:01 <snouto> yes
Jun 10 23:35:09 <kergoth> ant_home: change it to raise ValueError("Unknown section '%s'. Valid sections are: %s" % (section, dirmap.keys()))
Jun 10 23:35:27 <snouto> so if i included meta-openembedded in bblayers.conf
Jun 10 23:35:34 <snouto> pip python will be included
Jun 10 23:35:37 <kergoth> no, you'd include meta-python in bblayers.conf
Jun 10 23:35:38 <neverpanic> snouto: that's possible, but you could also build distributions using bitbake without using meta-openembedded
Jun 10 23:35:51 <kergoth> and no, that would make the recipe available, it won't magically appear in your image unless you add python-pip to IMAGE_INSTALL
Jun 10 23:36:01 <snouto> or do i have to refer to it in image_install_append
Jun 10 23:36:16 <kergoth> as i said, adding a layer to your config doesn't magically add all its recipes to your image
Jun 10 23:36:28 <kergoth> so yes, you'd need to add it to IMAGE_INSTALL
Jun 10 23:36:54 <snouto> oh ok
Jun 10 23:37:21 <snouto> thank you guys so much
Jun 10 23:37:36 <snouto> neverpanic: thank you for your help today , really appreciated
Jun 10 23:41:16 <ant_home> kergoth: I'll do, thanks
**** ENDING LOGGING AT Sat Jun 11 02:59:58 2016