Re: ✘GPS WKRO workaround

[Gary E. Miller]

Yo Bernd!

On Sun, 8 Dec 2019 14:08:26 +0100
Bernd Zeimetz <address@hidden> wrote:

> On 12/7/19 7:51 PM, Gary E. Miller wrote:
>  How are you getting "current GPS leap second"?
> > 
> > The base layer is that gpsd is compiled in with a starting leap
> > second value.  Right now that comes from timebase.h, which is
> > created by leapsecond.py.  The value there is 19, but the correct
> > current value is 18.  leapsecond.py must die.  
> 
> If I remember right a found a fix for that issue without letting it
> die, so if removing the code is too much work right now, we could at
> least just fix it. I can did it out and commit if if you want.

leapsecond.py and teimbase.h are now gone.  The code, and SConstruct,
are much simpler now.

Eventually gpsd should do like ntpd and read leapsecond.cache at
runtime.

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
        address@hidden  Tel:+1 541 382 8588

            Veritas liberabit vos. -- Quid est veritas?
    "If you can't measure it, you can't improve it." - Lord Kelvin

pgpw5dsp_NyGe.pgp
Description: OpenPGP digital signature