Open Bug 1498535 Opened 6 years ago Updated 2 years ago

Patching clang has no effect on sccache'd builds

Categories

(Firefox Build System :: General, enhancement)

Product:
Firefox Build System
Component:
General
Type:
enhancement

Tracking

(Not tracked)

People

(Reporter: glandium, Unassigned)

References

Details

Because clang now uses shared libraries, per bug 1492037, and because sccache uses the digest of the compiler executable as part of its cache key, when patching llvm in such a way that the clang executable doesn't change (which, because of shared libraries, is almost all kinds of patches), we end up reusing the cache from the previous build without the patch applied. This is not a problem when upgrading to new versions, but when applying patches, it is. One way we can work around this is by forcing the clang build not to be reproducible by using something like -Wl,--build-id=uuid. It feels like, however, we should find a generic solution at the sccache level.
Summary: Patch clang has no effect on sccache'd builds → Patching clang has no effect on sccache'd builds
Alex filed a similar issue a while ago about this happening when the compiler in use is a shell script that invokes another compiler: https://github.com/mozilla/sccache/issues/235 .
See Also: → https://github.com/mozilla/sccache/issues/235
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.