RE: [DBI] msvcrt.dll issues when running in an XP environment
"Andrew McLaren" <[email protected]>
| Newsgroups | gmane.comp.apache.mod-perl |
|---|---|
| Organization | Aratika NZ |
| Message-ID | <D8833438FF7B4AAABF7AD3913E18BF47@jupiter> |
Further to the earlier note, I have been and done the following; Replaced DBI, DBD-Pg and Log-Log4perl with the packages from theoryx5 (1.59, 1.45 and 1.06 respectively), which should all be compatible builds with the ASF Apache release. At this point httpd is starting successfully, but I'm immediately having a different problem with Postgre. This is not Apache related - a simple bit of standalone Perl to connect to a database crashes Perl with an exception on an unknown ModName. Not a lot of help there. I've reverted back to the pgfoundry 2.10 DBD-Pg package. This gives connectivity back to the database, but immediately starts giving the msvcrt.dll errors when running under Apache. At the moment I'm at a bit of a Catch 22. I can't totally verify that the theoryx5 packages have resolved the Apache problems, as the lack of a database connection limits what I can test. However, it does appear that this may have resolved that issue. However, this build of DBD-Pg appears to have other problems that prevent it working at all (and appears that these may be known issues with this version of DBD-Pg). As an alternative I've tried using ODBC to get to the database. The ODBC package works fine standalone, but also exhibits the msvcrt problems running under Apache. This is another package that I don't know the build history of, and there is no known consistent package available at theoryx5. I've just tried a 2.14 DBD-Pg package from trouchelle.com, but have no details of how this was constructed,, and this takes over and installs a heap of replacement dll's. This won't even start standalone, and I'm probably going to have to do a clean Perl install to recover from that. Still struggling Andrew