You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That would be wonderful, but I doubt POSIX-like socket API related fns like socket (PF_INET, SOCK_RAW, ...), setsockopt() and select() are portable enough in the world of WinAPI.
I guess @cygwin or @midipix would be a better choice for that.
I'm not an experienced C programmer, but from what I researched WinSock and POSIX sockets work in a similar manner - mainly because Windows sockets were originally based on code from BSD:
Although these proprietary BSD derivatives were largely superseded by the UNIX System V Release 4 and OSF/1 systems in the 1990s (both of which incorporated BSD code and are the basis of other modern Unix systems), later BSD releases provided a basis for several open source development projects, e.g. FreeBSD, OpenBSD, NetBSD, Darwin or PC-BSD, that are ongoing. These, in turn, have been incorporated in whole or in part in modern proprietary operating systems, e.g. the TCP/IP (IPv4 only) networking code in Microsoft Windows and most of the foundation of Apple's OS X and iOS.
Description / Steps to reproduce the issue
enable traceroute in inetutils MSYS2 package
Expected behavior
traceroute
Actual behavior
error: target not found
Verification
Windows Version
MSYS_NT-10.0-22631
Are you willing to submit a PR?
No response
The text was updated successfully, but these errors were encountered: