diff options
Diffstat (limited to 'contrib/amd/README')
| -rw-r--r-- | contrib/amd/README | 18 |
1 files changed, 8 insertions, 10 deletions
diff --git a/contrib/amd/README b/contrib/amd/README index 33db6bc..2b91b9d 100644 --- a/contrib/amd/README +++ b/contrib/amd/README @@ -61,7 +61,7 @@ This is a manual method that will let you build in any directory outside the am-utils source tree. It requires that your "make" program understand VPATH. This can be used multiple times to build am-utils concurrently in multiple (but different) directories. In fact, the buildall script -described above. +described above does precisely that, using the A.* subdirectories. (4) If you need to configure am-utils with extra libraries and/or headers, for example to add hesiod support, do so as follows: @@ -74,7 +74,7 @@ for example to add hesiod support, do so as follows: hlfsd, lib, etc, all you need to do to get a new version of am-utils is run make. -If you modify any of the files in the aux/ or conf/ directories, or any *.in +If you modify any of the files in the m4/ or conf/ directories, or any *.in or *.am file, then you must rebuild the configure script, Makefile.in files, aclocal.m4, etc. The best way to do so is to run @@ -83,12 +83,10 @@ or ./buildall -K To be a developer and be able to run "bootstrap", you must have -autoconf-2.13, automake-1.4, and libtool 1.3.5 installed on your system (or +autoconf-2.50, automake-1.5, and libtool 1.4 installed on your system (or later versions thereof). You no longer need to get my special version of -automake. Note also the the bootstrap script and several other tools are -not available in the regular distribution of am-utils, only though the CVS -server for am-utils. Contact me if you'd like to be a maintainer and get -access to the CVS server. +automake. Contact me if you'd like to be a maintainer and get access to the +CVS server. After you've remade the basic configuration files you must rerun the buildall script to rerun configure and then remake the binaries. @@ -98,9 +96,9 @@ before. Let me know if you are having any problems with them. I fully expect, at least initially, to have to be the sole developers of the M4 macros and let others concentrate on C sources. -[E] Report all bugs to amd-dev@majordomo.cs.columbia.edu. Avoid reporting -to my personal email address. It is important to involve the whole list in -bug fixes etc. +[E] Report all bugs to amd-dev@cs.columbia.edu. Avoid reporting to my +personal email address. It is important to involve the whole list in bug +fixes etc. Good luck. |
