| 29 Nov 2024 |
 atemu12 | I fixed that in the kernel once | 16:55:19 |
 p14 | I am unclear how it is used in gcc, is there information about that somewhere? At least for some standard builds of some software, removing it improves reproducibility by removing the outpath from affecting the build. | 16:56:57 |
 raboof | https://reproducible-builds.org/docs/randomness/ mentions "Link-Time Optimizations" may have to do with it. if we figure out what exactly is going on it'd be good to add that to that page. | 17:00:04 |
| p14 | Yeah, I think it is used in LTO somehow; is LTO used in nixpkgs? If not it could be a noop. And even if it was, it would be good to use a different value for it which does not depend on outpath. | 17:01:22 |
| raboof | if it'd be a noop then setting it to the output shouldn't hurt, though | 17:01:48 |
| raboof | * if it'd be a noop then setting it to the output path shouldn't hurt, though | 17:02:01 |
| raboof | but I agree it doesn't seem like a great choice | 17:02:26 |
 Rick (Mindavi) | It is at least used to generate the build-id, when separateDebugInfo is set you see that it differs | 17:09:36 |
| Rick (Mindavi) | When the input path is different and the output is expected to be the same, e.g. when setting an unused environment variable | 17:10:36 |
