> steve@spartacus:~$ sudo /etc/init.d/slapd start
> Starting OpenLDAP: slapd - failed:
> 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.
>
> Can't call method "config" on an undefined value.
Okay, thanks.
I could have sworn that this wasn't happening with 2.3.30 or
thereabouts... oh, I know what the difference is. I was testing on
amd64. Right, now I understand.
This is that problem that's caused by Perl modules not being linked with
libperl on i386 (but not on any other architecture) and instead
duplicating the symbols between perl and libperl and leaving them
undefined in the modules. This works correctly if the modules are linked
with libperl, which they are on amd64 and Debian's other architectures.
You're right, this isn't closed; it's just i386-specific.
retitle 327585 slapd: [i386] perl backend failed to load XS (unknown symbols)
thanks
Stephen Gran <email address hidden> writes:
> steve@spartacus:~$ sudo /etc/init.d/slapd start 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.
> Starting OpenLDAP: slapd - failed:
> 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.
>
> Can't call method "config" on an undefined value.
Okay, thanks.
I could have sworn that this wasn't happening with 2.3.30 or
thereabouts... oh, I know what the difference is. I was testing on
amd64. Right, now I understand.
This is that problem that's caused by Perl modules not being linked with
libperl on i386 (but not on any other architecture) and instead
duplicating the symbols between perl and libperl and leaving them
undefined in the modules. This works correctly if the modules are linked
with libperl, which they are on amd64 and Debian's other architectures.
You're right, this isn't closed; it's just i386-specific.
-- www.eyrie. org/~eagle/>
Russ Allbery (<email address hidden>) <http://