3 ms·
Small details like differences in timestamps or build directories result in different binaries. Why is this even a problem? Did people actually think it was a
by andrewflnr 10y ago
Small details like differences in timestamps or build directories result in different binaries.
Why is this even a problem? Did people actually think it was a good idea to have a compiler's binary output depend on incidental crap like this, or did it sneak in somehow?
- madez 10y agoI am also surprised a compiler includes this information into a binary. My expection is that the compiler creates an optimized machine code functionally equivalent to the source code, and nothing else.
- breadbox 10y agoI think a lot of times it just sneaks in. For example, when one of my projects was in alpha state, I added the build timestamp to the `--version` output, so that I could reserve version number changes for actual releases. At that point in time I never thought it would become a debian package, much less that reproducible builds would be a thing someday.
- lelandbatey 10y agoThere are many ways to intentionally compile this kind of information into your binary. It's frequently done to include things like "this binary was compiled on 'x date'", usually for debugging use.