On Sun, Feb 03, 2008 at 06:02:34PM -0800, Russ Allbery wrote: > > Since the perl package in Debian is not linked against libperl, perl > > extensions also cannot be linked against libperl since this would cause > > two copies of the perl XS symbols to be loaded.
> And this is the problem. It *is* linked against libperl on every > architecture except i386, and on those architectures, the perl binary is > also linked against libperl instead of duplicating the code. I think i386 > should be changed to match. This came up on debian-devel recently. I agree that we're better off if perl links to libperl on all archs, so we can maximize the use of RTLD_LOCAL. I think libltdl's API should also be fixed. > > BTW, a similar bug was reported recently (... in the past 3 months or > > so; and possibly only via the mailing list) on the OpenLDAP package > > because back_meta references symbols from back_ldap but doesn't link > > against it, so back_meta in Debian can never see those symbols even if > > back_ldap is loaded first. I have a possible fix for this (which btw is > > detected by upstream's 'make test'), but have been reluctant to > > implement it so far because it's an ugly thing involving making symlinks > > to back_ldap to keep libtool happy. > Can't we just link back_meta against back_ldap? Or is that what your fix > for the problem does? Yeah, that's the fix; but libtool --install blows up nastily when you link against something that's not a system library, *and* has a name that doesn't begin with "lib", because -lback_ldap doesn't work very well for relinking... :) -- 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/ [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
