Closed john-tornblom closed 2 years ago
The socket options for Linux and BSD use different values for, e.g., SO_REUSEADDR, which in turn cause setsockopt to behave incorrectly.
musl: #define SO_REUSEADDR 2 freebsd: #define SO_REUSEADDR 0x0004
Should be fixed in: https://github.com/OpenOrbis/musl/commit/091e9f0d5d9ab5a5535ddb9cfbb85ea665d5afcc
The socket options for Linux and BSD use different values for, e.g., SO_REUSEADDR, which in turn cause setsockopt to behave incorrectly.
musl: #define SO_REUSEADDR 2 freebsd: #define SO_REUSEADDR 0x0004