-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Binary checksum different after each rebuild. #597
Comments
Further research has resulted in the possible use of the argument -frandom-seed=string. I'll give this a go - all going well I will close. http://stackoverflow.com/questions/4140329/binary-object-file-changing-in-each-build |
I was hoping the following would work but seems to have no bearing on the output. It is included though as an argument.
|
closing due to staleness, reproducable builds would be cool but I think there's a ton of work to do in the entire node toolchain, V8 possibly being the most difficult. |
@rvagg This also just came up today on a discussion around integration with Bazel (https://bazel.build/) which works with sha256 sums of binaries and actions for caching and incrementality. Running |
Seems nodejs/build#589 and mapbox/node-pre-gyp#136 is related. Also some mention of build reproducability here: nodejs/node#21897 |
@Globegitter, do you have any leads as to where does the entropy come from? AFAICT |
I've been trying to track down what would cause a rebuild to generate a binary with a different checksum. No files have changed and yet each time a rebuild is done it's different.
I suspect a compile time timestamp or similar in being included within the result.
Is anyone aware of an argument I can specify to prevent this behaviour?
The text was updated successfully, but these errors were encountered: