142629SobrienThis is the official version of am-utils. 238494Sobrien 338494SobrienSee the file NEWS for news on this and previous releases. 438494Sobrien 542629Sobrien*** General Notes to alpha/beta testers: 638494Sobrien 742629Sobrien[A] as alpha/beta testers, I expect you to be able to find certain things on 838494Sobrienyour own (especially look at the sources to figure out how things work). 938494Sobrien 1038494Sobrien[B] if you intend to modify any files, first find out if the file you want 1138494Sobriento modify gets autogenerated from some other place. If so, modify it at the 1238494Sobriensource. 1338494Sobrien 1438494SobrienYou can adjust some of the configuration of am-utils after it has been 1538494Sobrienauto-configured by putting whatever definitions you wish in a file called 1638494Sobrienlocalconfig.h, located in the top build directory (the same one where 1738494Sobrienconfig.h is created for you). 1838494Sobrien 1938494Sobrien[C] there are several ways you can build am-utils: 2038494Sobrien 2138494Sobrien(1) run the buildall script as follows: 2238494Sobrien 2338494Sobrien ./buildall 2438494Sobrien 2538494SobrienThis would build all the applications inside a special directory relative to 2638494Sobrienthe root of the source tree, called A.<cpu-company-system>, where the <> 2738494Sobrienpart is filled in by GNU's config.guess script. This is the preferred 2838494Sobrienmethod, for it will separate the build from the sources, and allow you to 2938494Sobrienrun buildall for multiple architectures concurrently. 3038494Sobrien 3138494SobrienYou can run "buildall -h" to see what options it takes. 3238494Sobrien 3338494Sobrien(2) run the configure script such as: 3438494Sobrien 3538494Sobrien ./configure 3638494Sobrien 3738494Sobrienand then run 3838494Sobrien 3938494Sobrien make 4038494Sobrien 4138494SobrienThis would configure amd in the directory you've run the configure script 4238494Sobrienin, and the built it there. Run "make install" to install all the necessary 4338494Sobrienfiles. 4438494Sobrien 4538494SobrienNote that this is good for building only one version of amd on one 4638494Sobrienarchitecture! Don't try this for multiple architectures. If you must, then 4738494Sobrienafter doing one such build, run "make distclean" and then reconfigure for 4838494Sobrienanother architecture. 4938494Sobrien 5038494Sobrien(3) run the configure script for build in a different location. Let's say 5138494Sobrienthat /src/am-utils-6.0 is where you unpacked the sources. So you could 5238494Sobrien 5338494Sobrien mkdir /src/build/sunos5 5438494Sobrien cd /src/build/sunos5 5538494Sobrien /src/am-utils-6.0/configure --srcdir=/src/am-utils-6.0 5638494Sobrien make 5738494Sobrien 5838494SobrienThis is a manual method that will let you build in any directory outside the 5938494Sobrienam-utils source tree. It requires that your "make" program understand 6038494SobrienVPATH. This can be used multiple times to build am-utils concurrently in 6138494Sobrienmultiple (but different) directories. In fact, the buildall script 62119679Smbrdescribed above does precisely that, using the A.* subdirectories. 6338494Sobrien 6438494Sobrien(4) If you need to configure am-utils with extra libraries and/or headers, 6538494Sobrienfor example to add hesiod support, do so as follows: 6638494Sobrien 6738494Sobrien configure --enable-libs="-lhesiod -lresolv" \ 6838494Sobrien --enable-ldflags="-L/usr/local/hesiod/lib" \ 6938494Sobrien --enable-cppflags="-I/usr/local/hesiod/include" 7038494Sobrien 7138494Sobrien[D] If you modify any of the *.[chyl] sources in the directories amd, amq, 7238494Sobrienhlfsd, lib, etc, all you need to do to get a new version of am-utils is run 7338494Sobrienmake. 7438494Sobrien 75119679SmbrIf you modify any of the files in the m4/ or conf/ directories, or any *.in 7682794Sobrienor *.am file, then you must rebuild the configure script, Makefile.in files, 7782794Sobrienaclocal.m4, etc. The best way to do so is to run 7838494Sobrien 7982794Sobrien ./bootstrap 8038494Sobrienor 8138494Sobrien ./buildall -K 8238494Sobrien 8382794SobrienTo be a developer and be able to run "bootstrap", you must have 84119679Smbrautoconf-2.50, automake-1.5, and libtool 1.4 installed on your system (or 8582794Sobrienlater versions thereof). You no longer need to get my special version of 86119679Smbrautomake. Contact me if you'd like to be a maintainer and get access to the 87119679SmbrCVS server. 8838494Sobrien 8938494SobrienAfter you've remade the basic configuration files you must rerun the 9038494Sobrienbuildall script to rerun configure and then remake the binaries. 9138494Sobrien 9238494SobrienModifying M4 macros may not be very intuitive to anyone that has not done so 9338494Sobrienbefore. Let me know if you are having any problems with them. I fully 9438494Sobrienexpect, at least initially, to have to be the sole developers of the M4 9538494Sobrienmacros and let others concentrate on C sources. 9638494Sobrien 97131702Smbr[E] Report all bugs to am-utils@am-utils.org. Avoid reporting to my 98119679Smbrpersonal email address. It is important to involve the whole list in bug 99119679Smbrfixes etc. 10038494Sobrien 10138494SobrienGood luck. 10238494Sobrien 10338494SobrienErez Zadok, 10438494SobrienMaintainer, am-utils. 105