New: ccache using wrong cached objects
https://bugs.busybox.net/show_bug.cgi?id=11261
Bug ID: 11261
Summary: ccache using wrong cached objects
Product: buildroot
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: critical
Priority: P5
Component: Other
Assignee: arnout at mind.be
Reporter: david.degrave at mind.be
CC: buildroot at uclibc.org
Target Milestone: ---
Signature · 2 lines
You are receiving this mail because: You are on the CC list for the bug.
[Buildroot] [Bug 11261] ccache using wrong cached objects
https://bugs.busybox.net/show_bug.cgi?id=11261
--- Comment #1 from Thomas Petazzoni <[email protected]> --- There is no description in this bug. Something went wrong when submitting the bug ?
Signature · 2 lines
You are receiving this mail because: You are on the CC list for the bug.
[Buildroot] [Bug 11261] ccache using wrong cached objects
In reply to bugzilla at busybox.nethttps://bugs.busybox.net/show_bug.cgi?id=11261
--- Comment #2 from David De Grave <[email protected]> --- (In reply to Thomas Petazzoni from comment #1)
Hi Thomas, no, I discovered a problem while building the linux kernel and finally found with the help of Arnout from where came the problem. It's something with ccache and the way buildroot deal with it.
So, he asked me to fill an empty bugzilla report for him to remember (I guess). He will fills all the details himself later... Sorry.
Signature · 2 lines
You are receiving this mail because: You are on the CC list for the bug.
[Buildroot] [Bug 11261] ccache using wrong cached objects
In reply to bugzilla at busybox.nethttps://bugs.busybox.net/show_bug.cgi?id=11261
Arnout Vandecappelle <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |WORKSFORME--- Comment #3 from Arnout Vandecappelle <[email protected]> --- Unfortunately, I was not able to reproduce the issue. We wiped the ccache and that solved the problem. I thought that I knew the cause (and thus would be able to reproduce), but apparently I didn't...
The issue was detected while David investigated the libfdt.h issue that was ultimately fixed by replacing -I$(HOST_DIR)/include with -isystem $(HOST_DIR)/include. Before that, he had developed a patch for the kernel that would fix it by changing the libfdt.h in the kernel to match the one in dtc itself. On one build machine, that patch worked perfectly fine; on another one, it apparently had no effect - until the ccache was removed.
In retrospect, it may be possible that this was caused by ccache installed on the host (so not our own ccache). But even with that added in the mix I couldn't reproduce.
I also thought at the time that I understood what was going wrong (I thought it was due to CCACHE_BASEDIR), but I've investigated that option further and it was a dead end.
So, with nothing more to go on, I'm closing this as WORKSFORME. Pity, because unreliable ccache is really painful.
Signature · 2 lines
You are receiving this mail because: You are on the CC list for the bug.