Re: bootstrap problem

2006-12-06 Thread Steven Shaw
With automake-1.10 on RHEL3: $ ./bootstrap autom4te: unknown language: Autoconf-without-aclocal-m4 aclocal: autom4te failed with exit status: 1 $ automake --version automake (GNU automake) 1.10 Written by Tom Tromey [EMAIL PROTECTED] and Alexandre Duret-Lutz [EMAIL PROTECTED]. Copyright

Re: bootstrap problem

2006-12-06 Thread Steven Shaw
On 06/12/06, Jim Meyering [EMAIL PROTECTED] wrote: It's probably one of these: - improper installation of autoconf or automake - autom4te directory created by some other version of tools You're not the first to get that diagnostic:

Re: bootstrap problem

2006-12-06 Thread Jim Meyering
Steven Shaw [EMAIL PROTECTED] wrote: On 06/12/06, Jim Meyering [EMAIL PROTECTED] wrote: It's probably one of these: - improper installation of autoconf or automake - autom4te directory created by some other version of tools You're not the first to get that diagnostic:

Re: bootstrap problem

2006-12-06 Thread Steven Shaw
On 06/12/06, Jim Meyering [EMAIL PROTECTED] wrote: Are you sure? Yes I am certain. autoconf, 2.61 is the latest stable release, I was using the default on RHEL3 which is 2.57. but 2.60 should work. Maybe even 2.59, but please don't. I've been trying hard to encourage people not to try

Re: bootstrap problem

2006-12-06 Thread Jim Meyering
Jim Meyering [EMAIL PROTECTED] wrote: Steven Shaw [EMAIL PROTECTED] wrote: ... I have automake-1.10 in my PATH. What are the other right tools? autoconf, 2.61 is the latest stable release, but 2.60 should work. Maybe even 2.59, but please don't. I've been trying hard to encourage people not

Re: bootstrap problem

2006-12-06 Thread Steven Shaw
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

Re: bootstrap problem

2006-12-06 Thread Robert Greig
On 06/12/06, Steven Shaw [EMAIL PROTECTED] wrote: 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

Re: bootstrap problem

2006-12-06 Thread Steven Shaw
On 06/12/06, Robert Greig [EMAIL PROTECTED] wrote: However we are able to install whatever versions of the build tools are required. Are we happy that we have established a list of versions that should all work together? I think so. IIRC I already have the following installed at the office

Re: bootstrap problem

2006-12-06 Thread Jim Meyering
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

Re: bootstrap problem

2006-12-05 Thread Jim Meyering
Alan Conway [EMAIL PROTECTED] wrote: Hi Jim, I'm still having problems with bootstrap in a fresh checkout: [EMAIL PROTECTED] cpp]$ ./bootstrap /bin/sh: AmqpClass.java: command not found /bin/sh: line 1: -cp: command not found make: *** [timestamp] Error 127 automake: cannot open

Re: bootstrap problem

2006-12-05 Thread Steven Shaw
On 05/12/06, Alan Conway [EMAIL PROTECTED] wrote: Steve, I did this with the initial patch from 2.60-2.59 can you try it with RHEL 3 versions? I changed the AC_PREREQ(2.59) in configure.ac, and a couple other things - if you run with the default RHEL 3 tools the error messages will tell you what

Re: bootstrap problem

2006-12-05 Thread Daniel Kulp
On Tuesday 05 December 2006 10:14, Alan Conway wrote: On Tue, 2006-12-05 at 15:00 +, Steven Shaw wrote: Oh. I backed the AC_PREREQ to 2.57 and automake requirement to 1.6.3 in Makefile.am. From bootstrap I get: Maybe Jim can help here. Thanks for the hand. It's be a few years since I

Re: bootstrap problem

2006-12-05 Thread Jim Meyering
Steven Shaw [EMAIL PROTECTED] wrote: I'm trying to build from a fresh checkout on RHEL3. Because the default autoconf version is not support (2.57), I've installed the following: autoconf-2.61 automake-1.9.6 libtool-1.5.22 m4-1.4.8 I've locally added the set -x to bootstrap to make

Re: bootstrap problem

2006-12-05 Thread Jim Meyering
Alan Conway [EMAIL PROTECTED] wrote: On Tue, 2006-12-05 at 15:00 +, Steven Shaw wrote: Oh. I backed the AC_PREREQ to 2.57 and automake requirement to 1.6.3 in Makefile.am. From bootstrap I get: Maybe Jim can help here. Thanks for the hand. It's be a few years since I did any serious

Re: bootstrap problem

2006-12-05 Thread Jim Meyering
Daniel Kulp [EMAIL PROTECTED] wrote: checking for CPPUNIT... configure: error: Package requirements (cppunit = 1.10.2) were not met: No package 'cppunit' found I'm stumped on that one as I DO have cppunit installed. [EMAIL PROTECTED] ~/working/qpid/cpp $ cppunit-config --version 1.10.2

Re: bootstrap problem

2006-12-05 Thread Daniel Kulp
On Tuesday 05 December 2006 10:54, Steven Shaw wrote: On 05/12/06, Daniel Kulp [EMAIL PROTECTED] wrote: checking for APR... yes checking for CPPUNIT... configure: error: Package requirements (cppunit = 1.10.2) were not met: No package 'cppunit' found Probably because it required

Re: bootstrap problem

2006-12-05 Thread Steven Shaw
On 05/12/06, Jim Meyering [EMAIL PROTECTED] wrote: This is the same aclocal problem you saw before. perhaps your path is not set right (so you're running some other version of aclocal), or maybe the libtool.am file is installed in the wrong place. I can assure you that my PATH was set up

Re: bootstrap problem

2006-12-05 Thread Steven Shaw
On 05/12/06, Daniel Kulp [EMAIL PROTECTED] wrote: However, why does all the README's and such say: * CppUnit 1.10.2: http://cppunit.sourceforge.net That's not quite fair. You didn't read all the READMEs! Methinks you only read README-dev.

Re: bootstrap problem

2006-12-05 Thread Steven Shaw
On 05/12/06, Jim Meyering [EMAIL PROTECTED] wrote: Well, would you please try with the newer version: automake-1.10? I'd rather not debug a problem if it's already been fixed in the latest. Thing is that I got it bootstrap working using standard RHEL3 versions. I just had to change a couple of

Re: bootstrap problem

2006-12-05 Thread Jim Meyering
Steven Shaw [EMAIL PROTECTED] wrote: On 05/12/06, Jim Meyering [EMAIL PROTECTED] wrote: Well, would you please try with the newer version: automake-1.10? I'd rather not debug a problem if it's already been fixed in the latest. Thing is that I got it bootstrap working using standard RHEL3

Re: bootstrap problem

2006-12-05 Thread Jim Meyering
Steven Shaw [EMAIL PROTECTED] wrote: On 05/12/06, Jim Meyering [EMAIL PROTECTED] wrote: Thanks. I did see it. ISTR that one problem is you switched from an AC_ macro to a now-deprecated AM_ one. Support for deprecated bits will likely be phased out in upcoming releases. So it's best not to

Re: bootstrap problem

2006-12-05 Thread Jim Meyering
Steven Shaw [EMAIL PROTECTED] wrote: ... It is defined by configure. The actual value it gets set to can be seen in lib/common/Makefile. For me it's empty because I turned it off: $ grep APR_LIBS.= lib/common/Makefile APR_LIBS = Well it's not for me: $ grep APR_LIBS

Re: bootstrap problem

2006-12-05 Thread Alan Conway
On Tue, 2006-12-05 at 16:27 +, Steven Shaw wrote: On 05/12/06, Daniel Kulp [EMAIL PROTECTED] wrote: However, why does all the README's and such say: * CppUnit 1.10.2: http://cppunit.sourceforge.net That's not quite fair. You didn't read all the READMEs! Methinks you only read

Re: bootstrap problem

2006-12-05 Thread Steven Shaw
On 05/12/06, Jim Meyering [EMAIL PROTECTED] wrote: I'll try with automake 1.10 and see if it works with the latest stable autotools. Good! :-) I will still try tomorrow on rhel3 with automake-1.10 but the good news is that it now works at home on Ubuntu Edgy with the following versions: