Swiftdiff options
| author | Tobias Markmann <tm@ayena.de> | 2015-02-01 15:33:39 (GMT) |
|---|---|---|
| committer | Tobias Markmann <tm@ayena.de> | 2015-02-02 14:37:41 (GMT) |
| commit | d860805af76ec85e003bf3019407bbb7acd218c9 (patch) | |
| tree | b83b63fe025f1e57f1b9bf2b7bc6863c665f3bb6 /3rdParty/Boost/src/boost/thread/win32/interlocked_read.hpp | |
| parent | 22ad0360bb273c62af4e5a2106f4e87c1b4fa3ac (diff) | |
| download | swift-d860805af76ec85e003bf3019407bbb7acd218c9.zip swift-d860805af76ec85e003bf3019407bbb7acd218c9.tar.bz2 | |
Fix IPv6 name resolution on Linux systems
Boost query objects are setup with the flag address_configured by
default which only does IPv6 resoltuion if a non-loopback device is
found. This detection mechanism does not seem to work. At least in my
test VM there was a non-loopback device with IPv6 address and it still
reported no IPv6 addresses. Setting the flag to passive will
have it always send queries for AAAA records.
Test-Informatioon:
Tested on Mac OS X 10.9.5 and Elementary OS 0.2.1 (Linux).
Change-Id: I346bcb7982dee465aa7847a7bae8981a16f2d3bc
Diffstat (limited to '3rdParty/Boost/src/boost/thread/win32/interlocked_read.hpp')
0 files changed, 0 insertions, 0 deletions