-
Notifications
You must be signed in to change notification settings - Fork 711
[new-build] Use canonical path to compiler in config hash #5159
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
which normalisation recipe do you recommend? |
I don't have one in mind :) But it should have the property that if P and Q point to the same file they should result in the same hash? Perhaps better yet, don't include the hash of the path but instead the hash of the binary? (May be too expensive I suppose.) |
@edsko the problem with the hash of the binary is that you'd be hashing the wrapper shell script One could as a heuristic also use the inode number of the file object |
Perfect, ought to be much cheaper to compute then 😁 |
Btw, there is a dual ticket to this one (to un-differentiate |
Changing the path to ghc from
/opt/ghc/8.0.2/bin/ghc
to/opt/ghc/8.0.2//bin/ghc
causescabal
to consider the compiler to have changed, leading to a lot of unnecessary recompilation.The text was updated successfully, but these errors were encountered: