Fix FreeBSD 13.5 build error - Using s6_addr struct#57
Open
devnull-hub-lab wants to merge 1 commit into
Open
Conversation
|
this would be helpful for other operating systems. I just reluctantly merged the s6_addr32 exposure to userland for MidnightBSD but the current release does not have it. |
cgzones
approved these changes
Feb 15, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Using s6_addr struct, in compliance with RFC 2553 and 3493 – also POSIX 1003.1-2017
This solves build issues on FreeBSD 13.5
In FreeBSD < 14.1, the 's6_addr32' structure inside /usr/include/netinet6/in6.h is not exposed to userland.
So, its safe to use s6_addr instead (s6_addr is the only in6_addr element specified in RFC 2553 and 3493 – also POSIX 1003.1-2017)