On Thu, 21 Jan 2016 20:01:37 +0100 Sven Hartge <s...@svenhartge.de> wrote: > On Tue, 28 Jul 2015 17:24:29 -0400 Douglas Calvert > <d...@douglasfcalvert.net> wrote: > > > Last night I rebuilt the latest ntpd in debian unstable from source with > > pps-tools installed. After restarting ntpd the rebuilt ntpd was able to use > > the pps signal from my sure gps. > > > > As it is I see no reason not to add pps-tools to the build-deps for ntpd. > > I want to add a "me too" to this bug. Please enable the use of PPS in > the package build.
I'm afraid i will have to add my +1 on this bug too. Please enable the use of PPS in the package build. > I just built a tiny GPS-disciplined NTP server using an Raspberry Pi2 > and a GPS addon card, as outlined here: > http://www.satsignal.eu/ntp/Raspberry-Pi-quickstart.html > > To be able to use the GPS_NMEA driver with PPS I had to manually rebuild > the package, something which should not be necessary. Exactly the same steps here. > Enabling the PPS source, even if the default Debian kernel lacks the > PPSAPI, does not hurt the normal user, but, as Kenyon Ralph said, > removes one step for users who build their only kernels or just use the > ntpd PPS discipline. Not that it matters to Debian, but for current Raspberry Pi 2 (kernel 4.1.19-v7+), there is even no need to recompile kernel, since PPS support is already present: CONFIG_PPS=m CONFIG_PPS_CLIENT_GPIO=m So NTP Build-Depends: pps-tools is the *only* missing bit right now... > Grüße, > Sven. Roman.
