**** BEGIN LOGGING AT Wed Jan 20 02:59:57 2021 Jan 20 07:28:15 RP: yep, that is fine Jan 20 08:07:36 hi. I want to have parted command in my rootfs , by installing wich package I can have it ?? Jan 20 08:11:36 Moh3N: http://layers.openembedded.org/layerindex/branch/dunfell/recipes/?q=parted Jan 20 08:12:36 mckoan thanks a lot Jan 20 08:32:12 hi I'm stephen Jan 20 08:36:45 stephensmithson: welcome Jan 20 08:43:56 hi i am trying to build core-image-sato for ARM with pytorch enabled. Can someone help how i can add it?? Jan 20 08:45:22 yo dudX Jan 20 08:47:20 LetoThe2nd: El duderino! Jan 20 08:47:33 pankaj347: http://layers.openembedded.org/layerindex/branch/master/recipes/?q=pytorch suggests that there is no obvious recipe for it, so you 1) have to create a recipe for it, probably in your own layer 2) have to create an image that pulls it in. Jan 20 08:49:55 does someone have recipe for pytorch ?? Jan 20 09:49:00 pankaj347: Look here https://github.com/renesas-rz/meta-renesas-ai Jan 20 10:32:41 Facing an issue where DEPENDS does not populate the recipe-sysroot with the packet. How to debug? Jan 20 10:33:39 is the recipe in DEPENDS yours? Jan 20 10:40:20 qschulz yes Jan 20 10:41:14 qschulz sorry mis-understood. the recipe is not my own. it is openamp, where openamp depends on libmetal. but the sysroot does not get populated with libmetal. Jan 20 10:41:57 qschulz https://github.com/OpenAMP/meta-openamp/blob/master/recipes-openamp/open-amp/open-amp.inc#L19 Jan 20 10:44:42 build libmetal first, then go into its ${WORKDIR}/sysroot-destdir. Are the files you're expecting there? No? You know where at least one issues lies Jan 20 10:45:54 then build open-amp, go to its ${WORKDIR}/recipe-sysroot. Is it there? No? use `bitbake -e open-amp | grep -e "^DEPENDS="`, does it have libmetal in it? Jan 20 10:46:26 if yes, then it's probably an issue with open-amp not using the correct flags that Yocto passes to its build system (or should be passing but the recipe is not using them) Jan 20 10:49:21 its there; Jan 20 10:49:22 raspberrypi3-64 $ bitbake -e open-amp | grep ^DEPENDS Jan 20 10:49:23 DEPENDS="cmake-native pkgconfig-native virtual/aarch64-xr-linux-gcc virtual/aarch64-xr-linux-compilerlibs virtual/libc libmetal ninja-native" Jan 20 10:49:23 raspberrypi3-64 $ Jan 20 10:52:48 oh wow, I admire your patience. Building Yocto on an RPi3... Jan 20 10:53:22 and the two first checks I suggested earlier? Jan 20 10:56:02 libmetal present in sysroot-destdir Jan 20 10:56:57 libmetal not present in recipe-sysroot for openamp Jan 20 10:58:01 and not building on rpi. just showing the pwd, builds is in x86 i7. Jan 20 10:58:07 lxc: not a single file coming from the libmetal's ${WORKDIR/}sysroot-destdir? Jan 20 10:59:03 lxc, qschulz: Also check if there is a libmetal file in openamp's ${WORKDIR}/recipe-sysroot/sysroot-providers/ Jan 20 11:00:10 no libmetal in recipe-sysroot/sysroot-providers Jan 20 11:00:59 lxc: try bitbake -f -c refreshrecipesysroot openamp Jan 20 11:01:30 lxc: and check again Jan 20 11:03:02 no refresh task. do_populate_sysroot and do_populate_sysroot_setscene and do_prepare_recipe_sysroot Jan 20 11:03:51 lxc: sorry, should be the preparerecipesysroot task. Jan 20 11:07:28 now I think I see something Jan 20 11:07:29 WARNING: open-amp-rel-v2020.2+gitAUTOINC+29eb98c023-r0 do_prepare_recipe_sysroot: Manifest /usr/local/src/yocto-xr/build/infn-xr/raspberrypi3-64/tmp/sstate-control/manifest-x86_64_x86_64-nativesdk-libmetal.populate_sysroot not found in raspberrypi3_64 cortexa53 armv8a-crc armv8a aarch64 allarch x86_64_x86_64-nativesdk (variant '')? Jan 20 11:10:19 lxc: Any changes in openamp's ${WORKDIR}/recipe-sysroot/sysroot-providers/ Jan 20 11:12:11 no Jan 20 11:13:01 lxc: you're building a nativesdk aren't you? Jan 20 11:13:10 no Jan 20 11:13:53 why is yocto looking for *tmp/sstate-control/manifest-x86_64_x86_64-nativesdk-libmetal* manifest then? Jan 20 11:22:18 note sure. but I was able to get it working by adding PACKAGE_ARCHΒ  = "aarch64" Jan 20 11:23:31 https://github.com/OpenAMP/meta-openamp/blob/master/recipes-openamp/open-amp/open-amp.inc#L33 Jan 20 11:27:37 lxc: ahahahaha Jan 20 11:27:44 it's some Xilinx stuff ;) Jan 20 11:29:57 either set it back to TUNE_PKGARCH or use MACHINE_ARCH (or define your SOC_FAMILY_ARCH in your machine conf file) Jan 20 11:32:32 send a patch to meta-openamp too, they shouldn't be using this in non-BSP layers Jan 20 11:49:22 abelloni: the overnight master-next build was one of the worst for a while, all looks like intermittent load issues :( Jan 20 12:04:25 qschulz yep xilinx specific. they assign PACKAGE_ARCH = "${SOC_FAMILY_ARCH}". and looks like they assign SOC_FAMILY_ARCH ?= "${SOC_FAMILY}" in xilinx bsp. but what is the rationale to change PACKAGE_ARCH? Jan 20 12:29:24 I had installed .so and .h files into the build by extracting from a tar file, when compiling my application with installed package using DEPENDS I got an error as PKG_SEARCH_MODULE cannot find installed package in CMakeLists.txt. So, how do I add my installed recipe to package config? Jan 20 12:44:11 lxc: (you're gone but maybe you'll read the logs) the point of PACKAGE_ARCH is to have it apply to as many machines as possible so Yocto does not need to rebuild the recipe for different "architectures" even though the outcome of the build is identical between machines Jan 20 13:01:17 general question, can I edit/add .S files in yocto before the build or do I have to do that after the build has finished? Jan 20 13:04:05 stephensmithson: that sounds very much like an xy-question. Jan 20 13:04:24 stephensmithson: beside that, general patching mechanisms apply. Jan 20 13:05:27 yes sorry, can't formulate my question correctly :( Jan 20 13:05:47 thank you for your answer! Jan 20 13:06:10 stephensmithson: just tell us what you want to fix/do and for which reason and we can start from there :) Jan 20 13:12:06 currently I am looking at what yocto is capable of, I have worked with buildroot before, so nothing specific as of this moment, thanks qschulz :) Jan 20 13:13:53 stephensmithson: the only thing yocto can't do that buildroot can is: "providing a rootfilesystem/kernel/bootloader fast, using little space and moderate learning effort." Jan 20 13:16:25 LetoThe2nd it is indeed easier to use so better suited for beginnersX-P Jan 20 13:16:29 X-P Jan 20 13:18:24 stephensmithson: buildroot is easier for beginners, there's little doubt about it. but you might run into problems if your real use case is outside the beginner domain, you start out with buildroot and then meet more and more feature needs that you can't cover. so it might or might not be good to choose buildroot or yocto. it all depends. Jan 20 13:24:56 Hi Guys, hope you are doing well! Jan 20 13:24:56 I was using "runqemu" to run an image and I wanted to ssh from the host to the guest but can't find a way to do that especially that I see that "runqemu" doesn't seem to support all options in qemu. Jan 20 13:25:45 I am running "runqemue" with nographic and slirp Jan 20 13:26:49 I saw some patches which were trying to forward port from host to guest but wasn't implemented for performance concerns I believe Jan 20 13:27:24 Is there some way to manage to ssh from host to gust? Jan 20 13:27:37 guest* Jan 20 13:28:03 LetoThe2nd: how likely was this to happen a few days after I asked you the same question :D? Jan 20 13:28:11 qschulz: i was just about to poke you! Jan 20 13:28:26 JohnKa: runqemu qemuarm64 slirp nographic qemuparams="-nic user,hostfwd=tcp::5555-:22" Jan 20 13:28:42 JohnKa: ssh -o "UserKnownHostsFile=/dev/null" -o "StrictHostKeyChecking=no" -p 5555 root@localhost Jan 20 13:29:19 JohnKa: runqemu probably supports all qemu options, you just need to pass them to qemuparams? Jan 20 13:31:23 qschulz: I see, I thought I am kinda limited by runqemu, now I see. Jan 20 13:31:47 qschulz: awesome, thanks! gonna give it a try Jan 20 13:33:37 JohnKa: otherwise I saw ma few articles playing with iptables and all, but couldn't be bothered :) Jan 20 13:40:44 qschulz: yeah, same here. this one is good enough for what I need Jan 20 13:42:05 can someone share me good tutorial for yocto ? Jan 20 13:43:38 pankaj347: https://www.youtube.com/playlist?list=PLD4M5FoHz-TxMfBFrDKfIS_GLY25Qsfyj Jan 20 13:43:39 https://docs.yoctoproject.org/brief-yoctoprojectqs/index.html Jan 20 13:47:49 paulbarker:Tq so much Jan 20 14:10:37 How can easily I apply a kernel patch to multiple kernels? I have three kernels for different machine types, but they will share a common kernel patch Jan 20 14:11:20 lxc: if the recipes are in the same directory, just put the patch in a files/ subdir Jan 20 14:11:54 if they are in different directories, you can add the directory of the patch with FILESEXTRAPATHS Jan 20 14:12:06 (please go with the first option) Jan 20 14:15:49 RP: Yep. That works. I have an example webpage that shows the reproducibility stats from the most recent build.... who do we talk to about trying to get it published? Jan 20 14:16:09 JPEW: halstead Jan 20 14:20:27 halstead: I have a simple static webpage that displays the reproducibility results from the latest build (the idea being that https://reproducible-builds.org/citests/ can link there for some visibility). How do we get something published? Jan 20 14:24:20 JPEW: there are a few ways. Probably scp onto one of the webserver is the easiest. Would that work on your end? Jan 20 14:31:23 halstead: Fine with me if that's the preferred way.... I wasn't sure if it needed to be "themed" to match the rest of the website, or if my rather plain look was fine :) Jan 20 14:31:40 halstead: I'm not a web designed for good reason :) Jan 20 14:31:54 s/designed/designer/ Jan 20 14:32:05 qschulz not in same directory. E.g. meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_5.4.bb and poky/meta/recipes-kernel/linux/linux-yocto_5.4.bb. Jan 20 14:34:06 JPEW: would it be picked up and themed like https://tests.reproducible-builds.org/archlinux/ is for example? Jan 20 14:35:18 halstead: No, we would be doing an "external" link on reproducible builds.org, so we have complete control over how it looks. I modeled ours after: https://r13y.com/ Jan 20 14:35:55 lxc: you anyway need a bbappend for those Jan 20 14:36:16 qschulz thx Jan 20 14:36:25 put the bbappend in the same directory and put your patch in a files subdir and you're good to go Jan 20 14:38:05 JPEW: in that case maybe we can add a page to WordPress and you can update that. Then it would get themed automatically. Jan 20 14:40:37 halstead: OK, we can try that Jan 20 14:44:40 JPEW: I'm going to look into ways to update content there programmatically and email you. Jan 20 14:45:54 halstead: excellent. Thanks! Jan 20 15:15:21 Hello all, after updating to the last version of Yocto i get the following issue : defconfig was supplied both via KBUILD_DEFCONFIG and SRC_URI. So how to override a kernel conf provided by vendor meta ? Jan 20 15:34:38 hello guys, I know that's not strictly related to yocto but I'll ask it anyway.. I can't really find an answer to that Jan 20 15:36:06 what's the relation within uboot ram address where I load files and the LOADADDR and ENTRYADDR that one usually specify for the kernel in a fitimage ? Jan 20 15:37:46 (ask on #u-boot, that's their stuff ;) ) Jan 20 15:38:16 I've tried sometimes ago but nobody replied :D Jan 20 15:38:25 maybe thay don't know too Jan 20 15:42:05 LOADADDR is where your file will be loaded, ENTRYADDR is where u-boot should jump. Probably something along those lines Jan 20 15:42:22 in case of uImage, ENTRYADDR is offset by the size of the uImage header Jan 20 15:43:39 except if you ask u-boot to not do it, the files you want to boot will be loaded into RAM (possibly a second time if your files were in RAM already). Honestly, big wild guesses Jan 20 16:06:10 qschulz, thanks for clarify Jan 20 16:07:44 So I need to instruct uboot where to load the itb Jan 20 16:08:14 and uboot retrieve the info on where to load and run the kernel from the values written in the itb ? Jan 20 16:08:26 thekappe: yes Jan 20 16:08:32 my english is really terrible Jan 20 16:08:36 be careful with overwrites Jan 20 16:08:42 and also my programming Jan 20 16:08:50 qschulz, yeah that was the point Jan 20 16:08:58 I was overwrting all day long Jan 20 16:09:14 that's style Jan 20 16:09:15 thekappe: same for initramfs, it'll be loaded somewhere too Jan 20 16:09:24 (if you have one in your itb) Jan 20 16:09:50 strange thing is for ramdisk and dtb I haven't added those entries ( I was following a template) Jan 20 16:10:03 thekappe: don't worry about English, it's not the mothertongue of many if not the majority of us here :) Jan 20 16:10:40 thekappe: why are you not inheriting kernel-fitimage from Yocto? Jan 20 16:10:58 this should give you a sane default as a base to hack on if you need more specific things Jan 20 16:10:59 needed to add also an fpga entry Jan 20 16:11:33 I started from there as you pointed out Jan 20 16:13:22 the its file autogenerated from kernel-fitimage.bbclass doesn't add load_addr for dtb and ramdisks Jan 20 16:14:07 then it'll be loaded "somewhere" in RAM Jan 20 16:14:07 but maybe is just a matter of conifugration Jan 20 16:14:20 somewhere doesn't sound too good to me Jan 20 16:14:21 IIRC there are variables in u-boot to define where they should be loaded Jan 20 16:15:05 I'll try to add them Jan 20 16:15:09 sounds better Jan 20 16:15:19 thanks man Jan 20 16:16:02 initrd_high I think Jan 20 16:17:11 and fdt_high Jan 20 16:26:27 basically Jan 20 16:26:57 i can try to load ramdisk at 0x0, kernel at 0128M Jan 20 16:27:43 I can try to load ramdisk at 0, kernel at 0+128M, dtb at 0+128M*2, fpga at 0+128M*3 Jan 20 16:28:02 supposing that each file won't exceed 128M Jan 20 16:28:29 finally I'll load the itb file at 128M*4 Jan 20 16:34:20 thekappe: check that 0 is a valid RAM address first Jan 20 16:34:27 (well, all of them actually :) ) Jan 20 16:34:47 my tip is to load small files before the kernel in the RAM Jan 20 16:35:12 e.g. a DTB won't be bigger than 1MB for sure, so put it 1MB before the kernel addr Jan 20 16:35:31 you're limited because of the hw for the fpga binary too so you know the max size Jan 20 16:35:36 kernel can fluctuate a lot Jan 20 16:35:41 same for initramfs Jan 20 16:42:04 qschulz, thanks Jan 20 18:42:35 Can I add an image recipe as a dependence for another, so that I build both? Jan 20 18:43:34 You can, but I'd suggest creating a separate recipe that depends on both images, for better parallelization Jan 20 18:43:50 We have all.bb for that purpose, with a whole bunch of DEPENDS lines Jan 20 18:44:06 sounds good as well Jan 20 18:45:10 neverpanic: do you have an example somewhere? Jan 20 18:49:35 ho, I could use WKS_FILE_DEPENDS as well to specify the required image recipe. Jan 20 18:55:51 v0n: not public unfortunately, no. Jan 20 18:59:49 neverpanic: what kind of images your all.bb recipe depends on? Jan 20 19:07:33 we leave .pyc files in the bitbake dir of poky -- which (may?) break when a distro uprev's py3 and gives a cryptic error... Jan 20 19:07:40 "ImportError: bad magic number in 'concurrent': b'\x03\xf3\r\n' " Jan 20 19:08:17 Note - not the build dir, but poky/bitbake dir. Wondering if we should be detecting the version change and clean those up as part of the build system? Jan 20 21:06:51 paulg: istr a recent change in master to disable generating those to avoid pseudo issues Jan 20 21:08:54 smurray, ok - well I'll ignore it for the time being and go look for that later. Jan 20 21:09:30 FWIW, I'm assuming the move from ubu-20.04 to ubu-20.10 triggered it, but I can't be 100% sure. Jan 20 21:10:49 I'm surprised python doesn't just reparse the .py in that situation Jan 20 21:11:33 but I do have memories of seeing it a couple of times myself outside of OE Jan 20 21:13:59 yeah, I'm laying a good chunk of blame here at python's feet for not cleaning up things itself --- vs. the cryptic error message. Jan 21 00:22:08 Say I use SRC_URI to fetch custom kernel sources in a `.zip`, but they are not at the root (they are in `sources/linux/linux`). Is there a way to tell SRC_URI that I am interested in that subdirectory only? Jan 21 01:03:40 jonesv[m]: you'd set S to point to that subdirectory so that the build starts under there Jan 21 01:07:03 Oh, like simply S = sources/linux/linux? Jan 21 01:11:54 Found it, just before SANITY_REQUIRED_UTILITIES in the manual 😊. Not easy to search for "S" 😁 Jan 21 01:53:36 Finally got it to work, thanks bluelightning ! Jan 21 01:58:27 hmm now it complains that it does not find a `.config` (which is correct, I did not add it anywhere). I managed to get the running config `config.gz`. Is there some place I could put it in my kernel recipe? πŸ€” Jan 21 01:58:27 The idea here is that I want to use a downstream kernel from their sources (and then see if I can do it only from patches, but that's a later step) Jan 21 02:00:13 I guess that's this: https://docs.yoctoproject.org/kernel-dev/common.html#creating-a-defconfig-file. Slowly starting to find my way around the docs 😊 Jan 21 02:00:25 Anyway it's 3am, good night :) Jan 21 02:10:58 hmm still not working. Seems like it finds the defconfig, but it does not create a .config out of it **** ENDING LOGGING AT Thu Jan 21 02:59:57 2021