On Thu, 2024-07-18 at 07:40 +0000, Oleksandr Hnatiuk via lists.openembedded.org wrote: > I am aware of this issue. As stated in my commit, it is designed to > improve reproducibility of gcc-cross-canadian as opposed to fully > fixing it. > > I have another patch I was going to submit which fully fixes this > package by modifying the code of gcc's fixincludes program to not > include full source directory, only source file name. However, > removing these files entirely as you suggest will also work. > > Of course, it would be best to fix this in code and submit the same > patch to gcc upstream to fix this issue for everyone. However, this > would take more time and require us to maintain another patch in > openembedded-core. Not sure which approach is preferred in OE.
We've now worked out why we didn't see this in our CI and have patches to fix that but that does mean we need the patches to fix this error more urgently! If you have something please do send it as I was thinking I might have to look at this today. Ideally we'd fix this with something acceptable to upstream, they'd take that and then we'd drop our changes next time we upgrade gcc. Maintaining a backported patch is fine, it is the ones that never get discussed with upstream we've been pushing back against. Re: deleting the files, the question is whether they're being used. If they are, we need to keep them. If they are never used, they could be deleted. I don't know which is the case here. Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#202192): https://lists.openembedded.org/g/openembedded-core/message/202192 Mute This Topic: https://lists.openembedded.org/mt/107268307/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
