This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: socat with IP6 support?
- From: Warren Young <warren at etr-usa dot com>
- To: Cygwin-L <cygwin at cygwin dot com>
- Date: Fri, 17 Jan 2014 14:29:45 -0700
- Subject: Re: socat with IP6 support?
- Authentication-results: sourceware.org; auth=none
- References: <CAF+jOM1XK9d36w+FdRtd2q35yirEaVb0p0wNyteuWru4zTGWrA at mail dot gmail dot com> <52D985D3 dot 9070506 at etr-usa dot com> <CAF+jOM3X96jE+2nXBbadstJf6ehKCk0ae9est+6wvX5G1VFupg at mail dot gmail dot com>
On 1/17/2014 13:45, Aaron Humphrey wrote:
So why does it think it
requires ip6.h if it compiles fine without it?
It's probably an unwarranted Linuxism. As I read POSIX[*], it is legal
to have IPv6 definitions in the same old headers the IPv4 interface is
defined in, as Cygwin does.
So, three choices:
1. Cygwin could add stub headers for these to placate socat and any
other software that uses their presence as an IPv6 test; or
2. Someone can lobby socat to fix their test; or
3. The socat package maintainer can patch the software before building
it. If it were me, I'd first try diddling config.h after the configure
script generates it, rather than hack the configure script itself. If
that works, it's a one-line fix.
[*] http://goo.gl/lMIJUK
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple