Gary E. Miller gem at rellim.com
Thu Apr 20 21:05:10 UTC 2017

Yo All!

It seems NTP Classic added (non-standard) support for reproduceable
builds since commit 24e5bcb672a0006c9854e04036793569d7a71c7f in Dec

This worked until commit c2d30fff9f1697bbc041065dda2a72b37755afa1
in Jan 2017 which broke it.

As of my recent commit 8cf918e318049767f452b4693de1cb45d7c6543a
the support for reproduceable builds should be working again.  And
it is compliant with the specification found here:


Until now, the pivot date and the NMEA base date, where derived
at compile time from __DATE__ and __TIME__.  Now they are derived
from the EPOCH which is set at configure time.  So for most cases
it will be within a minute of compile time.  If you wait 10 years
between configureing and compiling you might find some issues with
your binary.

For reproduceable builds the EPOCH can be set to an arbitrary time
by either of: 'waf --epcoch=EPOCH'  or setting an environment
variable: 'export SOURCE_DATE_EPOCH=EPOCH'

The standard recommends settng EPOCH by default to the date of the
last source file modification.  I'm not sure if that is desirable, 
should be optional, or just ignored.

Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
	gem at rellim.com  Tel:+1 541 382 8588

	    Veritas liberabit vos. -- Quid est veritas?
    "If you can’t measure it, you can’t improve it." - Lord Kelvin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <https://lists.ntpsec.org/pipermail/devel/attachments/20170420/3d26cca5/attachment.bin>

More information about the devel mailing list