**** BEGIN LOGGING AT Wed Mar 04 02:59:58 2015 Mar 04 09:13:59 hi Mar 04 14:45:16 khem: I sent two patches for v4l-utils. Please take a look Mar 04 17:18:04 https://plus.google.com/105083814157272466314/posts/S5AXQLkGLej Mar 04 17:18:08 fray and RP Mar 04 17:19:23 moin Mar 04 17:21:08 Crofton|work: gah Mar 04 17:21:19 nice photo Mar 04 17:23:58 I'm trying to get a Makefile based project (cryptopp) to build native, but the headers and libs are not being installed. Does anyone have any suggestions what might be missing? here are the files: https://gist.github.com/cbrake/35ab968c0b78eba99631 Mar 04 17:24:16 * guess I should say the headers and lib are not being staged Mar 04 17:24:54 if the files go into the correct place in do_install, then they'll be staged Mar 04 17:25:04 so presumably either nothing was installed, or it didn't go to the right places Mar 04 17:25:09 ok Mar 04 17:25:26 that recipe seems to work fine with -native Mar 04 17:25:28 i am curious about the patches, though, since it should be obeying our cflags variables anyway, not its own Mar 04 17:25:35 * works fine without -native Mar 04 17:26:11 well, first of all, you don't obey ${prefix} Mar 04 17:26:14 you'r ehardcoding /usr Mar 04 17:26:30 given native.bbclass overrides the prefixes, i'm guessing thats your problem Mar 04 17:27:26 ok, thanks -- I'll dig into that Mar 04 17:28:00 beyond that, you should really fix your extra_oemake to pass in everything else, not just CC :) but not related to your problem Mar 04 17:40:04 RP: are you short on yocto stickers? Mar 04 17:43:31 nerdboy: why? Mar 04 17:46:32 looks like fray has them all... Mar 04 17:47:38 * nerdboy apparently short on caffeine/humor today Mar 04 18:32:16 khem: wanted to let you know regarding this u-boot and toolchain issue I had, our u-boot was from 2009 ;) this is the reason why it did not compile with hf, the imx u-boot in OE is newer and it has no problems with a hf toolchain; we'll be updating ours I guess Mar 04 18:37:18 right :) Mar 04 18:39:59 abelloni: so mystery solved :) Mar 04 19:19:05 Jin^eLD: very clever decision ;) Mar 04 19:20:33 maybe it was just a cluebat on management? either way, keep it up... Mar 04 19:22:25 otavio: well, luckily we had someone who knows how to do it ;) I'm really a userspace guy and don't feel well close to hardware :> Mar 04 19:26:22 u-boot's not too bad, very kernel-like in config/build setup Mar 04 19:26:55 nerdboy: well, build setup is one thing but getting a new u-boot to work with the hardware is another... especially when the vendor shipped the old u-boot as a tarball without any commit history Mar 04 19:27:35 different versions can be a little finicky with reading the boot/partitions depending on fs... Mar 04 19:27:46 *boot/root Mar 04 19:27:50 I tend to stay away from such low-level things, not really my area :) Mar 04 19:28:18 meh, get a serial cable and do printenv Mar 04 19:28:27 you'll figure it out... Mar 04 19:29:13 closer to latest upstream(denx) you are the better, mostly Mar 04 19:29:33 I already found someone who will ;) and he's actually still struggling because it turned out not to be as straightforward as expected Mar 04 19:29:44 unless your machine is really old/funky... Mar 04 19:30:26 it's some icnexus made imx thingy Mar 04 19:30:29 send him over here if he has questions Mar 04 19:31:06 sure, thanks Mar 04 19:31:30 although I think he's fine in that regard, he's a lowlevel hacker actually, hacks kernels for proprietary tablet chipsets and stuff like that Mar 04 19:31:33 or #gentoo-embedded (just mention u-boot, not the other stuff ;) Mar 04 19:31:42 :) Mar 04 19:32:06 in the sense of ports oss kernels to get rid of the proprietary drivers Mar 04 19:32:39 * nerdboy on the integration/testing end of that Mar 04 19:32:49 :> Mar 04 19:33:18 gimme somethinn' to test Mar 04 19:34:06 I really don't know what he is working on recently, I think they were hacking rockchip Mar 04 19:34:14 that part he does as a hobby :) Mar 04 19:34:25 * nerdboy beating up tegra K1 currently Mar 04 19:34:38 I can ask him to ping you if you like Mar 04 19:34:52 rockchip runs sunxi kernel? Mar 04 19:35:00 with mali? Mar 04 19:35:12 I have no idea, I'm not involved in those things :) remember - userspace guy ;) Mar 04 19:35:22 * nerdboy has one allwinner device but no rockchips Mar 04 19:35:37 aah, no, rockchip is not allwinner Mar 04 19:35:44 rockchip is rockchip, I do not think it is sunxi related Mar 04 19:36:15 right, but i thought it was running the same-ish kernel? Mar 04 19:36:29 * nerdboy could be misremembering Mar 04 19:36:29 hmm.. ok, well, I do not think I can answer that question :) Mar 04 19:36:46 like i said, no rockchip devices Mar 04 19:37:14 I have one, I hacked a little bit to port twrp on it but later figured out that android actaully sucks big time and I lost interest after that Mar 04 19:37:42 so its rooted but running stock firmwrae and I barely use it anyway because I do not like touch based devices Mar 04 19:38:36 I did not try to run linux on it, just did not care anymore, my gf is using it to read lecture books at the university so she does not have to carry paper around, that's all we use it for Mar 04 19:38:52 and I wish android used OE, their build system is really a pain Mar 04 19:51:06 Jin^eLD, ++ Mar 04 19:51:41 :) Mar 04 20:03:47 webos? Mar 04 20:03:53 never tried Mar 04 20:04:19 best touch interface i've tried... Mar 04 20:04:32 *least annoying for sure... Mar 04 20:04:42 It was OE based too. Mar 04 20:05:36 there is "open" webos Mar 04 20:05:43 * nerdboy hasn't looked at it Mar 04 20:06:12 but i believe that was from before the LG deal? Mar 04 20:06:36 yes, originally. Mar 04 20:08:15 hmm,guys: QA Issue: task-usb-audio rdepends on kernel-module-snd-usbmidi-lib, but it isn't a build dependency Mar 04 20:08:20 why would it warn for packagegroups? Mar 04 20:08:36 it's clear that a packagegroup has no build dependencies, only RDEPENDS? or did anything change here? Mar 04 20:10:33 * Jin^eLD is still migrating from poky 1.5.3 to poky 1.7.1 Mar 04 21:05:51 ok, cryptopp-native is working, but I broke the cross build: https://gist.github.com/cbrake/35ab968c0b78eba99631 Mar 04 21:07:47 for the cross build, prefix is set as such: export prefix="/usr" Mar 04 21:08:09 so trying determine what variable I should be using, and is there a common one between native and cross builds Mar 04 21:10:58 (cmake is a wonderful thing -- most things *just work* when that is used ...) Mar 04 21:11:36 cbrake: LOL Mar 04 21:13:07 except when it doesn't, then it's terrible beast :) Mar 04 21:14:32 well from my experience in 90% of cases I had to use cmake - it did not work and was really terrible to use Mar 04 21:14:35 Jin^eLD: my first concern would be you're mentioning a 'task' recipe, which is something old (not packagegroup), yet that message is from current oe-core. are you using mismatched layer branches? Mar 04 21:14:36 it's on top of my shitlist :) Mar 04 21:15:07 kergoth: nono, the package name just is "task" for legacy reasons but it inherits packagegroup, it has been working fine in 1.5.3 Mar 04 21:15:14 I guess I referred to it in old lingo Mar 04 21:15:34 that error message generally indicates that automatic rdeps (e.g. shlibs) added a runtime dependency that wasn't known about at build time Mar 04 21:15:45 but your task shouldn't be shipping any files, so i don't see how that could occur Mar 04 21:16:04 hmm I wonder where I messed up this time Mar 04 21:16:15 * kergoth shrugs Mar 04 21:17:56 kergoth: https://gitorious.digitalstrom.org/dss-oe/dss-oe/blobs/master/yocto/dS/meta-digitalstrom-devel/recipes-core/tasks/task-usb-audio.bb Mar 04 21:18:01 that's the recipe Mar 04 21:18:04 I do not see anything weird there Mar 04 21:18:26 do you? Mar 04 21:24:06 and if you don't - any hints on how to debug this? Mar 04 21:24:17 actually I could unpack the ipk and see if something creeped inside Mar 04 21:25:23 nope, unpacked data is empty Mar 04 21:25:52 so how could that happen?? Mar 04 21:29:36 I checked out oe-core and built core-image-minimal (even got it booting on my development system). I figured I'd try something a bit more ambitious and build core-image-lsb. Do I need to keep adding things to DISTRO_FEATURES until I've satisfied core-image-lsb? What's correct way to build core-image-lsb? Mar 04 21:42:25 well, not sure if it's the correct way but I kept adding stuff to DISTRO_FEATURES and it's building now Mar 04 21:48:37 Jin^eLD: looks reasonable.. no idea, honestly Mar 04 21:49:00 georgem: use the poky-lsb distro? Mar 04 22:29:06 kergoth: any hints how to debug it? Mar 05 00:46:17 RP: around ? **** ENDING LOGGING AT Thu Mar 05 02:59:59 2015