From: "Yaakov (Cygwin/X)" <yselkowitz@users.sourceforge.net>
To: Reini Urban <rurban@x-ray.at>
Cc: cygwin@cygwin.com
Subject: Re: perl-5.14.2 switch
Date: Thu, 12 Jul 2012 18:40:00 -0000 [thread overview]
Message-ID: <CAGvSfezJym6tx+o79cBVf6vRR4zrPBhOHtL8TYQQtqCpEgMT3A@mail.gmail.com> (raw)
In-Reply-To: <CAHiT=DHsH_sZ9MPyc7o=t2m_Xb_XnD6KLXeMZ686oa3_-yYQCw@mail.gmail.com>
On Wed, Jul 11, 2012 at 10:07 AM, Reini Urban wrote:
> On Wed, Jul 11, 2012 at 4:53 AM, Yaakov (Cygwin/X) wrote:
>> Where this really breaks things is where a EU::E module is linked with
>> libtool (as in gnumeric's perl-loader plugin): the xsinit-generated
>> code calls boot_Win32CORE() but libtool will drop any static link
>> libraries when creating a shared library/module, meaning the link
>> fails with an unresolved reference to said function.
>>
>> AFAICS, static_ext should be empty; packages which actually need the
>> w32_* symbols can add Win32CORE as an argument to the EU::E functions.
>
> I see the problem, but I'm afraid that I cannot move Win32CORE from
> static to dynamic now.
> Generally we must have the ability to support both types of exts,
> static and dynamic. Some internal exts are also static, such as
> Cygwin, Internals, utf8, UNIVERSAL, DynaLoader, PerlIO, mro and
> partially version, attributes, Tie::Hash::NamedCapture. But they are
> included in libperl.
I'm not complaining that Win32CORE is static, if EU::E wouldn't insist
on using it all the time.
> Previously I solved this by adding Win32CORE.o to libperl itself.
> Should I do that?
I suppose so.
Yaakov
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2012-07-12 18:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-10 18:01 Reini Urban
2012-07-10 20:56 ` Yaakov (Cygwin/X)
2012-07-10 22:36 ` Reini Urban
2012-07-10 23:10 ` Yaakov (Cygwin/X)
2012-07-10 23:52 ` Reini Urban
2012-07-11 2:20 ` Yaakov (Cygwin/X)
2012-07-11 2:31 ` Reini Urban
2012-07-11 3:02 ` Yaakov (Cygwin/X)
2012-07-11 7:31 ` Dr. Volker Zell
2012-07-11 9:53 ` Yaakov (Cygwin/X)
2012-07-11 15:08 ` Reini Urban
2012-07-11 16:27 ` Steven Hartland
2012-07-11 17:01 ` Achim Gratz
2012-07-11 17:45 ` Steven Hartland
2012-07-11 18:30 ` Achim Gratz
2012-07-11 23:10 ` Steven Hartland
2012-07-12 5:20 ` Achim Gratz
2012-07-12 15:24 ` Reini Urban
2012-07-12 16:15 ` Corinna Vinschen
2012-07-12 16:50 ` Reini Urban
2012-07-12 18:40 ` Yaakov (Cygwin/X) [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAGvSfezJym6tx+o79cBVf6vRR4zrPBhOHtL8TYQQtqCpEgMT3A@mail.gmail.com \
--to=yselkowitz@users.sourceforge.net \
--cc=cygwin@cygwin.com \
--cc=rurban@x-ray.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).