Sherm Pendley wrote: >> wondering if the mod_perl library was reinstalled with the new Apache >> (probably), which had some dynamic linking done, designed for perl 5.6.0 >> (or possibly vice-versa), and the updated copy got "out of sync" with >> the >> newer perl. > > > Of course it got out of synch - Apple's mod_perl is compiled against > Perl 5.6.0, but you've installed Perl 5.6.1. > > If you update Perl, you must update mod_perl as well. And, in both > cases, if you've installed them in the same location as the > Apple-installed versions, you'll inevitably run into trouble when (not > if) some future update from Apple overwrites your customized install.
Although I agree with you in concept. This was not an issue when upgrading from 5.6.1. I did not have to reinstall mod_perl at that time, and things worked fine. It was only when mod_perl was updated with the Apache update (latest Security update). I'm guessing that the update to 5.6.1 scanned and relinked the libraries. I would have hoped that Apple's updates would check to see if relinking is necessary. They do this for larger updates (such as Developer tools), where it's clear this is needed. This really does seem like an oversight in the Security Update, making the assumption that no one updated Perl. Apple could have really simplified things for their users if they checked for necessary relinking of the libraries when updating them. > This isn't an OS/X issue - you'll get the same results any time the > installed version of Perl is different from the one against which > mod_perl is linked, regardless of OS. True. Although it is specific to Apple's Update procedure that caused this problem. Especially since Apache isn't even listed as one of the things being updated in the update docuementation. Cheers, -Alex
