Hi p5p,
we're currently doing the 5.8.8 -> 5.10.0 transition in Debian, and the
binary incompatibility in the XS module interface is biting us in an
unexpected way.
In a nutshell, it's possible during the upgrade to temporarily end up
in a state where perl is still 5.8.8, but some XS modules are already
the new ones (ie. built for 5.10.0).
The package scripts try to fail gracefully in situations like this by
doing effectively an 'eval "require Locale::gettext"' or the like.
Unfortunately this doesn't work: the require succeeds but the dynamic
linker kills the script off immediately afterwards because of a
symbol lookup error.
This can be circumvented by setting $ENV{PERL_DL_NONLAZY}=1 before
the eval, so it's arguably a feature. I'm wondering if it would make
sense for Perl to do this automatically inside all eval statements.
After all, the user is using the eval because he wants to catch
exceptions immediately.
If this is obviously too intrusive or otherwise broken, please hit me
with a cluebat. In that case, I think the eval entry in perlfunc.pod
could mention the issue.
I can take a shot at a patch for either case, I'd just like to know
which is the right thing to do.
Details on the Debian issue can be found at <http://bugs.debian.org/479711>,
cc'd as [EMAIL PROTECTED] .
# perl -e 'local $ENV{PERL_DL_NONLAZY}=0; eval "require Locale::gettext"; print
"got: $@" if $@; exit 0'; echo $?
perl: symbol lookup error: /usr/lib/perl5/auto/Locale/gettext/gettext.so:
undefined symbol: Perl_Istack_sp_ptr
127
# perl -e 'local $ENV{PERL_DL_NONLAZY}=1; eval "require Locale::gettext"; print
"got: $@" if $@; exit 0'; echo $?
got: Can't load '/usr/lib/perl5/auto/Locale/gettext/gettext.so' for module
Locale::gettext: /usr/lib/perl5/auto/Locale/gettext/gettext.so: undefined
symbol: Perl_Imarkstack_ptr_ptr at /usr/lib/perl/5.8/DynaLoader.pm line 225.
at (eval 1) line 3
Compilation failed in require at (eval 1) line 3.
0
Cheers,
--
Niko Tyni [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
