cf-socket: drop feature check for IPV6_V6ONLY on Windows
#19769
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The macro is present in all supported Windows toolchains. It's present in mingw-w64 v3+, and in MS SDK 6.0A+ (possibly earlier). Note: It may not be supported by `USE_LWIPSOCK`. Follow-up to a28f5f6 curl#18010 Follow-up to ca3f6de curl#10975
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The macro is present in all supported Windows toolchains.
It's present in mingw-w64 v3+, and in MS SDK 6.0A+ (maybe earlier).
Also:
USE_WINSOCK(was:_WIN32), to excludealternate socket libraries (i.e. lwIP). lwIP supports
IPV6_V6ONLYsince its 2.0.0 (2016-11-10) release and it's disabled by default,
unlike in Winsock.
Ref: lwip-tcpip/lwip@e65202f
set_ipv6_v6only().Follow-up to a28f5f6 #18010
Follow-up to ca3f6de #10975