[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GNU Libtool 2.1b released (alpha release)

From: Gary V. Vaughan
Subject: Re: GNU Libtool 2.1b released (alpha release)
Date: Wed, 6 Feb 2008 14:09:43 +0800

Hi Jason,

On 6 Feb 2008, at 13:37, Jason Curl wrote:
Gary V. Vaughan wrote:
On 1 Feb 2008, at 01:06, Gary V. Vaughan wrote:
The Libtool Team is pleased to announce alpha release 2.1b of GNU
With only one bug reported and fixed since Feb 1, either this is the
most spectacularly well engineered release in the history of libtool,
or else it is the least well tested release ever...

Either way, if there are no more bugs found before Feb 10th, I plan
to roll up 2.2 final.  If you have any projects that you're thinking
of moving to libtool-2, please test them now so that we can fix any
problems you encounter before the final release!!
Hi Gary,

Are there instructions somewhere how I can have this build sit side-by-side of Libtool 1.5.24 on Linux (Suse 10.3) or Cygwin? So that if I encounter problems I can easily switch between the two as a developer?

I don't know offhand where to find similar instructions online, but
setting up parallel installations is fairly intuitive and straight
forward.  The only gotcha to be aware of is that Automake's aclocal uses
a $prefix/share/aclocal directory as a repository of third party macros
such as those provided by libtool.  To keep things simple I leave my OS
installations of all the autotools unmolested, and install separate
copies of autoconf, automake and libtool into /usr/local.  In my case
that is autoconf-2.61a and automake-1.10a from their repositories, and
libtool-2.1c from CVS.  After following the instructions for downloading
each, I set my PATH to have /usr/local/bin at the front and then build
and install autoconf, then automake and finally libtool.  Going back to
the OS installations is a simple matter of moving /usr/local/bin back
to the end of my PATH and running 'hash -r' to tell my shell to reindex
it's cache of application locations.

It's easy enough to see which copies your shell is using by typing:

  $ libtool --version

If your installation of test autotools is more temporary, you might like
to keep it separate from /usr/local, and you can easily do that by
choosing a different prefix for each of autoconf, automake and libtool
at configure time: ./configure --prefix=/opt/unstable.  When you've
finished testing, you can remove the whole /opt/unstable to clean up

If you have other packages that yours depends on, and need to make
some extra .m4 files visible to /opt/unstable/bin/aclocal, you can just
copy them across from /usr/share/aclocal/ to /opt/unstable/share/aclocal,
being careful not to overwrite any files installed by unstable automake
and unstable libtool.

There are plenty of other ways of managing parallel installations, but
this is what I've been using successfully for the last several years.

  ())_.              Email me: address@hidden
  ( '/           Read my blog:
  / )=         ...and my book:

Attachment: PGP.sig
Description: This is a digitally signed message part

reply via email to

[Prev in Thread] Current Thread [Next in Thread]