[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Bumping libtool version was Re: Problem compiling 1.0.0beta1 on Solaris 9

From: Philip Martin <philip_at_codematters.co.uk>
Date: 2004-02-23 20:40:54 CET

Justin Erenkrantz <justin@erenkrantz.com> writes:

> --On Monday, February 23, 2004 7:31 PM +0100 Michael Legart
> <michael@legart.dk> wrote:
>
>> Philip Martin wrote:
>>>
>>> So it would appear that either the autoconf or libtool used in the
>>> tarball don't properly support Solaris. Which versions do you have
>>> installed?
>>
>> I'm using autoconf (GNU Autoconf) 2.57 and ltmain.sh (GNU libtool) 1.5
>> (1.1220 2003/04/05 19:32:58)
>
> FWIW, libtool 1.4.3 works for me here on Solaris 9. However, I'm
> using forte. It's *very* possible that libtool 1.4.3 has some problems
> with the GCC 3.x series on Solaris. So, yeah, perhaps we should bump
> up our release requirement for libtool to 1.5+ (1.5.2 is latest?). (I
> don't *think* autoconf would be involved.)
>
> Also, Greg Hudson on IRC said that DESTDIR isn't supported in libtool
> 1.4.3, so that's probably a reason to upgrade as well. -- justin

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)

-- 
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Feb 23 20:40:46 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.