Bug 50390

Summary: WARNING: Unrecognized options : --disable-ipv6
Product: Apache httpd-2 Reporter: Kuniaki Shimizu <kunkichi>
Component: BuildAssignee: Apache HTTPD Bugs Mailing List <bugs>
Status: NEW ---    
Severity: normal    
Priority: P2    
Version: 2.0.64   
Target Milestone: ---   
Hardware: Sun   
OS: Solaris   

Description Kuniaki Shimizu 2010-11-30 22:18:39 UTC
OS : Solaris10 Sparc

For 2.0.64, configure says --disable-ipv6 is "unrecognized options".

[2.0.64]
$ ./configure --prefix=/usr/local/apache --disable-ipv6
configure: WARNING: unrecognized options: --disable-ipv6
・・・
Checking for IPv6 Networking support...
checking for library containing getaddrinfo... none required
checking for library containing gai_strerror... none required
checking for library containing getnameinfo... none required
checking for gai_strerror... yes
checking for working getaddrinfo... yes
checking for negative error codes for getaddrinfo... no
checking for working getnameinfo... yes
checking for sockaddr_in6... yes
checking if APR supports IPv6... no -- disabled by user
・・・
configure: WARNING: unrecognized options: --disable-ipv6
$ 

For 2.0.63, no warnings.

[2.0.63]
$ ./configure --prefix=/usr/local/apache --disable-ipv6
・・・
Checking for IPv6 Networking support...
checking for library containing getaddrinfo... none required
checking for library containing gai_strerror... none required
checking for library containing getnameinfo... none required
checking for gai_strerror... yes
checking for working getaddrinfo... yes
checking for negative error codes for getaddrinfo... no
checking for working getnameinfo... yes
checking for sockaddr_in6... yes
checking if APR supports IPv6... no -- disabled by user
・・・・
$

It seems --disable-ipv6 works. Actually, after ./configure, 
compile has suceeded and I've tried a few small tests and looks good.

This looks same as Bug 45221, then I've tried installing latest
autoconf, ./buildconf, ./configure again, but nothing has changed,
./configure still says warning.

--disable-ipv6 is still valid option? 
If so, this warnings is harmless and ignorable?