X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Message-ID: <6910a60808241259p36c79cdl5ab902fbb96dd9b7@mail.gmail.com>
Date: Sun, 24 Aug 2008 21:59:23 +0200
From: "Reini Urban" <rurban AT x-ray DOT at>
To: cygwin AT cygwin DOT com
Subject: Re: Updated: perl-ExtUtils-Depends-0.300-2
In-Reply-To: <48B1BA2B.64130DDA@dessent.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <48B10011 DOT 50508 AT users DOT sourceforge DOT net> 	 <6910a60808240942p14201ae6p9b86b0c7cd3e89bc AT mail DOT gmail DOT com> 	 <48B1AA16 DOT 8070000 AT users DOT sourceforge DOT net> <48B1B2C9 DOT 5050702 AT x-ray DOT at> 	 <48B1BA2B DOT 64130DDA AT dessent DOT net>
X-Google-Sender-Auth: 883faa242ceaae7a
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

2008/8/24 Brian Dessent:
> 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.

Hmm, no tiny exception for us? ;-)

> Why can't the libWin32CORE library just be shared?

CORE stands there for a reason. I'll ask Jan Dubois. I want it either
shared or builtin.
p5p wants it statically linked, but only thought of MSVC and ld apparently.
The linker does it fine, only Yaakov needs it for some libtool packages.
A normal dynamic extension as Win32 will be the easiest, but they splitted it
from the Win32 extension to CORE for a reason. Less external deps probably.
So we went the way to link just the .o.
-- 
Reini Urban
http://phpwiki.org/ http://murbreak.at/

--
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/