At 11:34 AM 5/17/2001 -0400, Ed James, 410-295-1919,
[EMAIL PROTECTED] wrote:
>Hello all,
>
>I'm a little confused about the "binary compatability" of perl.
>
>I have 5.6.1 installed on VMS 7.1-1H1 and Solaris 2.8 with "-des" and
>with the same dynamic modules installed on both. The VMS system does
>have most of the VMS modules (Stdio, Device, Process, etc.) installed.
>
>I want to re-compile both perls with -DDEBUGGING.
FWIW, that's the default on VMS unless you chose otherwise.
>Will this require the re-install of all the dynamic modules?
Generally yes. Definitely on VMS.
VMS builds aren't cross-version compatible. They're not cross-option
compatible. Heck, by default they're not cross-compilation compatible.
(Perl's all shared images, and unless you set the PERLSHR_USE_GSMATCH
logical, we don't set the major or minor IDs, nor the gsmatch option)
>What causes a "binary in-compatability"?
Changes to anything that affects the source that XS modules import (like
all of perl's zillion macros) or the signature of the functions.
>Is this described anywhere?
Not that I can think of. There's a declaration that you're compatible
between builds if you select identical options, otherwise all bets are off.
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
