> I was surprised to hear that perl modules were linked to libperl on !i386
> (which would be the correct thing to do, I just didn't think the standard
> perl build rules handled this). So I checked, and on my amd64 system:
>
> $ ldd /usr/lib/perl/5.8.8/auto/POSIX/POSIX.so
> libm.so.6 => /lib/libm.so.6 (0x00002b02d4451000)
> libc.so.6 => /lib/libc.so.6 (0x00002b02d46d2000)
> /lib64/ld-linux-x86-64.so.2 (0x0000555555554000)
> $
>
> So sure enough, I tried the test case from
> <https://bugs.launchpad.net/ubuntu/+source/openldap2.3/+bug/90812>, and:
>
> # slapd
> Error Can't load '/usr/lib/perl/5.8/auto/POSIX/POSIX.so' for module POSIX: /usr/lib/perl/5.8/auto/POSIX/POSIX.so: undefined symbol: PL_sig_name at /usr/lib/perl/5.8/XSLoader.pm line 70.
> at /usr/lib/perl/5.8/POSIX.pm line 26
> Compilation failed in require at /etc/perl/SampleLDAP.pm line 2.
> BEGIN failed--compilation aborted at /etc/perl/SampleLDAP.pm line 2.
> Compilation failed in require at (eval 2) line 1.
> BEGIN failed--compilation aborted at (eval 2) line 1.
> #
>
> I have no idea if this is a regression from previous perl builds, but it
> looks to me like it's a general problem at this point.
Huh. I feel like I'm losing my mind. I could have sworn that I checked
this at one point and the modules were linked with libperl on amd64, but
maybe I'm dreaming. /usr/bin/perl is liked with libperl on amd64 and not
on i386, but yeah, even in stable the modules aren't.
Steve Langasek <email address hidden> writes:
> I was surprised to hear that perl modules were linked to libperl on !i386 perl/5. 8.8/auto/ POSIX/POSIX. so 1000) 2000) ld-linux- x86-64. so.2 (0x000055555555 4000) /bugs.launchpad .net/ubuntu/ +source/ openldap2. 3/+bug/ 90812>, and: perl/5. 8/auto/ POSIX/POSIX. so' for module POSIX: /usr/lib/ perl/5. 8/auto/ POSIX/POSIX. so: undefined symbol: PL_sig_name at /usr/lib/ perl/5. 8/XSLoader. pm line 70. perl/5. 8/POSIX. pm line 26 SampleLDAP. pm line 2. SampleLDAP. pm line 2.
> (which would be the correct thing to do, I just didn't think the standard
> perl build rules handled this). So I checked, and on my amd64 system:
>
> $ ldd /usr/lib/
> libm.so.6 => /lib/libm.so.6 (0x00002b02d445
> libc.so.6 => /lib/libc.so.6 (0x00002b02d46d
> /lib64/
> $
>
> So sure enough, I tried the test case from
> <https:/
>
> # slapd
> Error Can't load '/usr/lib/
> at /usr/lib/
> Compilation failed in require at /etc/perl/
> BEGIN failed--compilation aborted at /etc/perl/
> Compilation failed in require at (eval 2) line 1.
> BEGIN failed--compilation aborted at (eval 2) line 1.
> #
>
> I have no idea if this is a regression from previous perl builds, but it
> looks to me like it's a general problem at this point.
Huh. I feel like I'm losing my mind. I could have sworn that I checked
this at one point and the modules were linked with libperl on amd64, but
maybe I'm dreaming. /usr/bin/perl is liked with libperl on amd64 and not
on i386, but yeah, even in stable the modules aren't.
-- www.eyrie. org/~eagle/>
Russ Allbery (<email address hidden>) <http://