Mailing-List: contact cygwin-announce-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-announce-owner AT cygwin DOT com Delivered-To: mailing list cygwin-announce AT cygwin DOT com Delivered-To: moderator for cygwin-announce AT cygwin DOT com Message-ID: <3C453C12.3060903@ece.gatech.edu> Date: Wed, 16 Jan 2002 03:38:42 -0500 From: Charles Wilson Reply-To: cygwin AT cygwin DOT com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2 X-Accept-Language: en-us MIME-Version: 1.0 To: cygwin-announce AT cygwin DOT com Subject: New on sourceware: libtool-devel-20010531-6 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit The 'libtool-devel' package has added to the cygwin distribution. It contains a hacked version of libtool(from CVS 31-May-2001), installed into /usr/autotool/devel/*. This version of libtool takes advantage of the auto-import/auto-export capabilities of newer (2001-08-31) binutils in order to build DLLs without all that "__declspec()" muck. (Of course, you have to re-libtoolize your target package with the new version to get that to work -- which may also entail updating configure.in to work with autoconf-devel (autoconf-2.52) and re-autoconf-ing and re-automake-ing...) The libtool, libtool-devel, libtool-stable structure is similar to the large restructuring of the autotools that occured in late November. See this message: "Restructuring the automake and autoconf packages" http://cygwin.com/ml/cygwin-announce/2001/msg00177.html 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. -- 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. You might want to make sure you update/install ALL of the following packages: libtool libtool-devel libtool-stable 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 updated. 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 mirror. Please send questions or comments to the Cygwin mailing list at: cygwin AT sources DOT redhat DOT 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: cygwin-announce-unsubscribe-YOU=YOURDOMAIN DOT COM AT cygwin DOT com NOTES: 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 first. 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).