At 12:03 PM 02/27/2002, Ryan Bloom wrote: > > On Wed, Feb 27, 2002 at 04:44:03PM +0000, Thom May wrote: > > However, that brings up a point: > > > > Can we detect when a 1.3 module will be used with 2.0? One of my > > housemates was trying to install the PHP 1.3 module with 2.0.32 on > > Win32 last night. It just said as this bug does too: > > > > Cannot load E:/apache/Apache2/modules/ApacheModuleJServ.dll into > server: > > The specified module could not be found. > > > > Can we detect and report an suitable error message in this > > case? -- justin > >Yeah, that's actually trivial. The module structure has a key that >is the Apache version number. Look at MODULE_MAGIC_COOKIE. Just do >a quick comparison when we load the module, and output a valid error.
Not on Windows. You will not be able to even load the module. The LoadLibrary call will fail, since the module is linked against functions that don't exist. That is a standard system error message from using LoadLibrary to load a DLL when a required dependency doesn't exist. -- Greg Marr [EMAIL PROTECTED] "We thought you were dead." "I was, but I'm better now." - Sheridan, "The Summoning"
