Chris Quenelle wrote: > >>>> the use of __TIME__ and __DATE__ means that a build >>>> produces different binaries every single time; this forces engineers to >>>> manually evaluate whether or not a source change (a header file, for >>>> example) affects a given binary. This induces errors, or forces us to >>>> always ship any binary which has such constructs in the source code, >>>> inflating everyone's costs to no good purpose. > I agree the compiler should have a way to override these macros. > > Wouldn't it also be possible to modify the software in question so that > it doesn't > use __TIME__ and __DATE__? > > --chris >
From my original question: > > Any ideas? I really don't want to run sed scripts over tarballs > on every build to get rid of this problem. These are open source packages, developed elsewhere. Yes, we can patch all the software every time we build. I'd rather pass a flag or two to cc. - Bart -- Bart Smaalders Solaris Kernel Performance barts at cyber.eng.sun.com http://blogs.sun.com/barts "You will contribute more with mercurial than with thunderbird."
