"Steven Shaw" <[EMAIL PROTECTED]> wrote: > On 06/12/06, Jim Meyering <[EMAIL PROTECTED]> wrote: >> "Steven Shaw" <[EMAIL PROTECTED]> wrote: >> > I guess AM_PATH_CPPUNIT isn't compatible with automake 1.9.2 which is >> > the default on RHEL4. I can no longer generate the ./configure there.
RHEL3, RHEL4, etc. should not matter, as long as you're using the latest tools. But seeing as using an older release is at odds with the presumption that you're doing a bootstrap build, there may be bugs in those tools, or in your installation. I cannot overemphasize this: please don't use automake older than 1.10, nor autoconf older than 2.60. The gap between autoconf-2.59 and 2.60 is far larger than the numbers imply. Your AM_PATH_CPPUNIT problem may go away once the new file, cpp/m4/cppunit.m4 appears. > > On RHEL4 they *are* later tools ;) >> Didn't you just say I was singing to the choir? >> Yet you continue to use these older versions of the tools. >> >> Please, do not spend time trying to make the bootstrap framework work >> with autoconf or automake that are not the latest. There is no point. > > That's sure becoming clear. There is a requirement that people using the bootstrap procedure have a very modern (cutting edge, even) build environment. That usually means having the latest stable versions of autoconf, automake, libtool. And if you build those yourself, then you also have to have the latest version of m4 and probably a couple other subsidiary tools. If you're building them yourself, then be sure to run "make check" for each package. I will write some code in bootstrap that makes it refuse to run (and give an informative diagnostic) if it doesn't find the required tools.
