**** BEGIN LOGGING AT Thu Oct 05 03:00:01 2017 Oct 05 03:02:23 bluelightning, After I copy the defconfig next to recipe and add file://defconfig to SRC_URI, the next time I do source poky/oe-init-build-env, bitbake virtual/kernel will use that defconfig file after renaming it to .config? Oct 05 03:02:42 learningc: yes Oct 05 03:03:08 though if you're in the same shell session, no need to re-source the environment setup script Oct 05 03:05:33 bluelightning, But how will bitbake know the defconfig file has changed since it has already created the build directory? Oct 05 03:06:03 learningc: any changes to recipes or files they refer to (e.g. in SRC_URI) will be noticed by bitbake on the next execution Oct 05 03:06:21 I see Oct 05 03:08:18 bluelightning, But what will happen to the original defconfig file in the recipe directory? When I copy my .config file into a defconfig file in the recipe directory, won't it erase the original one? Oct 05 03:14:03 learningc: sorry I'm not following - the "original one"? Oct 05 03:16:05 bluelightning, I suppose there must be an "original" defconfig file to use to build the kernel when I clone poky? Oct 05 03:17:39 learningc: with linux-yocto, no - the configuration is assembled from fragments based upon enabled features - for more details see our kernel manual Oct 05 03:17:46 bluelightning, I mean, what file will bitbake use when I bitbake my kernel without creating any .config/defconfig file ? Oct 05 03:18:39 I see Oct 05 03:22:20 bluelightning, I'm not sure where is the recipe directory to put the defconfig copy. Is it in build directory created by source poky/oe-init-build-env or in the poky directory when I clone poky? Oct 05 03:22:59 learningc: the latter Oct 05 03:23:35 learningc: however note that as a matter of best practice you wouldn't modify the original recipe, you would create a bbappend with the changes in it in your own layer Oct 05 03:24:25 that makes it easier to handle upgrading in the future - i.e. you're not dealing with a forked repository Oct 05 03:25:04 bluelightning, I see. Many thanks to you. Oct 05 09:29:33 hello guys Oct 05 09:30:21 I need to place particular packages version to text file in the image. Is there elegant approach to do this? Oct 05 09:30:53 you mean something like a version manifest? Oct 05 09:34:15 LetoThe2nd: yep Oct 05 09:34:58 look at the buildinfo stuff, i think it can do something alike. maybe with some massaging Oct 05 09:36:27 LetoThe2nd: thank you Oct 05 09:36:34 good luck Oct 05 09:38:02 LetoThe2nd: did you mean this bbclass -> https://git.yoctoproject.org/cgit.cgi/poky/plain/meta/classes/image-buildinfo.bbclass ? Oct 05 09:38:34 Ox4: yes i think so Oct 05 09:38:41 maybe its not a perfect fit, but a start Oct 05 09:38:52 understood Oct 05 09:53:09 hi Oct 05 09:54:52 is it possible to include an inc file from an other layer? if the inc file does also include inc files, will path be ok? Oct 05 09:55:13 should be ok, just give it the full path. Oct 05 09:57:10 I tried but I got problem with SRCPV Oct 05 09:57:29 if I put my recipe in the layer with inc files, SRCPV is resolved Oct 05 09:58:16 if I put my recipe in another layer with full path includes, I got a "versions of u-boot available: my_version+git${SRCPV}" Oct 05 10:01:26 my bad there was an error in path ... thanks LetoThe2nd Oct 05 10:01:40 :-) Oct 05 10:18:35 When is manifest file generated? Oct 05 10:18:54 after which phase? Oct 05 10:36:12 Ox4: image preprocessing Oct 05 11:44:15 I am seeing this error, https://paste.ubuntu.com/25679130/ can anyone please me out , how should I fix it Oct 05 11:50:56 Ramose: did you do what the last line says? Oct 05 11:52:05 JaMa: This conf/site.conf doesn't exist Oct 05 11:52:13 This *file Oct 05 12:03:30 Hey all Oct 05 12:05:29 Interesting question : I've got an old project via yocto 1.6 thats been stable a long time, but needs dropbear updating for security. Now, normally id just copy in the suitable upstream recipe but theres already a dropbear.inc in the common poky dir... What's the "right" way to do this? Obv I can just bodge over the top in the poky dir but isn't there a better approach? Oct 05 12:05:48 *copy the upstream recipe into my own layer Oct 05 12:06:08 pev: you can put a copy of the .inc in the new layer? Oct 05 12:21:23 RP: Ah, grand! Will that then supercede the version under poky? Oct 05 12:37:05 pev: the recipe will look in the same folder before hunting around Oct 05 13:30:38 Hi, what does FILES_${PN} is it for ? And by adding -dev or -dbg or whatever ? Thanks. Oct 05 13:38:43 ChrysD: its for telling the package management what shall go into the package Oct 05 13:39:32 LetoThe2nd : But when you do the " do_install ", it tell where to go to the sysroot. So implicitly it will go into the package no? Oct 05 13:39:46 ChrysD: no. Oct 05 13:40:38 ChrysD: usually FILES will be a subset of what goes into the sysroot. think manpages. Oct 05 13:40:47 For example, in that example, you dont have a FILE_${PN} : http://variwiki.com/index.php?title=Yocto_Hello_World Oct 05 13:42:01 ChrysD: because some stuff is inherently in FILES_${PN} unless defined otherwise, like bindir, libdir, etc. Oct 05 13:42:10 but it should all be in the docs, after all. Oct 05 13:42:40 in a nutshell, you probably need FILES_ if you install something to a non canonical /usr application part Oct 05 13:42:44 s/part/path/ Oct 05 13:43:53 mmmh Oct 05 13:46:36 not sure of understanding but i will still dig. Oct 05 13:49:09 ChrysD: http://www.yoctoproject.org/docs/2.3.2/ref-manual/ref-manual.html#var-FILES Oct 05 13:49:26 I already read but thanks. Oct 05 13:52:42 LetoThe2nd : what confuse me is the fact that with do_install, i have my file into my device without the need of putting FILES. Oct 05 14:23:36 Any device-tree wizards around? Oct 05 14:26:21 I have my amba { slcr@f8000000 { clkc@100 { foo; }; }; }; coming from upstream, but I would like to extend it. Oct 05 14:26:50 I don't want to overwrite the file from upstream Oct 05 14:27:00 What is the correct syntax to do that? Oct 05 14:31:22 JoiF: Does clkc have a alias, e.g. "clkc: clkc..."? then use &clkc { ...}; otherwise use the path /amba/slcr... {...}; in your top level dts Oct 05 14:33:43 nrossi: As always, you're here to save me ;) Oct 05 14:34:08 But no, it doesn't have an alias Oct 05 14:34:33 I have to have the full reference, right? With the addresses and everything? Oct 05 14:36:03 JoiF: I think so, but dtc might have gotten smarter since i last had to use paths ;) Oct 05 14:39:57 What are all the way which kernel modules can be loaded automatically at boot ? I have a meta made by my own, which the image produced had the driver loaded at boot. Now i changed project but still the same meta and now it's not loaded automatically. Oct 05 14:40:41 Local.conf are the same. Oct 05 14:41:02 the image recipe is the same and distro is the same. Oct 05 14:41:23 With bitbake virtual/kernel -c menuconfig , the driver is in "" state Oct 05 14:42:56 ChrysD: most common is the KERNEL_MODULE_AUTOLOAD variable which results in the module package containing an entry in /etc/modules-load.d Oct 05 14:43:35 nrossi : I know this one, but i didn't needed to set this variable to have my module loaded in the first project. That's why i'm wondering. Oct 05 14:44:17 ChrysD: could be loaded by udev due to a device needing it, really depends on the module for that though Oct 05 14:44:29 nrossi : it's a camera driver Oct 05 14:44:39 nrossi : ov5640 Oct 05 14:44:51 nrossi : to be more precise ov5640_camera_mipi Oct 05 14:45:38 WHich strike me is that the first project, i made my own image recipe which require core-image-minimal and added few packages Oct 05 14:45:58 nrossi: So we are on the same page that this https://gist.github.com/johannfr/89eb3e6fc15bed7d9bddfa713cccff21 is adding those two lines to whatever is already in clkc@100 at a higher level? ..and not overwriting the entire block? Oct 05 14:46:36 I guess I'm about to find out .. it just finished compiling ;) Oct 05 14:47:57 I have a newbie question: I want to have libpcap in my image. I would usually use "CORE_IMAGE_EXTRA_INSTALL =+ "libpcap". Howewer I see that I can also do 'bitbake libpcap'. Does the latter also include libpcap in the image? Oct 05 14:48:34 no, the latter just builds the libpcap packages Oct 05 14:48:37 doesn't do anything with images Oct 05 14:48:45 bitbake libpcap will only do the package, but doesn't mean that i will be put into your image. Oct 05 14:49:33 : so it is like a test run ? Oct 05 14:49:46 no, it just builds the recipe Oct 05 14:50:16 OK so in my case I will use "CORE_IMAGE_EXTRA_INSTALL =+ "libpcap" since I want the package in the image.. thanks. Oct 05 14:50:41 cpf : It allow to build only the recipe instead of all the image for testing purpose. Like if you change a recipe and want to know if it work, it's faster to do bitbake 'recipe' instead of bitbake 'image' Oct 05 14:51:14 JoiF: valid syntax, but no idea why you are trying to feed the gem1_emio_mux clock back into the clkc? Oct 05 14:51:16 : yes I see. it makes sense. Oct 05 14:53:26 Hello, I'm trying to build with a custom BSP and a custom toolchain. The manual Oct 05 14:53:26 http://www.yoctoproject.org/docs/1.8/adt-manual/adt-manual.html#optionally-using-an-external-toolchain Oct 05 14:53:29 states that I shall add the layer that contains the toolchain to my bblayers.conf Oct 05 14:53:30 How do I build such a layer ? What should I put in that layer ? Oct 05 14:54:16 nrossi: The reason I'm doing that may have something to do with the fact that I have no idea what I'm doing. ;) Oct 05 14:55:08 nrossi : no more idea? Oct 05 14:55:41 nrossi: But it comes from here: https://forums.xilinx.com/t5/Embedded-Linux/Unable-to-get-25MHz-Frequency-with-gem0-device-connected-to/m-p/687379#M15654 Oct 05 14:55:57 With modifications from gem0 to gem1 Oct 05 14:57:22 nrossi: My /sys/kernel/debug/clk/clk_summary at least shows me 25000000 for "gem1_emio_mux" and its child-node "gem1" Oct 05 14:57:30 Both of which were previously zero Oct 05 14:57:39 I have a strange behavior : I have an image recipe which "require recipes-images/images/my-other-image". But my new image doesn't include the image_install of my "required image". :s Oct 05 14:58:06 ChrysD: hard to say tbh so many ways to load modules :| Oct 05 14:58:22 nrossi : ok still thanks Oct 05 15:02:46 JoiF: ignore me, i forgot you have to route the emio clock into the gem's :| which is done via through clkc Oct 05 15:05:47 mhhh when i do -c clean of an image recipe, and i do bitbake image_recipe, is like if it i've done nothing. Oct 05 15:05:53 even with -cleanall Oct 05 15:06:56 ChrysD: some things don't result in a change in the hashes, -c cleansstate to be sure your not using sstate cached content Oct 05 15:07:39 nrossi : i've done an image, and after it another image. and the another image had problem so that i wanted to do a clean rebuild Oct 05 15:07:50 nrossi : so i guess it was th eproblem Oct 05 15:09:32 nrossi : doesn't do nothing. It only do the 'do_rootfs' Oct 05 15:10:06 nrossi : the only way is removing tmp/download and sstate folders... Oct 05 15:11:01 ChrysD: that will be a completely fresh build, and will rebuild everything... Oct 05 15:11:14 nrossi : it's what i want Oct 05 15:12:04 nrossi : i've done a first image " bitbake image1" and from that i've done second image " bitbake image 2". But when i've done the second image, it was directlty to the case of "do_rootfs". SO i wanted to do fresh build with only building "image2" Oct 05 15:14:45 ChrysD: sure, if thats what you want :) then you only need to delete tmp and sstate dirs, download is just whats downloaded from the internet Oct 05 15:15:04 nrossi : SO what does cleanall do? Oct 05 15:15:53 nrossi : fo ra recipe image i mean Oct 05 15:16:31 ChrysD: http://git.openembedded.org/openembedded-core/tree/meta/conf/documentation.conf#n13 Oct 05 15:18:13 nrossi : It's what i've already read. But if i do a -cleanall of an image recipe, it won't clean the recipe which depends the image recipe? Oct 05 15:18:54 ChrysD: -c clean* only clean the specific target recipe you specify and nothing else Oct 05 15:19:21 nrossi : oh Oct 05 15:19:36 nrossi : i thought -c cleanall will do a kind of "cleaning" Oct 05 15:19:39 Thanks Oct 05 15:19:42 hi o/ Oct 05 15:20:21 I got a ctc that is generated for a lot of HOST_TARGET: arm-overkiz-linux-musl, arm-overkiz-linux-gnueabi, arm-overkiz-linux-musleabi, Oct 05 15:20:30 how can we explain that? Oct 05 15:20:35 I need only one, the right one:p Oct 05 15:21:06 I like that documentation.conf instead of the manual, thanks for the discovery ahah Oct 05 15:35:50 hello, I am exposing a FAT32 partition on my SD card to Windows using g_mass_storage USB gadget driver... and yet it showing up as unallocated... the driver works fine when exposing the partition via USB on Ubuntu 16.04 Oct 05 15:35:56 I have a question.. I have a local poky repository along with the meta-openembedded layer Oct 05 15:36:45 the partition I am exposing was created via wic Oct 05 15:36:47 I have also create a build repository with the downloads directory Oct 05 15:37:39 How can I be sure that I have all the files that are needed to build the image w/o an internet connection ? Oct 05 15:38:53 fberg: bitbake image -cfetchall Oct 05 15:39:24 thank you rburton Oct 05 15:39:56 once executed, all the fetched sources will be in the build/download folder ? Oct 05 15:40:23 I am using: modprobe g_mass_storage file=/dev/mmcblk1p4 stall=no Oct 05 15:40:40 am I missing an argument to make this work properly with Windows? Oct 05 16:08:22 If i do "require image....." into my new image recipe, what is inside the iMAGE_INSTALL of the required one should be into the new image right? Oct 05 19:28:15 I have a problem where GCC optimizations are itnerfering with a patch to some code. Is there a way to disable optimizations for a specific recipe? Oct 05 19:28:40 I tried to do EXTRA_OEMAKE = " CPPFLAGS=-O0" but then my build fails, looks like its wiping out cppflags that were needed Oct 05 19:32:37 what is the best linux distro for a dev machine for using yocto and cros development for embedded linux? Oct 05 19:32:50 or how can I get yocto to spit out the log of a successful compilation so I could pull out the whole CFLAGS and hard code them? Oct 05 19:38:05 bodangly: CFLAGS and CPPFLAGS are bitbake variables, just modify them appropriately as you would any other bitbake variable, no need to muck with how they get passed in yourself Oct 05 19:38:19 that said, there are separate variables that hold the optimization flags, see meta/conf/bitbake.conf Oct 05 19:38:55 kergoth: can I adjust optimizations for just one recipe? Oct 05 19:39:08 i don't understandt eh question Oct 05 19:39:16 they're bitbake variables, set them in the recipe as you would anything else Oct 05 19:39:19 read the bitbake manual Oct 05 19:52:14 got it thank you Oct 05 19:52:26 CFLAGS += " -O0" worked Oct 05 20:11:06 zarzar: there are several distros supported by YP, Oct 05 20:11:55 zarzar: somewhere in the docs the exact distro-version map is defined Oct 05 20:42:02 Is there a way to limit CPU in Yocto? The CPU and GPU are getting pretty damn hot. Oct 05 20:42:13 Im wanting to reign it in, and see if that helps. Oct 05 20:59:53 tcpdump: you can set BB_NUMBER_THREADS and PARALLEL_MAKE to reduce the parallelism, see what's in your local.conf Oct 05 21:00:20 by default these days it automatically scales those based on the number of cores in your system Oct 05 21:01:01 if your GPU is getting hot that is something else (or just as a result of the CPU getting hot) - the build system doesn't use the GPU ;) **** ENDING LOGGING AT Fri Oct 06 03:00:01 2017