Cargo unit fingerprint influence on generated binaries

Hello,

I am trying to do a reproducible build on rust compiler, for that rust sources are built in 2 build directories (buildA & buildB) with command x.py build --build-dir buildA

But, the generated binary librustc_driver-xxxxx.so in build directories (../x86_64-unknown-linux-gnu/stage1/lib) are different.

When I analyzed the differences I could see the fingerprint is changed between both builds (The sources are identical just a rebuild on another build directory on buildB).

Does the change in fingerprint influences the generated binaries? if yes, how

Some addition details can be found here... rustc-driver binary is not identical for every build · Issue #102299 · rust-lang/rust · GitHub

For reference this was also posted by OP at Cargo unit fingerprint influence on generated binaries - compiler - Rust Internals. I answered there before I saw this post.

1 Like