On Sat, 31 May 2008, Brendan O'Dea wrote:
> On Fri, May 16, 2008 at 10:31 PM, Andy Dougherty <[EMAIL PROTECTED]> wrote:
> > On Thu, 15 May 2008, Niko Tyni wrote:
> >> 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).
> > Changing 5.10.0's $Config{vendorarch} to include the string "5.10" (much
> > as is done for $Config{archlib} aleady) might solve this problem. Or at
> > least it might cause the failure to appear earlier and in a way that is
> > easier to trap gracefully.
>
> Not really. Adding a version into the path simply changes the failure
> from an issue loading the .so (module is unusable) to one where the
> module is not found at all (module is unusable).
Agreed. In neither case does it actually work. However, the case of not
finding the module at all is probably easier to trap at compile time.
Because of lazy symbol loading, loading the wrong version of the module
sometimes appears to work -- until you actually try to use it.
--
Andy Dougherty [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
