This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[ANNOUNCEMENT] New: {libtool2.2/libltdl7}-2.2.2-1

GNU libtool is a generic library support script. Libtool hides the
complexity of using shared libraries behind a consistent, portable

This is a new major release, the first official cygwin release from the upstream 2.2 branch. As such, this release announcement is rather wordy -- but PLEASE note the WARNING below.

This release was built from the pristine upstream source; for the first time, there are no cygwin-specific patches.

--- WARNING ---
DO NOT install both libtool1.5 and libtool2.2. If you already have libtool1.5 installed, you should
(a) run setup.exe and uninstall libtool1.5 (but you can keep libltdl3 installed)
(b) run setup.exe again and install libtool2.2 (and libltdl7)

The libtool1.5 and libtool2.2 packages conflict, but cygwin's installer (setup.exe) is not yet capable of detecting or dealing with conflicts of this sort. You may install the runtime libraries from both versions:
as the runtime library packages are specifically constructed so that they can coexist. However, the development packages
can not both be installed at the same time. If you have any issues, the safest "recovery" procedure is to use the setup.exe program to uninstall both libtool1.5 and libtool2.2 packages (leave the libltdl* packages alone; they are fine). Then, run setup.exe again, and explicitly install either libtool1.5 or libtool2.2.

Note that there has already been reported to the mailing list an issue with regards to cygport: The cygport package explicitly requires libtool1.5, which may cause problems if you have cygport installed, and attempt to uninstall libtool1.5. We hope to resolve this issue soon.

--- From the official libtool-2.2 announcement ---
Following almost 4 grueling years in development, the Libtool Team is pleased to announce the final release of GNU Libtool 2.2.

GNU Libtool hides the complexity of using shared libraries behind a consistent, portable interface. GNU Libtool ships with GNU libltdl, which hides the complexity of loading dynamic runtime libraries (modules) behind a consistent, portable interface.

This is the first stable release from the Libtool 2.2 branch. Libtool 2.0 was never released, as by the time 1.9f was released from the stable branch, the head of the development branch had already become much more stable than the supposed stable branch!!

Compared to the old stable Libtool 1.5.x branch, the new stable 2.2 branch has been almost entirely rewritten, and has too many improvements and brand new features to enumerate here. Please see the NEWS file in the distribution for a comprehensive list of user visible changes.

Despite a new and improved M4 interface to Libtool from Autoconf, every effort has been made to retain backwards compatibility with the 1.5.x interfaces. Autoupdate (which ships with Autoconf) will help you upgrade your to the new interface when you are ready to migrate.

[ed: There was no cygwin release corresponding to the upstream libtool-2.2[.0] release, because a number of regressions related to cygwin cropped up. These regressions were corrected in the upstream libtool-2.2.2 release.]

"old" testsuite -- this is the same testsuite that has been used in libtool1.5.x for years
All 115 tests passed

"new" testsuite -- this is a dejaGnu-based testsuite that did not exist in libtool1.5.
ERROR: 63 tests were run,
5 failed (3 expected failures).
3 tests were skipped.

The two "unexpected" failures are
21: Link order of deplibs.
66: Run tests with low max_cmd_len
(where #66 just sees the #21 failure again). But on cygwin, #21 is not actually unexpected.)

--- CHANGES ---
As stated in the upstream announcement, there are too many improvements and changes between libtool-1.5.x and libtool-2.2.x to list here. There are some backwards incompatibilities in libltdl (which is why the DLLNUM has been bumped from "3" to "7"). However, basic libtool usage remains backwards compatible, although new and improved interfaces are also available. For example, in instead of

dnl which must be invoked before:

You can simply do:
LT_INIT([dlopen win32-dll])

One other behavior change: in the past, the libtool script was generated when a client packages' configure script was run, and was generated "ïn the middle" of that execution. This meant that often, client packages would explicitly "parse" the libtool script itself, during later parts of the configure -- or, sometimes compile and/or link tests required the use of the generated libtool.

That is no longer the default behavior. With libtool2.x, the libtool script itself is not generated until the AC_OUTPUT() phase of the configure script execution. If the previous behavior is required, you can force the libtool generation to occur earlier by using the LT_OUTPUT macro.

For an exhaustive list of changes, please read the NEWS file and the new info documentation (`info libtool').



To update your installation, click on the "Install Cygwin now" link on
the web page.  This downloads setup.exe to your
system.  Then, run setup and answer all of the questions.

MAKE SURE to uninstall libtool1.5 (if present) before installing libtool2.2.


If you want to unsubscribe from 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:

If you need more information on unsubscribing, start reading here:

Please read *all* of the information on unsubscribing that is available
starting at this URL.

Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]