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. You'd expect that the ./configure would fail if it need m4 1.4.8 though, right? 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. Heck. At home I can now quite happily build qpid-cpp. That's just not convenient for the JPMC guys though. I'll suggest to them that they ought to order a build PC and put Fedora on it.
