**** BEGIN LOGGING AT Tue Jun 09 02:59:58 2015 Jun 09 08:09:22 morning all Jun 09 08:11:56 hi bl Jun 09 08:12:31 hi woglinde Jun 09 08:15:58 gm Jun 09 08:52:36 what might be a reason that kernel headers are incomplete on the target respectively in the sysroot? the module in question get compiled and installed, but the related header for ioctls is missing Jun 09 08:53:24 but otherwise /usr/include/linux seems to be populated Jun 09 08:55:09 hu Jun 09 08:55:12 hi rather :) Jun 09 12:50:41 Jin^eLD: long time. Hi! Jun 09 12:50:47 hey likewise! Jun 09 12:50:53 indeed, long time, how are you? Jun 09 12:50:56 what are you up to these days? Jun 09 12:51:15 Jin^eLD: have been doing much FPGA programming. Now back for i.MX6. Jun 09 12:51:28 Jin^eLD: and you? Jun 09 12:52:13 mostly same as always - userspace application stuff, I'm not friends with hardware ;) Jun 09 12:53:29 imx sounds familiar though, got such a box too, we build OE for it Jun 09 12:53:32 :) Jun 09 13:47:37 i hate vendor tools... "ERROR: This installation is not supported on 32 bit platforms." -- > uname "x86_64"... sigh Jun 09 13:48:14 nrossi: yeah, ain't no fun without a proper Evil Vendor Tree Jun 09 13:48:24 nrossi, odd hour for you? Jun 09 13:48:33 odd indeed Jun 09 14:21:23 What are the .sigdata files for in the stamp directory? I'm looking in siggen.py and I'm not sure if I understand. Do these files contain signatures that just haven't been hashed and stored as a stamp file? Jun 09 14:28:01 consmith: that's a pickled version of the components that went into the signature - it can be used with bitbake-dumpsig / bitbake-diffsigs / other tools for debugging Jun 09 14:29:35 bluelightning: should there be tasks that have sigdata files but not regular stamps? When are the sigdata files generated? Jun 09 14:33:08 consmith: the sigdata file gets generated at stamp creation time AFAIK Jun 09 14:33:54 but you can use bitbaek -S to generate them without executing the tasks and creating the stamps Jun 09 14:34:04 bluelightning: so for every stamp there should also be a sigdata file? That's not what I'm seeing, so I'm a bit confused. Jun 09 14:34:24 JaMa: ah, so there may be tasks that have sigdata but not a stamp? Jun 09 14:35:51 yes, rm_work also removes some stamp files, but can leave sigdata files Jun 09 14:36:33 JaMa: perfect, thanks! Jun 09 14:56:56 * joeythesaint wonders if anyone has set up a patchwork server for stuff outside bitbake/oe/oe-core. Jun 09 14:57:48 Because I would love to use the patchwork workflow for meta-selinux, but I'm not thrilled with the idea of setting up my own patchwork. Jun 09 14:59:17 joeythesaint: we're starting to do that here but mainly as a staging point for work on patchwork itself Jun 09 15:01:17 bluelightning: Ah. I've been using some pretty brittle imapfilter rules right now and it's highly unsatisfactory, but when I started investigating how to set up patchwork I fell back to "I must be repeating work someone else has already done." Jun 09 15:02:13 Maybe I'll take another run at fixing my broken lua again. Jun 09 15:03:11 I believe we should be able to support additional projects in the OE patchwork btw Jun 09 15:03:22 that's probably the easiest solution Jun 09 15:07:05 That'd be ideal, if that's possible. I just assumed the OE patchwork was intended to be kept as small as possible. Jun 09 15:07:22 Who might I ask about that to see if it's an option? Jun 09 15:07:26 additional projects shouldn't be too much of a burden Jun 09 15:08:32 I don't think there's a formal process; I don't have admin rights myself but khem or tom k. might be the people to speak to (I should really find out, so if you could add me on CC that would be great...) Jun 09 15:10:52 Will do. Jun 09 15:19:25 From stackoverflow: http://stackoverflow.com/questions/30385436/use-yocto-to-extend-a-read-only-filesystem-with-extra-packages Jun 09 16:07:58 I am trying to do a build for the jetson tegra tk1 board and I keep getting error with do_kernel_checkout Jun 09 16:08:06 here is the log: http://pastebin.com/YFsQDxfD Jun 09 16:10:32 is there a quick fix for checking out the kernel? Jun 09 16:14:30 hoi hrw Jun 09 16:14:46 reconnect ;D Jun 09 16:15:06 sdh11 you checkout to the direcotroy git where the recipes needs the directory linux Jun 09 16:15:20 hrw okay Jun 09 16:15:30 sdh11, did you update the manifest I agce you to fido? Jun 09 16:15:45 you may be mixing version expectations Jun 09 16:16:01 hrw what was your blog adresse again? Jun 09 16:16:19 http://marcin.juszkiewicz.com.pl Jun 09 16:16:56 no. i was still trying to build on dizzy. let me try that Jun 09 16:20:08 hrw thanks Jun 09 16:34:42 is someone still accpeting patches for dora? Jun 09 16:35:03 we found a long stending depency problem for python-netserver Jun 09 16:35:06 someone should be, but better to ping them in e-mail Jun 09 17:20:28 Crofton|work: You were wondering why im online at odd hours, https://lists.yoctoproject.org/pipermail/meta-xilinx/2015-June/001023.html Jun 09 17:21:09 yeah I saw that Jun 09 17:22:00 I have days when I want to slap some sense into Xilinx :) Jun 09 17:22:31 Crofton|work: that happens pretty much everyday no? :P Jun 09 17:22:49 depends on what sort of problems I am having Jun 09 17:23:02 the target of my annoyance shifts regularly Jun 09 17:23:30 moving targets a harder to hit, you should stop moving them :) Jun 09 17:24:08 very true Jun 09 17:24:24 and shooting at three or four at once is bad :) Jun 09 17:24:45 thats why they made the buck shot :) Jun 09 17:29:20 hit a very odd bug... infinite build path in glib. Cause the file was created in the future :|... that will teach me to keep my virtual machine sync'd :) Jun 09 17:31:02 * Crofton|work laughs Jun 09 17:39:19 * nrossi thinks 'great scott' is the expected response Jun 09 18:31:08 do sstate and stamp files not share the same checksum/signatures? Jun 09 19:21:19 sdh11, my build with master does complete Jun 09 20:22:18 Crofton|work, which bsp? The first I sent you? Jun 09 22:03:58 I built from khem's **** ENDING LOGGING AT Wed Jun 10 02:59:59 2015