Mailinglist Archive: opensuse (1640 mails)
| < Previous | Next > |
How to deploy a dynamically linked perl XS library? (Re: [opensuse] libperl.a gone in opensuse-11.0?)
- From: Josef Wolf <jw@xxxxxxxxxxxxx>
- Date: Fri, 1 Aug 2008 08:45:06 +0200
- Message-id: <20080801064506.GD26387@xxxxxxxxxxxxxx>
On Thu, Jul 31, 2008 at 07:28:18PM -0400, Cristian Rodríguez wrote:
OK, at least the security aspects have a point.
The question now becomes, how to (painless) deploy a perl XS library
which makes callbacks into perl. That means, the XS library needs
access to the my_perl variable, which is declared as
static PerlInterpreter *my_perl;
in the original libperl.so
Any hints?
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
Josef Wolf escribió:
Thanks for the answer, Christian!
On Thu, Jul 31, 2008 at 04:15:20PM -0400, Cristian Rodríguez wrote:
Josef Wolf escribió:
Was this library moved to a different package?No, it was removed, it has absolutely no use.
I think I have a use for it: I have a home-grown XS library which
provides functionality from a C library to perl. Linking everything
into one binary saves lots of pain when it comes to deployment of
such a program.
It does not really work the way you expect.. see:
http://people.redhat.com/drepper/no_static_linking.html
OK, at least the security aspects have a point.
The question now becomes, how to (painless) deploy a perl XS library
which makes callbacks into perl. That means, the XS library needs
access to the my_perl variable, which is declared as
static PerlInterpreter *my_perl;
in the original libperl.so
Any hints?
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
| < Previous | Next > |