Note that the automatic build process inspects the machine environment and tests for the presence of system header files and the contents of these files to determine if certain features are available. When one or more of these features are present, the code is compiled to use them; if not, no special code is compiled. However, even if the code is compiled to use these features, the code does a special test at run time to see if one or more are actually present and avoids using them if not present. In such cases a warning message is sent to the system log, but the daemon should still work properly.
If your site supports multiple architectures and uses NFS to share files, you can use a single source tree to compile executables for all architectures. While running on a target architecture machine and with the distribution base directory active, create a subdirectory using a command like mkdir `config.guess`, which will create an architecture-specific directory with name peculiar to the architecture and operating system. Then change to this directory and configure with the ../configure command. The remaining steps are the same whether building in the base directory or in the subdirectory.
You are now ready to configure the daemon and start it. You will need to create a NTP configuration file ntp.conf and possibly a cryptographic key file ntp.keys. Directions for doing that are in the Notes on Configuring NTP and Setting up a NTP Subnet. A tutorial on debugging technique is in NTP Debugging Technique. If problems peculiar to the particular hardware and software environment are suspected, browse the Hints and Kinks page.
Bug reports of a general nature can be sent to David Mills <firstname.lastname@example.org>. Bug reports of a specific nature on features implemented by the programmer corps mentioned in the Copyright page should be sent directly to the implementor listed in that page, with copy to email@example.com.
Please include the version of the source distribution (e.g., ntp-4.0.70a) in your bug report.
Please include the output of config.guess in your bug report.
It will look something like: pdp11-dec-fuzzos3.4
Additional make commands
See the ./scripts/wininstall/readme.nt file for directions to compile the sources, build the libraries and link the executables. Initiate the build by running either bldrel.bat or blddbg.bat to compile all of the source and create an InstallShield based graphical installation package.
To install the executables, make sure that you are logged in as a system account, or one with administrator privileges such as the "administrator" account. As part of the build an InstallShield based graphical installer was created. Run \ntp\scripts\wininstall\intel\disk1\setup.exe to begin the installation. This installer will prompt for basic defaults, copy the binaries, install the service, and start it up. The other option is to run \ntp\scripts\wininstall\distrib\install.bat which will do the basic installation from the command line.