Harlan Stenn <st...@ntp.org> wrote: > Rob writes: >> Harlan Stenn <st...@ntp.org> wrote: >> > Martin Burnicki writes: >> >> IMO the best approach would be to detect this at runtime. >> > >> > That means we'd need a header file... >> > >> > If I'm not mistaken (and it's getting late for me), if the header file >> > is missing we don't expect the API. If the header file is present we >> > expect it to "do the right thing" and even then we check error returns >> > from the API. >> >> But the problem is the file is normally not there, even when the API is. > > No, the problem is that it's not normally there on *linux* boxes where > the file is maintained in a separate package. > > It *is* provided by the other OSes that implement this API.
Thos OSes probably have no package management and/or always install everything even when the user has not asked for it. Again, the solution is simple: building a correct ntpd depends on the availability of the pps-tools package on the build system. It should be added to the build dependencies to solve the problem. Current build dependencies on Debian are: debhelper (>= 4.2.12), libreadline-dev, lynx, libcap-dev, libedit-dev, libperl-dev, libssl-dev (>= 0.9), libsnmp-dev, quilt (>= 0.40), libevent-dev Add pps-tools to that list and the problem is over, finito. The only problem we face is that people don't want to type 'A, pps-toolsESCZZ' and finish a long-running discussion. _______________________________________________ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
