This is the mail archive of the
mailing list for the Cygwin project.
[ANNOUNCEMENT] New on sourceware: libtool-20010531a-1
- From: Charles Wilson <cwilson at ece dot gatech dot edu>
- To: cygwin at cygwin dot com
- Date: Wed, 16 Jan 2002 03:39:22 -0500
- Subject: [ANNOUNCEMENT] New on sourceware: libtool-20010531a-1
- Reply-to: cygwin at cygwin dot com
The 'libtool' package is now available on sourceware. GNU libtool
is a generic library support script. Libtool hides the complexity
of using shared libraries behind a consistent, portable interface.
However, THIS package is NOT the real libtool. It's a set of
wrapper scripts that call the REAL libtool from the libtool-stable
package or from the libtool-devel package, depending on the needs
of your target.
This is similar to the large restructuring of the autotools that
occured in late November. See this message:
"Restructuring the automake and autoconf packages"
for an explanation as to why we need wrapper scripts and these
-stable and -devel installations of the autotools.
See the NOTES at the end of this email for some additional information.
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' from the 'Devel' category. You may need to click the
"Full" button if it doesn't show up. You might want to make sure
you update/install ALL of the following packages:
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:
email@example.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.
*** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***
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
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.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html