| README (82794) | README (119679) |
|---|---|
| 1# -*- text -*- 2 3This is the official version of am-utils. 4 5See the file NEWS for news on this and previous releases. 6 7*** General Notes to alpha/beta testers: 8 --- 47 unchanged lines hidden (view full) --- 56 cd /src/build/sunos5 57 /src/am-utils-6.0/configure --srcdir=/src/am-utils-6.0 58 make 59 60This is a manual method that will let you build in any directory outside the 61am-utils source tree. It requires that your "make" program understand 62VPATH. This can be used multiple times to build am-utils concurrently in 63multiple (but different) directories. In fact, the buildall script | 1# -*- text -*- 2 3This is the official version of am-utils. 4 5See the file NEWS for news on this and previous releases. 6 7*** General Notes to alpha/beta testers: 8 --- 47 unchanged lines hidden (view full) --- 56 cd /src/build/sunos5 57 /src/am-utils-6.0/configure --srcdir=/src/am-utils-6.0 58 make 59 60This is a manual method that will let you build in any directory outside the 61am-utils source tree. It requires that your "make" program understand 62VPATH. This can be used multiple times to build am-utils concurrently in 63multiple (but different) directories. In fact, the buildall script |
| 64described above. | 64described above does precisely that, using the A.* subdirectories. |
| 65 66(4) If you need to configure am-utils with extra libraries and/or headers, 67for example to add hesiod support, do so as follows: 68 69 configure --enable-libs="-lhesiod -lresolv" \ 70 --enable-ldflags="-L/usr/local/hesiod/lib" \ 71 --enable-cppflags="-I/usr/local/hesiod/include" 72 73[D] If you modify any of the *.[chyl] sources in the directories amd, amq, 74hlfsd, lib, etc, all you need to do to get a new version of am-utils is run 75make. 76 | 65 66(4) If you need to configure am-utils with extra libraries and/or headers, 67for example to add hesiod support, do so as follows: 68 69 configure --enable-libs="-lhesiod -lresolv" \ 70 --enable-ldflags="-L/usr/local/hesiod/lib" \ 71 --enable-cppflags="-I/usr/local/hesiod/include" 72 73[D] If you modify any of the *.[chyl] sources in the directories amd, amq, 74hlfsd, lib, etc, all you need to do to get a new version of am-utils is run 75make. 76 |
| 77If you modify any of the files in the aux/ or conf/ directories, or any *.in | 77If you modify any of the files in the m4/ or conf/ directories, or any *.in |
| 78or *.am file, then you must rebuild the configure script, Makefile.in files, 79aclocal.m4, etc. The best way to do so is to run 80 81 ./bootstrap 82or 83 ./buildall -K 84 85To be a developer and be able to run "bootstrap", you must have | 78or *.am file, then you must rebuild the configure script, Makefile.in files, 79aclocal.m4, etc. The best way to do so is to run 80 81 ./bootstrap 82or 83 ./buildall -K 84 85To be a developer and be able to run "bootstrap", you must have |
| 86autoconf-2.13, automake-1.4, and libtool 1.3.5 installed on your system (or | 86autoconf-2.50, automake-1.5, and libtool 1.4 installed on your system (or |
| 87later versions thereof). You no longer need to get my special version of | 87later versions thereof). You no longer need to get my special version of |
| 88automake. Note also the the bootstrap script and several other tools are 89not available in the regular distribution of am-utils, only though the CVS 90server for am-utils. Contact me if you'd like to be a maintainer and get 91access to the CVS server. | 88automake. Contact me if you'd like to be a maintainer and get access to the 89CVS server. |
| 92 93After you've remade the basic configuration files you must rerun the 94buildall script to rerun configure and then remake the binaries. 95 96Modifying M4 macros may not be very intuitive to anyone that has not done so 97before. Let me know if you are having any problems with them. I fully 98expect, at least initially, to have to be the sole developers of the M4 99macros and let others concentrate on C sources. 100 | 90 91After you've remade the basic configuration files you must rerun the 92buildall script to rerun configure and then remake the binaries. 93 94Modifying M4 macros may not be very intuitive to anyone that has not done so 95before. Let me know if you are having any problems with them. I fully 96expect, at least initially, to have to be the sole developers of the M4 97macros and let others concentrate on C sources. 98 |
| 101[E] Report all bugs to amd-dev@majordomo.cs.columbia.edu. Avoid reporting 102to my personal email address. It is important to involve the whole list in 103bug fixes etc. | 99[E] Report all bugs to amd-dev@cs.columbia.edu. Avoid reporting to my 100personal email address. It is important to involve the whole list in bug 101fixes etc. |
| 104 105Good luck. 106 107Erez Zadok, 108Maintainer, am-utils. | 102 103Good luck. 104 105Erez Zadok, 106Maintainer, am-utils. |