Chris Devers wrote: >>>But isn't it supposed to not work unless it offers error messages? >>> >>You would think so >> > >I was having fun with the [snipped] double negative earlier... :) >
Yeah, I kinda figured... just covering the bases. ;) >>Well, the thing is, I don't think it even gets that far in executing the >>conf file. >> > >You think? Or you know? What does "apachectl configtest" tell you? > Well, the syntax checking will fail if you don't have the LoadModule. However, if the LoadModule line is present, that will pass, the conf will load, compile, and execute... However, it didn't make it to the point past the LoadModule line. The invalid linking of libraries to the updated Perl probably made the whole process up and die. The most disturbing thing though is that there's absolutely no error messages. Only the normal startup log entries, ending just before the ones that would normally appear for the loading of mod_perl. >As mentioned later in this thread, the problem is very likely to be that >Perl and mod_perl are out of sync, and that they'll only work is built >against the same version. If you upgrade Perl, you need to do the same for >mod_perl. Downgrading back to 5.6.0 brought them back into sync. > Yeah.... I was the one that originally mentioned it. :) The problem of linking occured to me when I started to think more thoroughly what occurs with Apple's updates. So, I decided to test that theory. I'm sure upgrading back to 5.6.1 would work again. Oddly, I didn't need to recompile mod_perl when I first updated Perl and things were fine. I wonder if the Perl compile/installation does the relinking for things that were dependent on it (would be a good thing, making things simple, and catching everything). >Again, I think this is a general mod_perl issue, and not OSX related -- >any time you make a system change like that it can disturb linkages, and >that's exactly what you're seeing here... > Can, but doesn't always. In other updates from Apple where linking mismatches are more clear, the update relinked the libraries. Apparently this wasn't the case here. Since Apple has taken it upon themselves to hide the update process (definitely a good thing for ease of use), it seems they should also think about what happens when libraries are updated and handle it. Yes, I know that I can manually pick apart the update, if I manually downloaded it (did that), but it shouldn't be necessary. It can't be THAT uncommon that people do CPAN module installs, which can often result in an automatic update of Perl. In light of that, I would hope that Apple would take into consideration that possibility with future updates. Cheers, -Alex >
