**** BEGIN LOGGING AT Fri Jun 09 03:00:04 2017 Jun 09 06:06:40 morning all Jun 09 06:07:29 quick and possibly stupid question ... how can one build a kernel module ? (resulting a .ko file in the end) Jun 09 06:07:56 I mean are there any recipes available in yocto for kernel modules Jun 09 06:07:58 ? Jun 09 06:08:00 thanks Jun 09 06:09:36 i think i found the answer :) Jun 09 06:09:37 http://wiki.kaeilos.com/index.php/Howto_build_a_kernel_module_out_of_the_kernel_tree Jun 09 07:08:59 good morning Jun 09 08:27:20 Good morning all, i have a few question for you :-) I would like to build my own kernel module for ARM target, everything works fine in Yocto but i would like to be able to share custom kernel source to an other team in order to let him build their modules. But i'm not able to find kernel sources after sdk install ... any advice ? :) Jun 09 08:28:13 currently i'm buildding a new sdk with : TOOLCHAIN_TARGET_TASK_append += "kernel-devsrc"TOOLCHAIN_TARGET_TASK_append += "kernel-devsrc" option... still buildding Jun 09 09:04:31 does anyone knows if it would be possible to install sdk from rpms? (with smart for example) Jun 09 09:05:30 with sysroot and so on Jun 09 09:30:03 hello Jun 09 09:30:24 is there a way to say if [[ recipe exist ]]; then do something; fi ? Jun 09 09:31:07 in a script set to exit on any error Jun 09 09:31:38 cornel : when you RDEPENDS from something, and nothing provides it , it will give you an error. Jun 09 09:31:59 cornel : or DEPENDS ... Jun 09 09:32:14 Hi where can i finde all arguments like SDK_FEATURES and RDEPEND and what they mean ? Jun 09 09:32:47 MarcWe : In the yocto project reference manual Jun 09 09:32:48 ChrysD, the whole idea is to avoid set +e/set -e around $(bitbake -n ) in a bash script Jun 09 09:33:34 ChrysD: Tnx Jun 09 09:34:03 MarcWe : Search for " Variable Glossary " Jun 09 09:34:33 MarcWe : The n° chapter could be between 12 to 14 ( depends of the version of the document ) Jun 09 09:35:30 MarcWe : http://www.yoctoproject.org/docs/2.3/ref-manual/ref-manual.html#ref-variables-glossary Jun 09 09:35:47 ChrysD: oke i only exeded on the mega man Jun 09 09:35:53 tnx verymuch Jun 09 09:59:34 Is it possible to SRC_URI by git on files in gitlab that are in private? Jun 09 10:02:57 can i block a xml file of being installed by a selected recipe Jun 09 10:03:29 MarcWe: you can delete the file in a do_install_append() { rm ${D}/path/to/file } Jun 09 10:28:54 rburton: where can i look up all variables like ${D} Jun 09 10:29:08 rburton: btw tnx Jun 09 10:29:48 the meaning or what they actually contain? Jun 09 10:30:25 http://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html is usually quite helpful Jun 09 10:31:38 tnx whana know witch vars i can use and sort of what they contain Jun 09 10:33:06 http://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#ref-variables-glossary Jun 09 10:33:40 if you want to get the actual contents when building a package, you can use bitbake -e (attention, lots of output) Jun 09 10:35:12 MarcWe: the quick start and development guide have guided examples. a full list is in the reference manual but that's long Jun 09 10:36:36 k Jun 09 10:36:39 tnx Jun 09 11:07:50 Hi, is there a way to order tasks in yocto? My Problem is that I use wic to create my partition layout. Therefore I use the ext4 image wich should be created before, however both images are built in parallel. This causes that wic always uses the old ext4 image. Jun 09 11:08:17 I use IMAGE_FSTYPES = "ext4 ext4.gz wic" in my-image.bb Jun 09 13:12:05 hello, Jun 09 13:12:52 I'm using buildhistory to collect the sha1s for the recipes that contain srcrev=autorev Jun 09 13:13:11 I can put the file in my distro.conf and everything works; Jun 09 13:13:57 however, I have another layer which defines another image; how can I use the buildhistory in this case ? I don't have a distro.conf in this layer Jun 09 13:14:28 so where should I put the revisions of the packages ? Is it possible to put them in the image file ? Is this the correct way to do it ? Jun 09 13:39:22 I could add it to layer.conf in each, layer, not sure it's the most suitable place Jun 09 13:59:49 Hi folks, I'm having a problem getting a recipe to be built within yocto: https://gist.github.com/kratsg/10cf7835a83d4f17ad93173c8655c8e9 Jun 09 14:01:15 with this recipe: https://github.com/kratsg/meta-l1calo/blob/master/recipes-core/root/root_6.04.12.bb. So then I decided to try a newer version of ROOT. Jun 09 14:02:47 however, if I do that, and try to use the built-in LLVM that it ships with, then I get problems about my host compiler appears to require libatomic? https://gist.github.com/kratsg/027c92d0b020a594c9669a04f1457ed0 Jun 09 15:11:20 hi everybody, someone have tried to import an core-image-minimal to AWS? Jun 09 15:11:29 i'm soving a lot of problems, but i'm stuck on a error saying that my kernel version is not compatible Jun 09 15:11:39 I set the XEN configs and options that AWS recommends, but nothing works Jun 09 15:11:58 maybe there is a layer that creates an image ready to be imported or something like that? Jun 09 17:24:36 is there any way to do machine-override for FOO[bar] construct? Jun 09 17:29:17 denix: nope, would have to use inline python or anonymous python Jun 09 17:30:16 kergoth: thanks Jun 09 17:36:12 kergoth: is there any way to unset/undefine existing FOO[bar] variables? Jun 09 17:38:25 sadly not with the 'unset' syntax, i think you'd have to resort to anonymous python if setting it to the empty string won't do Jun 09 17:38:39 would probably be worthwhile to let 'unset' handle flag syntax in bitbake Jun 09 17:38:44 i.e. unset FOO[bar] Jun 09 17:39:20 that would be nice... Jun 09 17:41:00 unfortunately, there's a class that checks for a flag to be set and bails out, there doesn't seem to be a good way to change that from a recipe or bbappend... Jun 09 17:41:26 hello, I'm working on a pretty base level task here. I'm trying to get bitbake to build a package from a tarball that I have installed elsewhere on my computer, and I've managed to get it to see that tarball by using the SRC_URI variable in the bitbake recipe. But when I look at the /tmp/work directory the source files are not extracted there. Jun 09 17:45:37 twall: devtool add filename.tarball Jun 09 17:46:05 twall: Or if the project lives in a git repo point devtool add to the URI Jun 09 17:47:14 the tarball is a git repo I've cloned to my machine elsewhere and tar'd up after a couple quick changes. Jun 09 17:48:05 twall: sounds like you want to fork the git repo, clone the fork, make your changes, commit them to git and point devtool add to it ;) Jun 09 17:48:36 twall: that will also allow you to PR your changes back if applicable Jun 09 17:48:50 good idea Jun 09 18:05:18 hbruce: will the presentation you gave during yocto summit that was highlighting the devtool workflow be uploaded to the yoctoproject page? Jun 09 18:05:26 hbruce: I believe it was you who presented that :) Jun 09 18:06:20 ulf`: yocto "summit"? Jun 09 18:06:42 denix: or whatever it was called Jun 09 18:06:56 do you mean yocto dev day? Jun 09 18:07:17 just checking I didnt' miss anything... Jun 09 18:07:35 denix: not a dev day Jun 09 18:07:40 denix: summit and that one was Intel internal Jun 09 18:08:12 At least I think it was :) Jun 09 18:08:13 ah, Intel internal... Jun 09 19:31:58 msg ulf` So, after making a devtool layer from the repo, I realized that the repo itself is read-only and I can't fork from it. Any other ideas? Jun 09 19:32:11 dammit, forgot a / Jun 09 19:33:02 twall: You can fork a read-only repo? Jun 09 19:34:06 ...wait yes i can. more coffee is required. Jun 09 19:35:13 :) **** BEGIN LOGGING AT Fri Jun 09 23:33:10 2017 **** ENDING LOGGING AT Sat Jun 10 03:00:01 2017