httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William A. Rowe, Jr." <>
Subject Re: Win32 binary distributions 2.1.9-beta and onwards
Date Thu, 01 Dec 2005 23:46:48 GMT
William A. Rowe, Jr. wrote:
> Colm MacCarthaigh wrote:
>> On Thu, Dec 01, 2005 at 04:40:25PM -0600, William A. Rowe, Jr. wrote:
>>> I have 6.0, 2000/.NET, 2003, and 2005 sitting here, and will build 
>>> whichever
>>> flavor is deemed 'appropriate'.
>>> If nobody speaks up, I'm building 'same old, same old' under MSVCRT.
>> I think that's appropriate, 2005 is a bit of a battle right now. Getting
>> openssl to compile with 2005 is a real nightmare (more than usual).
> If this too shall pass, I'm in favor of 'doing it right' for the long term,
> 2.2 will be here a while.  Raising some questions beyond the httpd 
> community
> with an eye to the official binary sometime early next week, prior to 
> hackathon.

Ok, on further consideration, if Joe casual user has the opportunity to open
up the project in their free edition of VisualStudio 2005, and learn Apache,
perhaps contribute back, I believe *we* win, and the user wins.

That said, I'm inquiring of the ActiveState staff about their tools, where are
they going to be in the next month or few?  Not endorsing them, but they are
one of several valid solutions.

We push our module authors to whatever we build to, if they are doing anything
fancy with freeing resources in a different context than they were allocated
(either passing off resource ownership to us from their module, or surrendering
our ownership to their module as a raw resource.)  APR makes almost all of these
a no-op, and in fact mod_aspdotnet uses VC 2000, soon to be 2005, because it
never trades ownership of resources this way.

But language blending, al la mod_python or mod_perl, is an entirely different
beast, these things will be passed back and forth, and will cause hassles.  So
httpd is somewhat dependent upon other organizations which distribute win32
ported languages compiled in MSVC.

As far as OpenSSL etc, nothing says those can't be patched and we are up and
running again quickly, in fact they'd broken their shared build on HPUX and
that's where I'm currently spending my patience.  After that, proposing the
fix for VS2005 should be a no-brainer ;-)


View raw message