Using Apache 2.2 from ApacheLounge for Win32 modperl
Hi all, While ApacheLounge makes available a Win32 binary of Apache2.2 that seems to work better for modperl than the distribution from apache.com, be advised that if you intend to use libapreq2, you may not want to use the mod_perl binary from ApacheLounge. I don't have the technical details, but if you try to use ApacheLounge's mod_perl and theoryx5's libapreq, you will not be able to use Apache2::Reload at the very least. For some reason, the MSI version of ActivePerl (tested with build 822) is more stable than the AS version in terms of starting up httpd on system startup, and service restarts. So please avoid the latter. My recommendation: 1. Use the Apache2.2.x binary from ApacheLounge 2. Use the MSI version of ActivePerl, NOT the AS version 3. Use the mod_perl library from theoryx5, NOT from ApacheLounge 4. Use the libapreq2 library from theoryx5 Tested on Windows XP SP2 x86
Re: Using Apache 2.2 from ApacheLounge for Win32 modperl
On Sun, 19 Aug 2007, Foo JH wrote: Hi all, While ApacheLounge makes available a Win32 binary of Apache2.2 that seems to work better for modperl than the distribution from apache.com, be advised that if you intend to use libapreq2, you may not want to use the mod_perl binary from ApacheLounge. I don't have the technical details, but if you try to use ApacheLounge's mod_perl and theoryx5's libapreq, you will not be able to use Apache2::Reload at the very least. For some reason, the MSI version of ActivePerl (tested with build 822) is more stable than the AS version in terms of starting up httpd on system startup, and service restarts. So please avoid the latter. My recommendation: 1. Use the Apache2.2.x binary from ApacheLounge 2. Use the MSI version of ActivePerl, NOT the AS version 3. Use the mod_perl library from theoryx5, NOT from ApacheLounge 4. Use the libapreq2 library from theoryx5 Tested on Windows XP SP2 x86 This might be a result of what was mentioned before about possible problems using the binaries from http://www.apachelounge.com/download/ (which is compiled with VC++ 2005) with ActivePerl and ActivePerl-compatible ppm packages (which are compiled with VC++ 6). Mixing these can lead to conflicts, as discussed at, eg, http://search.cpan.org/src/SHAY/Win32-UTCFileTime-1.46/INSTALL Also, note that the apache-2.2.5 release available from http://www.apachelounge.com/download/ is based on sources which have not officially been released by the ASF: http://marc.info/?l=apache-httpd-dev&m=118747498301087&w=2 -- best regards, Randy
Re: Using Apache 2.2 from ApacheLounge for Win32 modperl
Randy Kobes wrote: > On Sun, 19 Aug 2007, Foo JH wrote: >> >> My recommendation: >> 1. Use the Apache2.2.x binary from ApacheLounge >> 2. Use the MSI version of ActivePerl, NOT the AS version >> 3. Use the mod_perl library from theoryx5, NOT from ApacheLounge >> 4. Use the libapreq2 library from theoryx5 >> >> Tested on Windows XP SP2 x86 > > This might be a result of what was mentioned before about possible > problems using the binaries from http://www.apachelounge.com/download/ > (which is compiled with VC++ 2005) with ActivePerl and > ActivePerl-compatible ppm packages (which are compiled with VC++ 6). > Mixing these can lead to conflicts, as discussed at, eg, > http://search.cpan.org/src/SHAY/Win32-UTCFileTime-1.46/INSTALL This is the primary reason that Apache 2.0 and 2.2 ship based on VC 6 builds. In order to maintain binary compatibility, they depend on the more reliable (at that time) VC 6 C Runtime. I wouldn't mix and match at all. Expect from one provider a solid set of binaries, either all VC 6 as found from AS and the ASF. Or entirely use another vendors build entirely built with VC 2005. Either way, if you mix and match you will find surprises. > Also, note that the apache-2.2.5 release available from > http://www.apachelounge.com/download/ is based on sources > which have not officially been released by the ASF: > http://marc.info/?l=apache-httpd-dev&m=118747498301087&w=2 Actually note that it isn't a release and is being rerolled. Seems Apachelounge is doing themselves and their users a disservice, again. You'll be keeping your eye out for a 2.2.6 (or later in the event of some calamity with that reroll). Bill
Re: Using Apache 2.2 from ApacheLounge for Win32 modperl
Actually note that it isn't a release and is being rerolled. Seems Apachelounge is doing themselves and their users a disservice, again. I disagree. ApacheLounge's binary distribution is the only one that (configured with modperl) survives an application restart. As I posted in an earlier mail, ASF's binaries do not work in modperl setups. So far I have not received any response (only verifications) that contradict my findings. I applaud the people who put in effort (AND maintain a web site for that) to fix a long-standing problem, and share it with the professionals at large. It's a lot of work, and it takes a great spirit to think for the rest of us code compiler noobs.
Re: Using Apache 2.2 from ApacheLounge for Win32 modperl
This might be a result of what was mentioned before about possible problems using the binaries from http://www.apachelounge.com/download/ (which is compiled with VC++ 2005) with ActivePerl and ActivePerl-compatible ppm packages (which are compiled with VC++ 6). Mixing these can lead to conflicts, as discussed at, eg, http://search.cpan.org/src/SHAY/Win32-UTCFileTime-1.46/INSTALL You're probably right. The only saving grace is the Apache binaries seem to be nicely decoupled from the modperl/ libapreq2 code. I have not had much issues marrying them together. The only thorn I'm dealing with is that spaces in directory names is not good. But I can live with that.
Re: Using Apache 2.2 from ApacheLounge for Win32 modperl
On Mon, 20 Aug 2007, Foo JH wrote: Actually note that it isn't a release and is being rerolled. Seems Apachelounge is doing themselves and their users a disservice, again. I disagree. ApacheLounge's binary distribution is the only one that (configured with modperl) survives an application restart. As I posted in an earlier mail, ASF's binaries do not work in modperl setups. So far I have not received any response (only verifications) that contradict my findings. I applaud the people who put in effort (AND maintain a web site for that) to fix a long-standing problem, and share it with the professionals at large. It's a lot of work, and it takes a great spirit to think for the rest of us code compiler noobs. There wasn't a quarrel with ApacheLounge providing binary distributions in general, and indeed, this is encouraged in the broad community within the guidelines of the Apache Software Foundation (ASF). The specific issue here was that there was a binary distribution available on the ApacheLounge site (which has since been removed) which wasn't marked very clearly as being built from sources of an ASF release candidate, which are intended for testing only. -- best regards, Randy