On Fri, Apr 19, 2013 at 05:26:41PM +0300, Niko Tyni wrote: > On Thu, Apr 18, 2013 at 11:01:17PM -0700, Steve Langasek wrote: > > On Thu, Apr 18, 2013 at 04:18:38PM +0100, Neil Williams wrote:
> > > I don't see a need to have the perl:i386 interpreter installed on amd64
> > > in order to build third party i386 perl modules, the amd64 interpreter
> > > should be fine, just as it is when cross building third party armel perl
> > > modules.
> > But you need the foreign-architecture libperl installable, for the perl
> > modules to be linked against.
> I don't think you do. The modules aren't linked against libperl, it's
> the other way around: libperl loads them at run time with dlopen(3).
> They are effectively plugins in a private directory.
Hmm, well, it seems that's true for the case of libperl; but that means
there's suboptimal behavior when using libperl as an embedded interpreter
(which I assume is still supported?) because of likely use of RTLD_LOCAL by
the calling application: extensions for embedded interpreters that exist as
plugins with undefined symbols ('ldd -d -r') may be unable to resolve their
symbols at load time because the interpreter isn't in the global namespace.
So perhaps this is all a bit theoretical in practice, and people are
muddling through with such suboptimal behavior.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
signature.asc
Description: Digital signature
