CONFIGURE: ENET: Add more system headers in checks #4778
Merged
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
They mostly come from OpenBSD 7.2 and Debian 11 manual pages, and they shouldn't hurt since backends/networking/enet/source/unix.cpp already includes them.
|
Thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 new ENet stuff checks for various system calls, but some systems may want some additional system headers for the checks to succeed.
The additions mostly come from OpenBSD 7.2 (https://man.openbsd.org) and Debian 11 manual pages, and they shouldn't hurt since
backends/networking/enet/source/unix.cppalready includes those headers.OK?