[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: Joe Orton <joe_at_manyfish.co.uk>
Date: 2004-02-23 21:45:51 CET

On Mon, Feb 23, 2004 at 11:04:57AM -0800, Justin Erenkrantz wrote:
> --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

Yeah, the Debian-patched libtool-1.4.3 used to package 1.0.0 has both a
patch to fix DESTDIR installs, and a patch to ignore -pthread on link
lines.

Use of libtool 1.5/1.5.2 is not advisable since the configure script
would then fail on systems without a C++ compiler.

Of these problems I'd worry least about DESTDIR installs failing: people
doing DESTDIR installs are probably packagers and can just run
autogen.sh in their package builds using known-good version of libtool.

So libtool 1.4.3 probably remains the version of choice.

joe

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Feb 23 21:46:06 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.