Fw: ntpsec | build failed today on server - but without issues in the past (#320)

[Trevor N.]

The CI builds worked, and I usually start with a ./waf distclean so I
didn't notice that moving the function into libntp breaks builds that
have not been cleaned.
While attempting to fix classic bug 2659 I noticed another problem
with my commit d74cf1e3: Since the UTC offset is now required to
obtain the timecode, the factory default configuration of the
Palisade, Acutime 2000 and Acutime Gold will no longer work with fudge
flag2 active. That flag is normally used for troubleshooting with
those receivers, so I did not test it. It's possible to configure them
so they will work, but the configuration can't be done without user
intervention.

>Yo All!
>
>Looks like MR 422 broke some builds.  Trevor, can you look at this?
>
>RGDS
>GARY
>---------------------------------------------------------------------------
>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
>
>
>Begin forwarded message:
>
>Date: Sat, 27 May 2017 07:44:39 +0000
>From: "di. hans mayer" <gitlab at mg.gitlab.com>
>To: gem at rellim.com
>Subject: Re: ntpsec | build failed today on server - but without issues
>in the past (#320)
>
>
>Hint: It compiles fine with the standard configuration
>
>    ./waf configure 
>
>there must be something wrong with the refclock config 
>
>    ./waf configure --refclock=gpsd,generic,shm,pps,nmea,local
>
>
>
>// Hans
>