**** BEGIN LOGGING AT Sat Dec 05 02:59:58 2015 Dec 05 04:24:24 kergoth: Thanks. I assume it's best to stick closely to that for recipes, eh? Dec 05 14:14:56 Hello, I am a beginner using yocto. I have made a custom layer with a non-yocto kernel (Linus's tree), it compiles and installs fine but at do_package i get these errors http://pastebin.com/t0uxgW7A . I googled around a bit and saw that I should remove these in the do_install function. Could anyone give me a hint on how I can do that? Dec 05 15:47:48 i just added this to my recipe and it seems to have fixed it Dec 05 15:47:51 do_install() { Dec 05 15:47:52 for x in `find ${B}*.ko.gz`;do Dec 05 15:47:54 rm $x Dec 05 15:47:56 done Dec 05 15:47:57 } Dec 05 15:53:22 obsrwr, your assuming there is no space in paths Dec 05 15:54:15 find -iname -exec rm -f "{}" Dec 05 15:54:22 will be safer isnt it ? Dec 05 15:55:21 crap, yes Dec 05 15:55:24 thanks Dec 05 15:55:43 you're welcome Dec 05 15:56:12 btw they could be other ways Dec 05 15:57:16 I'm sure they could :) but baby steps Dec 05 17:48:17 that for loop will execute the find command each time through the loop Dec 05 17:49:58 you know i never really thought it like that in bash Dec 05 17:50:42 * nerdboy still on first coffee... Dec 05 17:50:55 but bash is a little weird sometimes Dec 05 17:50:57 it's not production code anyway, this is me playing with yocto outside of work xD Dec 05 17:51:52 still had a few problems after the rootfs was built, i couldn't mount the ext4 img Dec 05 17:52:01 so i'm doing a clean build now Dec 05 17:54:21 * nerdboy looking at bash stuff Dec 05 17:55:19 that's right, it's mostly the quoting/expansion of (possible) weird stuff Dec 05 17:56:14 a glob/regex is safest in the first line i think Dec 05 18:02:32 exactly what does ${B} expand to though Dec 05 18:03:14 where did you get that? Dec 05 18:03:56 i read it in the reference manuals, said it's the build directory, tried it, seems to have worked Dec 05 18:04:12 it says it's where objects end up in Dec 05 18:04:27 http://www.yoctoproject.org/docs/1.8/dev-manual/dev-manual.html#build-directory Dec 05 18:05:06 oh damn it's actually the 2nd path after sourcing oe-init Dec 05 18:05:30 i did a really dumb thing Dec 05 18:05:32 :) Dec 05 18:06:01 that deletes all the modules for all my machines Dec 05 18:07:57 because that's all i do in the do_install also, i think none of the modules actually get into my rootfs either Dec 05 18:08:52 how do you guys write a custom kernel layer? i just took linux-yocto-custom.bb Dec 05 18:09:14 B should be build dir Dec 05 18:09:34 and this is the nice but non-posix way: Dec 05 18:09:47 find . -name '*.temp' -delete Dec 05 18:10:13 plus quote your variables Dec 05 18:10:35 rm "${x}" Dec 05 18:10:59 this is common practice? Dec 05 18:11:18 common practice for recipes? Dec 05 18:11:22 yes Dec 05 18:11:47 probably shouln't depend on gnu extensions Dec 05 18:12:01 ah Dec 05 18:12:25 but you don't need a loop for that anyway Dec 05 18:13:08 so. find . -name '${B}*.ko.gz' -delete ? Dec 05 18:14:17 find "${B}"/foo -name \*.ko | xargs -0 rm Dec 05 18:14:41 er, -print0 before the pipe Dec 05 18:15:21 oh, got it Dec 05 18:23:11 i read that do_install opies from B to D so i'll replace {B} with {D} and see if that works better Dec 05 18:23:23 beause the problem is really do_package in my ase Dec 05 18:23:28 case* Dec 05 18:25:36 here's a nice one from an ebuild: find . -name Makefile.in -print0 | xargs -0 sed -i -e 's:-W\(error\|extra\)::g' Dec 05 18:28:01 :) Dec 05 18:32:18 to be "safe" should really do rm -f or -rf on the end of xargs Dec 05 18:40:51 huh Dec 05 18:40:52 http://pastebin.com/tu9sN2NJ Dec 05 18:41:06 do_install() { Dec 05 18:41:07 find "${D}" -name \*.ko.gz -print0 | xargs -0 rm Dec 05 18:41:09 } Dec 05 18:44:07 getting slightly bizzare Dec 05 18:50:04 wait, i'm a moron Dec 05 18:50:06 nevermind Dec 05 18:50:55 can't possibly be something in D cause i'm overriding the do_install function Dec 05 18:53:04 __yeah__, i gotta find a better way Dec 05 18:53:48 Please set FILES such that these items are packaged. Alternatively if they are unneeded, avoid installing them or delete them within do_install. Dec 05 18:54:03 how do i get those modules packaged Dec 05 19:11:45 it just told you Dec 05 19:11:52 set the FILES variables to include those paths Dec 05 19:11:55 see the reference manual Dec 05 19:17:51 oh, FILES_${PN}.. i have seen the light **** ENDING LOGGING AT Sun Dec 06 02:59:58 2015