X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Message-ID:	<48B1AA16.8070000@users.sourceforge.net>
Date:	Sun, 24 Aug 2008 13:36:06 -0500
From:	"Yaakov (Cygwin Ports)" <yselkowitz AT users DOT sourceforge DOT net>
User-Agent:	Thunderbird 2.0.0.16 (Windows/20080708)
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>
In-Reply-To:	<6910a60808240942p14201ae6p9b86b0c7cd3e89bc@mail.gmail.com>
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

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.

> With -Wl,--export-all-symbols it should really be able to allow this static lib
> together with the dlls.

No, it won't.


Yaakov

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEAREIAAYFAkixqhYACgkQpiWmPGlmQSPrwgCeP7PbqibUGCt6d7w5/h2pEsXM
ZdQAn3NcFE0e8gHdT19uFICmsAd5PLec
=p971
-----END PGP SIGNATURE-----

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

- Raw text -