X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Message-ID: <48B1BA2B.64130DDA@dessent.net> Date: Sun, 24 Aug 2008 12:44:43 -0700 From: Brian Dessent X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: Updated: perl-ExtUtils-Depends-0.300-2 References: <48B10011.50508@users.sourceforge.net> <6910a60808240942p14201ae6p9b86b0c7cd3e89bc@mail.gmail.com> <48B1AA16.8070000@users.sourceforge.net> <48B1B2C9.5050702@x-ray.at> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin@cygwin.com Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Reini Urban wrote: > Sure. Fixing libtool of course. > Mixing static and dynamic libs should be possible. I think you're missing the point of why libtool disallows it: not because it won't work in a specific instance, but because it is not portable. There is no fix for the fact that on some systems it's impossible to link a shared library that contains non-PIC code, and that on those same systems static libraries are built non-PIC. The core idea behind libtool is to abstract away these sort of details, so if it made an exception and allowed this to succeed on some systems but refused on those systems where it's impossible then it would fail to meet this most basic goal. In other words: there's nothing to fix. Why can't the libWin32CORE library just be shared? Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/