On Mon, 2004-02-23 at 20:36, kfogel@collab.net wrote:
> Philip Martin <philip@codematters.co.uk> writes:
> > Michael, you said that the 0.37 tarball worked. If you still have
> > that tarball (I can't find it) unpack it, run ./configure and then run
> > ./configure --version and ./libtool --version to see what versions
> > it used.
> >
> > I seem to remember we had a problem in the past when the tarball was
> > made with Debian's patched libtool rather than a pristine upstream
> > one. Karl, can you say what versions were used? They identify
> > themselves as
> > GNU Autoconf 2.53
> > ltmain.sh (GNU libtool) 1.4.3 (1.922.2.111 2002/10/23 02:54:36)
>
> That seems right.
>
> It was my home machine (which I don't have access too from here ATM).
> But I can tell you that I first tried to build the tarball on my work
> machine, and buildcheck complained:
>
> You need libtool version 1.4.3 or newer installed
>
> So I moved the process to the home machine, and buildcheck didn't
> complain there. But, my home machine *is* a Debian 'testing' box.
This is the same issue that happens again and again. I've been
bitten by it too. The trick is that a RM needs to have a _prisitine_
libtool 1.4.3 in his path. I installed it in my homedir and add
it as the first thing in my PATH when doing releases.
Karl, I remember that we hunted for libtool 1.4.3 past november when
doing a point release ;) :). Did you forget? Not really that weird
in the middle of the night, while being /.'ed ;).
Sander
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Feb 23 22:44:44 2004