Bug 50390

Summary:	WARNING: Unrecognized options : --disable-ipv6
Product:	Apache httpd-2	Reporter:	Kuniaki Shimizu <kunkichi>
Component:	Build	Assignee:	Apache HTTPD Bugs Mailing List <bugs>
Status:	RESOLVED LATER
Severity:	normal	Keywords:	MassUpdate
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?

Comment 1 William A. Rowe Jr. 2018-11-07 21:10:00 UTC

Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd.

As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd.

If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question.

If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with.

Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.