Fix Windows/MSYS2/MinGW64 build failures (issue #280) #355
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.
Summary
Fixes #280 - Users on MSYS2/MinGW64 get build failures when running configure from the wrong shell.
Root cause: MSYS2 has multiple shells with different host triplets:
x86_64-pc-msys- Does NOT match*-mingw*patternx86_64-w64-mingw32- Matches*-mingw*patternWhen users run configure from the MSYS shell (default), it falls through to the Unix case, looking for
arpa/inet.hinstead ofwinsock2.h.Changes:
*-msys*case in configure.ac with Windows headers/libraries and a warning about msys-2.0.dll dependencyTest plan