"Steven Shaw" <[EMAIL PROTECTED]> wrote: > On 06/12/06, Jim Meyering <[EMAIL PROTECTED]> wrote: >> P.S. If you build your own auto* tools, you should be sure to get >> the latest stable m4 version, 1.4.8, and build and install *it* >> (and put it first in your path) before building autoconf or automake. > > I may not have done that. I did install m4-1.4.something but probably > not before I built automake/autoconf.
That is the key. m4 must be installed, and in your path when building autoconf (and maybe automake, too), otherwise, some of autoconf's machinery won't work properly. I think you'd see the failure if you run "make check", but not at configure time. > You'd expect that the ./configure would fail if it need m4 1.4.8 though, > right? The notes in m4's HACKING file make me think m4-1.4.5 is new enough. > This whole process has been very frustrating for you and me both. I > got a build to work today briefly but when I tried again from a fresh > checkout it was broke because of subsequent patches. It's not my call > to generate the ./configure on RHEL3 or RHEL4. It's something that > JPMC want to be able to do in order to be able to build at least a > qpid-cpp-client distribution (with examples) for an internal team who > are trying that out. It all worked fine prior to autoconf/automake. Sorry for the hassle, but rest assured it's for a good cause. You're just having to endure the get-the-kinks-out phase. Would another tarball help? Or even regularly-built/published snapshot tarballs?
