On May 8 22:05, Andrew Schulman wrote:
On May 8 15:23, Andrew Schulman wrote:
On Jan 20 03:45, Andrew Schulman wrote:
Cygwin doesn't seem to
define IPV6_DSTOPTS. In Ubuntu, it's defined in
/usr/include/linux/in6.h (value 59), along with a whole bunch of other
IPv6
To copy file1 to file2 on the localhost, run:
socat tcp6-listen: file2
to set up a listener, and:
socat tcp6:[::1]: file1
to connect to the listener and transfer the file.
If you have two hosts, you could try the same, running the first command
on the
On May 9 06:01, Andrew Schulman wrote:
To copy file1 to file2 on the localhost, run:
socat tcp6-listen: file2
to set up a listener, and:
socat tcp6:[::1]: file1
to connect to the listener and transfer the file.
If you have two hosts, you could try
2.0 works for me, too.
Thanks for testing.
--
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
On Jan 20 03:45, Andrew Schulman wrote:
Cygwin doesn't seem to
define IPV6_DSTOPTS. In Ubuntu, it's defined in
/usr/include/linux/in6.h (value 59), along with a whole bunch of other
IPv6 socket options.
I'm not sure what the best solution is here. I could define it locally,
but
On May 8 15:23, Andrew Schulman wrote:
On Jan 20 03:45, Andrew Schulman wrote:
Cygwin doesn't seem to
define IPV6_DSTOPTS. In Ubuntu, it's defined in
/usr/include/linux/in6.h (value 59), along with a whole bunch of other
IPv6 socket options.
I'm not sure what the best
On May 8 15:23, Andrew Schulman wrote:
On Jan 20 03:45, Andrew Schulman wrote:
Cygwin doesn't seem to
define IPV6_DSTOPTS. In Ubuntu, it's defined in
/usr/include/linux/in6.h (value 59), along with a whole bunch of other
IPv6 socket options.
I'm not sure what the
To copy file1 to file2 on the localhost, run:
socat tcp6-listen: file2
to set up a listener, and:
socat tcp6:[::1]: file1
to connect to the listener and transfer the file.
Note, this only works if file1 and file2 are absolute paths. If not
they have to be
Thanks. I added the ip6.h header nevertheless for the upcoming
Cygwin 1.7.28.
This seems to work fine for socat, but for socat-debuginfo 2.0.0-b6, the
build fails because IPV6_DSTOPTS is undefined. Cygwin doesn't seem to
define IPV6_DSTOPTS. In Ubuntu, it's defined in
On Jan 20 03:45, Andrew Schulman wrote:
Thanks. I added the ip6.h header nevertheless for the upcoming
Cygwin 1.7.28.
This seems to work fine for socat, but for socat-debuginfo 2.0.0-b6, the
build fails because IPV6_DSTOPTS is undefined.
I don't quite understand this. socat-debuginfo is
can you build socat with IPv6 support out of the box and it actually
works?
It did build and work just fine with the FreeBSD ip6.h file, with and
without the patch, but as I said, for all that socat uses the actual
ip6.h library, I could have put in a file empty except for the
On Jan 17 15:39, Aaron Humphrey wrote:
On Fri, Jan 17, 2014 at 3:19 PM, Corinna Vinschen wrote:
Our ipv6 stuff is in cygwin/in6.h, which is included by cygwin/in.h,
which in turn is included by netinet/in.h.
Ah, that explains it.
We could fetch FreeBSDs netinet/ip6.h. In contrast to
On Sat, Jan 18, 2014 at 12:47:51PM +0100, Corinna Vinschen wrote:
...I added the ip6.h header nevertheless for the upcoming Cygwin
1.7.28.
A new snapshot is building now. Should be ready soon.
cgf
--
Problem reports: http://cygwin.com/problems.html
FAQ:
On 1/17/2014 11:58, Aaron Humphrey wrote:
I had thought that cygwin 1.7 had IPv6 support,
It does, to the extent that the underlying Winsock APIs do. Basically,
you want to be on Vista or newer if you're going to depend on IPv6 under
Cygwin. IPv6 support for earlier versions of Windows was
On Fri, Jan 17, 2014 at 12:34 PM, Warren Young war...@etr-usa.com wrote:
On 1/17/2014 11:58, Aaron Humphrey wrote:
I had thought that cygwin 1.7 had IPv6 support,
It does, to the extent that the underlying Winsock APIs do. Basically, you
want to be on Vista or newer if you're going to
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,
On Fri, Jan 17, 2014 at 02:29:45PM -0700, Warren Young wrote:
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.
AUL. I like it.
cgf
--
Problem reports:
On Jan 17 16:32, Christopher Faylor wrote:
On Fri, Jan 17, 2014 at 02:29:45PM -0700, Warren Young wrote:
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.
AUL. I like it.
Our ipv6
On Fri, Jan 17, 2014 at 3:19 PM, Corinna Vinschen wrote:
Our ipv6 stuff is in cygwin/in6.h, which is included by cygwin/in.h,
which in turn is included by netinet/in.h.
Ah, that explains it.
We could fetch FreeBSDs netinet/ip6.h. In contrast to Glibc's
netinet/ip6.h it does not include
19 matches
Mail list logo
