**** BEGIN LOGGING AT Wed Aug 17 02:59:56 2022
Aug 17 15:17:35 <cb5r> I accidentally corrupted some files in `tmp/work/imx6guf-guf-linux-gnueabi/linux-guf/5.10.104-r0/recipe-sysroot-native/usr/bin/arm-guf-linux-gnueabi/../../lib/arm-guf-linux-gnueabi/gcc/arm-guf-linux-gnueabi/9.3.0/plugin/include` and just cannot find out how to repair this. Where is the actual source of these files? If I clean(sstate) all gcc-* and linux recipes the corrupt headers just appear again on next build
Aug 17 16:20:41 <khem> cb5r: Just delete tmpdir
Aug 17 16:20:42 <khem> it will use sstate and get you there in no time
Aug 17 16:20:42 <khem> and do a rebuild
Aug 17 16:20:43 <khem> provided you did not change metadata
Aug 17 16:20:55 <cb5r> khem: Dont think I did 😅 What exactly counts as metadata?
Aug 17 16:21:33 <khem> meta-* and poky and local.conf etc under conf/
Aug 17 16:23:43 <cb5r> khem: oh no - I am actually currently cleaning up my local.conf a bit 🙄
Aug 17 16:24:25 <khem> that might or might not rebuild stuff depending upon what changes are made
Aug 17 16:27:26 <cb5r> phew - it uses the sstate cache 🙂
Aug 17 16:29:12 <cb5r> <khem> "cb5r: You need to install gcc-..." <- BTW: I installed `gcc-10-plugin-dev` on the docker host that runs the build but I am still getting the same error: `build/tmp/work/imx6guf-guf-linux-gnueabi/linux-guf/5.10.104-r0/recipe-sysroot-native/usr/bin/arm-guf-linux-gnueabi/../../lib/arm-guf-linux-gnueabi/gcc/arm-guf-linux-gnueabi/9.3.0/plugin/include/coretypes.h:430:10: fatal error: poly-int.h: No such file or directory`
Aug 17 16:31:21 <cb5r> * installed `gcc-9-plugin-dev` and `gcc-10-plugin-dev`, * 10-plugin-dev` (not sure which one it should be) on the
Aug 17 16:32:37 <cb5r> * installed `gcc-9-plugin-dev` and `gcc-10-plugin-dev`, * 10-plugin-dev` (not sure which one it should be) on the, * docker host (Debian 11) that runs
Aug 17 16:34:43 <khem> oh I mean install in staging sysroot ( cross build ) not on your host
Aug 17 16:35:10 <cb5r> oooh OK - I was wondering how this was supposed to work 😄 hehe
Aug 17 16:35:12 <khem> so in failing recipe add it to DEPENDS += "gcc-plugins"
Aug 17 16:35:54 <khem> or if it is something you are building an image first and then debugging on target then add it to rdeps
Aug 17 16:36:00 <khem> so it can be part of your image too
Aug 17 16:37:26 <cb5r> `ERROR: Nothing PROVIDES 'gcc-plugins' (but /home/yocto/workspace/sources/meta-seconorth-machine/recipes-kernel/linux/linux-guf_5.10.bb DEPENDS on or otherwise requires it). Close matches:
Aug 17 16:37:26 <cb5r>   gcc RPROVIDES gcc-plugins`
Aug 17 16:37:26 <cb5r> why isnt the gcc one used? 🤔
Aug 17 18:21:44 <khem> oh yeah just DEPEND on gcc is fine
Aug 17 18:22:18 <khem> since its build time if it was runtime you will add RDEPENDS += "gcc-plugins" to specifically include just plugins in image
Aug 17 18:23:53 <cb5r> I guess build time should suffice, no? I only need it to be able to add some flags for iptables to the kernel
Aug 17 18:39:02 <cb5r> Mmh, weird. Building only the kernel with `DEPENDS += "gcc"` works fine but when I then build the image I get the same error about missing headers again 🤔
**** ENDING LOGGING AT Thu Aug 18 02:59:57 2022