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 to push the envelope on the dev tools. Just use the latest.
I've now tried RHEL3 with automake-1.10 and autoconf-2.61. No dice. Back to the libtool error. but I do have a libtool.m4 in my automake installation. No to worry. I am giving up generating a ./configure on RHEL3. It is a waste of time. I managed to get a ./configure generated on RHEL4 also available here at JPMC. I had to change the required version of automake back to 1.9.2 (it was 1.9.6). However, I don't expect that ./configure to enable a build to succeed on RHEL3 (as I've already tried a ./configure generated under Ubuntu). Any idea about the linking problem? Maybe it's a libtool version problem?
People building from a tarball can expect things to work with truly minimal prerequisites, *not* developers running ./bootstrap.
I know. You are singing to the choir.
