Download libtool-2.2

Once again there are an enormous number of improvements over the last release. This code in this release has has been broadly rewritten, and many of the internal and external interfaces have changed. Wherever possible we have provided backwards compatibility. Autoupdate is your friend. There are an enormous number of changes and improvements since the last release. I've just uploaded libtool 1. The md5sums of all files are as given below, but you should download the associated. My public signature is available from my website , and wwwkeys.

I am pleased to announce the release of GNU Libtool 1. Some features of the new release are:. This release was bootstrapped and tested with Automake 1. Tarballs and both traditional and xdelta diffs against release 1. The Libtool Team is pleased to announce alpha release 1. This release has improved support for cygwin and other improvements over the previous Libtool alpha release.

This release will likely be the last alpha before Libtool version 1. You will find diffs and xdeltas from libtool If you prefer, you can fetch the unbootstrapped sourcecode using anonymous CVS by following these instructions but using the tag released. There are also a small number of incremental improvements and bugfixes since the last release.

This is the first release to include the code that has been in development on the multi-language-branch for the last 18 months or so, that was recently merged into the mainline development sources.

If you prefer, you can fetch the unbootstrapped sourcecode using anonymous CVS by following these instructions but using the tag releaseb. The main difference between this release and libtool On the 2nd Anniversary of the release of libtool If you prefer, you can fetch the unbootstrapped sourcecode using anonymous CVS by following these instructions but using the tag release It's getting late, and I need to be in bed because Santa won't come until we're asleep, right?

But my next step will be to follow zeiz's directions to portsnap fetch extract that's what you mean when you say "updating the ports tree," right? Merry Christmas! Click to expand Pegasus Member Reaction score: 6 Messages: Hello guys, I have an issue in this regard as well. Now I want to install open-vm-tools on my vmware box windows host. The thing is that the installation fails at libnotify since the version of libtools installed is I think the latest one available with version 7.

Well, Ive done portupgrade -R libtool and it basically tells me that it is excluding up-to-date packages. How do I go about updating the libtool to 2. Keen to hear from u people. DutchDaemon knows what he's talking about. However, here's what I learned from it: Never install the ports collection from the install CD. They are soon outdated after the release.

Now I do a basic install, and then I use portsnap fetch and extract to install the most recent ports collection. Last time I did this, I got the most recent version of libtool 2. Of course, you're probably not wanting to do a complete reinstall On googling realised its a bug. Then I did see dutchdeamon's post above and realized I might as well uninstall libtool1. Seems to be working for now. I do not know if some earlier dependencies might be affected.

Can I create a symlink for libtool1. Keen to hear frm you guys,. By "never was able to fix the problem," I mean I scrapped that install, started over. That's kind of how I'm learning BSD. Thanks for the clarification about the ports collection.

I'd like to try portmanager and see if it's a little lighter. You'll find much more knowledge about portmaster than about portmanager on these forums. DD, I noticed your portmaster link was to FreshPorts. Xilinx Support Community. Sign in to ask the community. Embedded Systems Embedded Linux.

View This Post. September 4, at PM. Libtool version issue with Hello, I have been using petalinux for a while. My project is currently working as expected with petalinux I am quite sure I have all petalinux dependencies installed. I am migrating to One of them is to build mono. However: while building mono is perfectly fine under This is libtool 2. I tried many ways to fix this, including running autoreconf -ivf from inside or outside recipe, but in the best case it just fail later saying it cannot find "..

There are numerous longstanding bugs in the Automake bug tracker which need attention. Help with any of the other outstanding bugs is welcome also. If you have time and inclination, please pick any and give it a whirl; no one is working on them. For bugs in Automake, please see the Bug Reporting section of the manual.

Automake depends on other projects; it's best for everyone if bug reports are directed to the correct place.