**** BEGIN LOGGING AT Wed Jul 22 02:59:59 2015
Jul 22 06:22:32 <LukasW> Hello together. I have a question about yocto: Iam working on a yocto-linux for a TI OMAP-L138, which is a ARM9+DSP in one package. The Linux is running fine, and does everything i want. I have implemented a kernel driver to start the DSP-Core from the Linux on the ARM9-Core, but now i need to generate the Firmware for the DSP with the Yocto buid system. Main problem is, that i need a compiler from TI to compile the Code for the DSP 
Jul 22 06:23:42 <LukasW> How do i write a recipe to download an place the compiler from TI-Website to my yocto build environment, and NOT to my target?
Jul 22 06:24:40 <LukasW> ... so i can use that compiler in another recipe to generate the firmware for the DSP from my sources?
Jul 22 07:16:58 <Ox4> hey guys
Jul 22 07:17:09 <Ox4> how to remove LDFLAGS for the particular package?
Jul 22 07:41:50 <btooth> good morning
Jul 22 07:41:51 <btooth>  have a vmdk image.. but this only boots until "EXT3-fs (hda2): mounted filesystem with ordered data mode" .. booting the iso image it
Jul 22 07:41:54 <btooth> will boot further into systemd. do you have any idea?
Jul 22 08:51:32 <abelal> Hi guys
Jul 22 08:52:24 <abelal> the linux kernel development manual suggests that the preempt-rt config inherits from standard
Jul 22 08:52:35 <abelal> i am building for x86_64
Jul 22 08:53:17 <abelal> but the configuration (.config) i end up with is way too different from the standard branch final .config
Jul 22 08:53:56 <abelal> can anybody please guide me how I can debug the configuration process to root cause the issue
Jul 22 09:17:31 <Ox4> kergoth: hey
Jul 22 09:17:46 <Ox4> kergoth: I have responded you on github
Jul 22 09:54:28 <Ox4> also where can I find d.getVar definition?
Jul 22 10:15:04 <drix> hi guys
Jul 22 10:15:37 <drix> i've got a issue that i'm not able to get rid off, could someone help me plz ?
Jul 22 10:15:48 <drix> here's the trace: http://paste2.org/WwgB23D1
Jul 22 10:24:27 <AzaToth_> Looking through http://git.yoctoproject.org/cgit/cgit.cgi/yocto-autobuilder/commit/?id=ab0b9dd35d31a59918408558c62d35dd3e649d83 I can't figure out how this commit could add a button
Jul 22 11:20:16 <nuil> somebody already tried to get a working openjdk-8 working_
Jul 22 11:22:07 <rink_> get a working X working ...
Jul 22 11:22:17 <nuil> done
Jul 22 11:48:01 <davis> hello
Jul 22 11:49:23 <davis> ls
Jul 22 11:54:06 <davis> I'm new to yocto and beaglebone
Jul 22 11:54:48 <davis> I've downloaded poky and the beaglebone bsp. I've also downloaded the tools and built/run the qemu santos image.
Jul 22 11:55:41 <davis> i would like to build the beaglebone image now. Am I supposed to move the beaglebone bsp into the poky dir and replace/supplement the meta dirs there with the beaglebone version?
Jul 22 11:56:52 <raykinsella78> Its fishy really
Jul 22 11:57:36 <AzaToth_> Atm i have one recipe building a rootfs, and another recipe making an installable image; and I need to manually build the rootfs recipe before building the iso recipe; I've tried to add the rooffs recipe as a DEPENDS to no avail. Anyone got a clue what I might do wrong?
Jul 22 11:57:49 <AzaToth_> ±spelling
Jul 22 12:07:42 <bboozzoo> davis: beaglebone-bsp as in meta-ti?
Jul 22 12:18:03 <davis> bboozzoo: im not sure about meta-ti. I pulled the bsp from git://git.yoctoproject.org/meta-yocto -b daisy as listed https://www.yoctoproject.org/downloads/bsps/daisy16/beaglebone
Jul 22 12:19:57 <kido> hi, I wonder if I can put the same FEATURES in IMAGE_FEATURES and DISTRO_FEATURES or if there is a list of possible FEATURES that can be set on each ?
Jul 22 12:20:02 <bboozzoo> davis: you should be fine with fido or master
Jul 22 12:20:40 <bboozzoo> then just set your MACHINE="beaglebone" in local conf and to the build
Jul 22 12:21:19 <davis> bboozzoo: for the build system, I pulled git clone -b fido git://git.yoctoproject.org/poky.git
Jul 22 12:21:38 <davis> perhaps I should have pulled the third one there which was daisy?
Jul 22 12:23:58 <bboozzoo> davis: all files are already there, you just clone poky, then source oe-init-build-env, set MACHINE="beaglebone" in local.conf and run bitbake core-image-minimal, once that finishes, you can just prep a SD card image with wic (wic create -e core-image-minimal sdimage-bootpart) and skip the fdisk part of the manual
Jul 22 12:24:27 <davis> bboozzoo: sounds good. i'll try that.
Jul 22 12:24:39 <davis> bboozzoo: I apprecaite your help. Thank you!
Jul 22 12:25:34 <davis> btw, can I keep the qemu and the beaglebone simultaneously and swith back and forth as needed without rebuilding everything?
Jul 22 12:27:52 <AzaToth_> wonder if EXTRA_IMAGEDEPENDS is what I'm looking for...
Jul 22 12:58:00 <mcfrisk> does bitbake have timeouts for do_fetch? I have wget stuck on a misbehaving svn repo with -t 2 and -T 360 but the download seems to be stuck somewhere else for more than 10 minutes
Jul 22 13:01:20 <AzaToth_> so, what might be the best solution if I want to include a rootfs.tar.gz in an other rootfs which is gonna be an iso?
Jul 22 13:15:35 <WarheadsSE> anmyone recognize this issue? pseudo: uh-oh!  '/proc/XXXX/fd/3' seems to be a symlink, but I can't read it.  Ignoring. Can't open /proc/XXXX/fd/3: Is a directory
Jul 22 13:17:20 <bluelightning> mcfrisk: wget stuck on an svn repo? wget shouldn't be fetching from svn...
Jul 22 13:21:31 <AzaToth_> i.e. I want to make take foo-${MACHINE}.tar.gz and place it in foo-installer-${MACHINE}.iso etc..
Jul 22 13:21:40 <mcfrisk> bluelightning: we're using wget to https svn repo to avoid credential crap with svn, .netrc is enough, but timeouts are not working somehow..
Jul 22 13:21:43 <AzaToth_> as a separate file
Jul 22 13:25:03 <AzaToth_> anyone?
Jul 22 13:28:58 <bluelightning> AzaToth_: EXTRA_IMAGEDEPENDS just says that the do_populate_sysroot task for the items listed needs to have been run before the image is built
Jul 22 13:29:50 <bluelightning> I don't think that's really what you want
Jul 22 13:30:56 <bluelightning> you could try looking at our live image support and maybe do something like what it does
Jul 22 13:31:06 <AzaToth_> bluelightning, ok
Jul 22 13:31:12 <bluelightning> meta/classes/image-live.bbclass (which uses bootimg.bbclass)
Jul 22 13:31:43 <WarheadsSE> bluelightning: any input on the problem on of my devs is having with all instances of bitbake he is trying to use ?
Jul 22 13:31:57 <bluelightning> WarheadsSE: none I'm afraid, never seen that error before
Jul 22 14:56:14 <WarheadsSE> bluelightning: might be hitting an oddity in apparmor all of a sudden.
Jul 22 14:56:19 <WarheadsSE> we're looking into it
Jul 22 14:57:34 <bluelightning> WarheadsSE: it may be worth noting that dora is now nearly two versions out of support
Jul 22 14:57:53 <WarheadsSE> Yes, we know. this last release will be the last we use with dora.
Jul 22 14:58:08 <WarheadsSE> (out the door in about a week), then we're moving all the way up
Jul 22 15:30:14 <rburton> joshuagl: the mesa sed patch on the list from yesterday is for fido, btw
Jul 22 16:04:26 <joshuagl> rburton: ack, have the mail open on my busy desktop :-)
Jul 22 17:39:12 <Crofton|work> zeddii, any idea what this means?
Jul 22 17:39:28 <Crofton|work> ERROR. Could not locate meta series for zynq
Jul 22 17:39:38 <Crofton|work> from a kernel do_patch
Jul 22 17:41:21 <zeddii> it means that the BSP description + configuration wasn't found so the series that controls the patch phase wasn't generated. is this with current master ? If I can poke at it, I can be more specific.
Jul 22 17:41:46 <Crofton|work> yeah current master
Jul 22 17:41:53 <Crofton|work> something similar worked
Jul 22 17:41:58 <Crofton|work> a few days ago
Jul 22 17:42:10 <Crofton|work> I'm looking for stupid typos atm
Jul 22 17:42:19 <zeddii> interesting. nothing should have merged to impact that. My new series I sent could do that .. but it isn;t merged.
Jul 22 17:42:35 <zeddii> Crofton|work, I feel your pain. I built, booted and stress tested qemuarm on 4.1
Jul 22 17:42:44 <Crofton|work> I'm pretty sure it worked at least :)
Jul 22 17:42:46 <zeddii> and then when I go back to it today .. nothing, boot hang.
Jul 22 17:42:57 <zeddii> and now I can't get it too boot on any kernel, any config.
Jul 22 17:43:00 <Crofton|work> so of course I blame you
Jul 22 17:43:10 * zeddii is used to it.
Jul 22 17:43:14 <zeddii> :)
Jul 22 17:43:36 <Crofton|work> the error reporting doesn't help me solve problems
Jul 22 17:44:00 <Crofton|work> while you are here, do al .cfg files need to be called out in an scc file
Jul 22 17:44:08 <zeddii> can you pastebin the layers ?
Jul 22 17:44:10 <Crofton|work> It appears just addingthe cfg file works
Jul 22 17:44:31 <zeddii> Crofton|work. nope. they can just be right on the SRC_URI. or in a .scc file. either works.
Jul 22 17:44:36 <Crofton|work> ok
Jul 22 17:45:11 * zeddii wonders if gcc 5.1 is his pain source.
Jul 22 17:47:17 <Crofton|work> heh
Jul 22 17:47:22 <Crofton|work> blame someone else
Jul 22 17:48:31 <zeddii> buy myself some time. smashing my head into my desk isn't helping.
Jul 22 17:48:57 <Crofton|work> let me stash changes and see if old one builds
Jul 22 17:55:54 <Crofton|work> zeddii, the recipe works, only broke after I tried updating with new patches from the developer
Jul 22 17:56:01 <Crofton|work> you are likely off the hook
Jul 22 17:56:10 <Crofton|work> except for the not so helpful error messages
Jul 22 17:56:40 <Crofton|work> any kind of ordering needed with scc cfg and patch files
Jul 22 17:56:44 <zeddii> agreed. I have some changes there. but I did actually take a note.
Jul 22 17:57:04 <zeddii> Crofton|work, nope. you can mix and match. with obvious patch ordering implications.
Jul 22 17:57:23 <Crofton|work> but a problem there would lead to a patch fail in the log
Jul 22 17:57:31 <zeddii> yep.
Jul 22 17:57:50 <zeddii> there were some missed return codes back in the day .. but they are caught now.
Jul 22 17:58:08 <zeddii> gah.
Jul 22 17:58:09 <zeddii> perf.
Jul 22 17:58:15 * zeddii dives into a perf failure now.
Jul 22 18:10:11 <Crofton|work> zeddii, one char error in a file name, between scc and SRC_URI
Jul 22 18:10:47 <zeddii> ok. I can make that same error here, and craft a better debug message.
Jul 22 18:12:22 <Crofton|work> that would be helpful
Jul 22 18:12:30 <Crofton|work> you shoudl certainly be able to dupe it
Jul 22 18:28:11 <r22s> Hi all, I'm trying to install elasticsearch and am running into a dependency issue.  I bet it's a simple fix but haven't found the answer yet.
Jul 22 18:28:28 <r22s> *not install, trying to build an image that includes elasticsearch
Jul 22 18:28:48 <r22s> During do_rootfs, I see the following error:
Jul 22 18:29:08 <r22s> ERROR: Unable to install packages. Command '...' returned 1:
Jul 22 18:29:19 <r22s> error: elasticsearch-1.7.0-r0 requires libc.so.6(GLIBC_2.0)
Jul 22 18:29:22 <r22s> error: elasticsearch-1.7.0-r0 requires libc.so.6(GLIBC_2.1)
Jul 22 18:29:26 <r22s> error: elasticsearch-1.7.0-r0 requires libc.so.6
Jul 22 18:30:27 <r22s> I'm including glibc 2.20 as part of the build, and the .so.6 symlink is there as well.
Jul 22 18:30:29 <r22s> Any ideas?
Jul 22 19:41:44 <khem`> r22s: is elasticsearch precompiled
Jul 22 19:49:37 <r22s> khem`: It's a few bash scripts that call into java .jars
Jul 22 20:11:23 <abelloni> is there some yocto dev day planned before/after elce ?
Jul 22 20:27:57 <acidfu> abelloni, what is elce
Jul 22 20:28:04 <acidfu> ?
Jul 22 20:31:04 <abelloni> embedded linux conference europe
Jul 22 20:31:19 <acidfu> ah ;)
Jul 22 23:38:27 <Happycat> Hi !
**** ENDING LOGGING AT Thu Jul 23 02:59:59 2015