Out of curiosity. Is the ipv6 supposed to be working properly now?
Last time I updated, I noticed that remote operation was broken.
That is, Xlib was unable to connect to a remote system (I assume
it didn't work with internet sockets anymore, but unix domain sockets
still worked).
On Fri, 8 Aug 2003, Egbert Eich wrote:
> Mark Vojkovich writes:
> > Out of curiosity. Is the ipv6 supposed to be working properly now?
> > Last time I updated, I noticed that remote operation was broken.
> > That is, Xlib was unable to connect to a remote system (I assume
> > it didn't work
The path below will fix the problem that arises when running
a client on an inet4 only system over tcp with Xlib compiled
with inet6 support.
If noone objects I'll commit it.
Egbert.
Index: Xtranssock.c
===
RCS file: /home/eich/
Mark Vojkovich writes:
> On Fri, 8 Aug 2003, Egbert Eich wrote:
>
> > Mark Vojkovich writes:
> > > Out of curiosity. Is the ipv6 supposed to be working properly now?
> > > Last time I updated, I noticed that remote operation was broken.
> > > That is, Xlib was unable to connect to a re
Egbert Eich wrote:
Mark Vojkovich writes:
> Out of curiosity. Is the ipv6 supposed to be working properly now?
> Last time I updated, I noticed that remote operation was broken.
> That is, Xlib was unable to connect to a remote system (I assume
> it didn't work with internet sockets anymore,
Mark Vojkovich writes:
> Out of curiosity. Is the ipv6 supposed to be working properly now?
> Last time I updated, I noticed that remote operation was broken.
> That is, Xlib was unable to connect to a remote system (I assume
> it didn't work with internet sockets anymore, but unix domain so
