<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div dir="auto" style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div dir="auto" style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div dir="auto" style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><br><div><blockquote type="cite"><div>On May 20, 2024, at 1:52 PM, Noel Grandin <noelgrandin@gmail.com> wrote:</div><br class="Apple-interchange-newline"><div><div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><span class="gmail_default" style="font-family:tahoma,sans-serif">So I saw the same thing on my ARM macbook, and I chased it for a while, resetting/clearing ccache, rebooting, etc, but it just kept coming back, so I gave up and updated to a newer version of ccache for my mac, which seems to have fixed it (and as a bonus, is much newer and supports nice compression, saving me disk space, etc)</span><div><span class="gmail_default" style="font-family:tahoma,sans-serif"><br></span></div><div><span class="gmail_default" style="font-family:tahoma,sans-serif">Patch to update LODE here:</span></div><div><span class="gmail_default" style="font-family:tahoma,sans-serif"> </span><span style="font-variant-ligatures: no-common-ligatures; font-family: Menlo; font-size: 13px;"><a href="https://gerrit.libreoffice.org/c/lode/+/167874">https://gerrit.libreoffice.org/c/lode/+/167874</a></span></div><div><span style="font-variant-ligatures: no-common-ligatures; font-family: Menlo; font-size: 13px;"><br></span></div><div><span style="font-variant-ligatures: no-common-ligatures; font-family: Menlo; font-size: 13px;">y<span class="gmail_default" style="font-family:tahoma,sans-serif">ou will need to re-run LODE setup after applying that patch.</span></span></div><div><br></div></div></div></blockquote><br></div><div>Thanks Noel! Your LODE patch stopped the warnings in two clean builds (but no ccache clearing) for me.</div><div><br></div><div>Earlier today, like you I had found that if you interrupt the build after some point and run <font color="#000000"><span style="caret-color: rgb(0, 0, 0);">ccache -C, the warnings stop</span></font>. But the problem would reappear after a make distclean or the next time some unknown code is recompiled (maybe in connectivity?).</div><div><br></div><div>Patrick</div><div><br></div></div></div></div></body></html>