1
To get the NTP distribution via anonymous CVS:
3
% cvs -d :pserver:anoncvs@www.ntp.org:/cvs/ntp login
5
the password is: anoncvs
8
% cvs -d :pserver:anoncvs@www.ntp.org:/cvs/ntp co ntp
10
after which the "ntp_update" script in the top-level of the tree should
11
keep things in synch and properly timestamped.
15
When obtaining the NTP distribution directly via CVS instead of
16
using "ntp_update", the files are installed in an arbitrary
19
When you run "make", this may cause some of the generated files
22
If you do not have the right verison of automake and autoconf,
23
these files will be regenerated incorrectly.
25
In this case, you can "fix" your distribution by running:
29
which will force any local changes to your NTP files to be
30
discarded and replaced with the versions in the repository.
32
If "ntp_update -C" does not work just remove the "broken"
33
files (probably Makefile.in files) and re-run ntp_udate.
35
There are some mailing lists for the NTP CVS distribution. For more
36
information, send a message to <majordomo@ntp.org> with the word "lists"
37
in the body of the message.
39
If you get NTP via CVS, you MAY need to build the release using GNU make
42
You can then "make dist" to build a release tarball that does not require
45
The reason GNU make and gcc may be required is because the repository
46
version of NTP does not have the make dependencies built-in. These
47
dependencies are created dynamically, and this dynamic process may
48
require GNU make and gcc.
50
I'm told that the version of automake we are now using does not require
51
GNU make or gcc for the dependency tracking, but I haven't tested this
added
removed
README.cvs
