Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Message-ID: <44B67708.5080802@ptc.com>
Date: Thu, 13 Jul 2006 11:38:32 -0500
From: Jess Holle <jessh@ptc.com>
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version: 1.0
To: dev@httpd.apache.org
CC: Jorge Schrauwen <jorge.schrauwen@gmail.com>,
 "Fenlason, Josh" <jfenlason@ptc.com>
Subject: Re: IPV6 enabled on supplied Windows 32 binary?
References: <C3BBBDFBE6D92C4EAA62BBE9793DECCF7702B2@MERCMBX07.na.sas.com>
 <44B66B03.1040404@ptc.com> <20060713160118.GA32321@dochas.stdlib.net>
In-Reply-To: <20060713160118.GA32321@dochas.stdlib.net>
Content-Type: multipart/alternative;
 boundary="------------040101060503000605020604"

This is a multi-part message in MIME format.
--------------040101060503000605020604
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit

Colm MacCarthaigh wrote:
> On Thu, Jul 13, 2006 at 10:47:15AM -0500, Jess Holle wrote:
>   
>> So what's the story with IPv6 on Windows?
>>     
> Works fine in every version of windows since 2000, although 2000 itself
> needs a kit and patching installed.
>   
Great.  That covers all versions of Windows my employer cares about, so 
we can build our Apache with IPv6 always enabled.
>> Are there some versions of Windows which always support it, but the 
>> headers we use for Windows don't detect this at build time?
>>     
> We don't use an autoconf-like system on Windows, so although we could
> detect this at build time, it's just something which has been left as a
> build option.
>   
I knew that but was wondering if there was some #if magic based on OS 
level defines instead.  I can see why there is not, though -- that would 
result in requiring an older OS to build an Apache that is compatible 
with the older OS.
>> We bundle our own Apache builds for a number of Windows OS levels and 
>> have customers who really want IPv6...  I don't want to break anything 
>> for the rest of the customers, though.
>>     
> That's at your own risk :-)
>   
Obviously :-)

By "break anything" I meant that it should still work despite the fact 
that they're actually only using IPv4, etc -- not that this would not 
uncover a bug -- which is always a risk.

--
Jess Holle


--------------040101060503000605020604
Content-Type: text/html; charset=ISO-8859-15
Content-Transfer-Encoding: 8bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-15"
 http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Colm MacCarthaigh wrote:
<blockquote cite="mid20060713160118.GA32321@dochas.stdlib.net"
 type="cite">
  <pre wrap="">On Thu, Jul 13, 2006 at 10:47:15AM -0500, Jess Holle wrote:
  </pre>
  <blockquote type="cite">
    <pre wrap="">So what's the story with IPv6 on Windows?
    </pre>
  </blockquote>
  <pre wrap=""><!---->Works fine in every version of windows since 2000, although 2000 itself
needs a kit and patching installed.
  </pre>
</blockquote>
Great.� That covers all versions of Windows my employer cares about, so
we can build our Apache with IPv6 always enabled.<br>
<blockquote cite="mid20060713160118.GA32321@dochas.stdlib.net"
 type="cite">
  <blockquote type="cite">
    <pre wrap="">Are there some versions of Windows which always support it, but the 
headers we use for Windows don't detect this at build time?
    </pre>
  </blockquote>
  <pre wrap=""><!---->We don't use an autoconf-like system on Windows, so although we could
detect this at build time, it's just something which has been left as a
build option.
  </pre>
</blockquote>
I knew that but was wondering if there was some #if magic based on OS
level defines instead.� I can see why there is not, though -- that
would result in requiring an older OS to build an Apache that is
compatible with the older OS.<br>
<blockquote cite="mid20060713160118.GA32321@dochas.stdlib.net"
 type="cite">
  <blockquote type="cite">
    <pre wrap="">We bundle our own Apache builds for a number of Windows OS levels and 
have customers who really want IPv6...  I don't want to break anything 
for the rest of the customers, though.
    </pre>
  </blockquote>
  <pre wrap="">That's at your own risk :-)
  </pre>
</blockquote>
Obviously :-)<br>
<br>
By "break anything" I meant that it should still work despite the fact
that they're actually only using IPv4, etc -- not that this would not
uncover a bug -- which is always a risk.<br>
<br>
--<br>
Jess Holle<br>
<br>
<br>
</body>
</html>

--------------040101060503000605020604--