Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 63143 invoked from network); 1 Dec 2005 23:48:47 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 1 Dec 2005 23:48:47 -0000 Received: (qmail 91971 invoked by uid 500); 1 Dec 2005 23:48:42 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 91920 invoked by uid 500); 1 Dec 2005 23:48:42 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 91909 invoked by uid 99); 1 Dec 2005 23:48:42 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Dec 2005 15:48:42 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [207.155.252.112] (HELO leander.cnchost.com) (207.155.252.112) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Dec 2005 15:50:08 -0800 Received: from [192.168.0.21] (c-24-13-128-132.hsd1.il.comcast.net [24.13.128.132]) by leander.cnchost.com id SAA02921; Thu, 1 Dec 2005 18:48:17 -0500 (EST) [ConcentricHost SMTP Relay 1.17] Errors-To: Message-ID: <438F8B68.1090109@rowe-clan.net> Date: Thu, 01 Dec 2005 17:46:48 -0600 From: "William A. Rowe, Jr." User-Agent: Mozilla Thunderbird 1.0.7-1.1.fc3 (X11/20050929) X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@httpd.apache.org Subject: Re: Win32 binary distributions 2.1.9-beta and onwards References: <434B64CC.5050806@rowe-clan.net> <438F7BD9.4030401@rowe-clan.net> <20051201230058.GA19392@dochas.stdlib.net> <438F84A5.1040008@rowe-clan.net> In-Reply-To: <438F84A5.1040008@rowe-clan.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N 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 ;-) Bill