X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: <48B1B2C9.5050702@x-ray.at> Date: Sun, 24 Aug 2008 21:13:13 +0200 From: Reini Urban User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-AT; rv:1.8.1.13) Gecko/20080313 SeaMonkey/1.1.9 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Updated: perl-ExtUtils-Depends-0.300-2 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> In-Reply-To: <48B1AA16.8070000@users.sourceforge.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Yaakov (Cygwin Ports) schrieb: > Reini Urban wrote: >> Did you look into the root cause for this headache, libtool? > > The gtk2-perl hack had nothing to do with libtool, it had to do with the > unique case of linking one Perl module against another. I was referring > to the EU::Liblist::Kid patch we discussed in July. > >> Sooner or later I want to get back to normal perl builds, with libWin32CORE.a >> being linked externally. > > As this is a libtool limitation, I really don't see another solution to it. Sure. Fixing libtool of course. Mixing static and dynamic libs should be possible. >> With -Wl,--export-all-symbols it should really be able to allow this static lib >> together with the dlls. > > No, it won't. -- 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/