Updated: libtool-devel-20020202-1

Charles Wilson cwilson@ece.gatech.edu
Tue Dec 31 07:35:00 GMT 2002

The 'libtool-devel' package has been updated to 20020202-1.
It contains a hacked version of libtool(from CVS 02-Feb-2002),
installed into /usr/autotool/devel/*.  Basically, this is a
forward port of the hacks from the previous, 20010531 release
to current libtool CVS HEAD.

The good news:  this version passes the "dry-run" test that
the previous one failed.  It adds no new selftest failures --
AND it passes the new C++ libtool testsuite.  So, it should
help to solve the problems the 20010531 version had with C++
code.  (I've used to it build the C++ 'libplotter' library from
GNU plotutils.)

See the NOTES at the end of this email for some additional information.

Chuck Wilson

To update your installation, click on the "Install Cygwin now" link
on the http://cygwin.com/ web page.  This downloads setup.exe to
your system.  Save it and run setup, answer the questions and pick
up 'libtool-devel' from the 'Devel' category.  You may need to
click the "Full" button if it doesn't show up.

Note that downloads from sources.redhat.com (aka cygwin.com) aren't
allowed due to bandwidth limitations.  This means that you will need
to find a mirror which has this update.

In the US, ftp://mirrors.rcn.net/mirrors/sources.redhat.com/cygwin/
is a reliable high bandwidth connection.

In Japan, ftp://ftp.u-aizu.ac.jp/pub/gnu/gnu-win32/ is already

In DK, http://mirrors.sunsite.dk/cygwin/ is usually up-to-date.

If one of the above doesn't have the latest version of this package
you can either wait for the site to be updated or find another

Please  send questions or comments to the Cygwin mailing list at:
cygwin@sources.redhat.com .  If you want to subscribe go to:
http://cygwin.com/lists.html I would appreciate if you would use
this mailing list rather than emailing me directly.  This includes
ideas and comments about the setup utility or Cygwin in general.

If you want to make a point or ask a question the Cygwin mailing
list is the appropriate place.


To unsubscribe to the cygwin-announce mailing list, look at the
"List-Unsubscribe: " tag in the email header of this message. Send
email to the address specified there.  It will be in the format:



1) libtool (along with autoconf and automake) are really only for
developer use.  If you don't already have a good understanding of
how to use the tools -- and experience using them on a "normal"
unix platform -- then you probably DON'T want to "learn" with this
port.  The combination of
   a) the brain dead DLL format (compared to elf shared libs)
   b) still evolving shared lib support in the binutils/gcc/cygwin
   c) the VERY beta status of libtool-devel
   d) the wacky -stable/-devel/wrapper structure we are forced to
      use means that cygwin is NOT a good platform to "learn how to
      use the autotools".

PLEASE do not ask for tutorials on automake/autoconf/libtool use
on the cygwin mailing list -- you will either be ignored, or mocked.

2) ALL libtools since version 1.4 (May 2001) have dispensed with
ltconfig.sh.  So, when re-libtoolizing, be sure to delete ltconfig.sh

3) You can't "pick and choose".  If you want to use libtool-devel, you
must also use automake-devel and autoconf-devel.  Likewise, all of the
-stable versions must be used together.

4) libtool-devel installs its info files and man pages into /usr/* as
well as into /usr/autotool/devel/*.  Also, libtool-devel's cygltdl-3.dll
is installed into /usr/bin.  Therefore, applications dynamically linked
to that DLL by libtool-stable and by libtool-devel will both use
libtool-devel's version at runtime.  (Fortunately, this is okay --
libtool-devel's cygltdl-3.dll works fine with apps that expect
libtool-stable's version).

More information about the Cygwin-announce mailing list