This is the mail archive of the
cygwin-xfree@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: X-server
- To: "Suhaib M. Siddiqi" <ssiddiqi@inspirepharm.com>
- Subject: Re: X-server
- From: Chris Faylor <cgf@cygnus.com>
- Date: Mon, 14 Jun 1999 18:59:46 -0400
- Cc: cygwin-xfree@sourceware.cygnus.com
- References: <000501beb5d6$f0b2c8b0$be84aad1@hunda>
Someone suggested trying to start up a client on your Windows machine
from a UNIX system. Have you tried that?
Also, I'm not sure, but it may be that 127.0.0.1 is not being
interpreted correctly as a host name. You can also try "localhost"
and/or the name of the Windows host or it's IP address.
-chris
On Sun, Jun 13, 1999 at 03:57:13PM -0400, Suhaib M. Siddiqi wrote:
>Please do not delete the XGGI.exe (X server executable) from
>pre-alpha-cygwin-xfree.tar.bz2. Simple rename it to something else, when installing
>the new one from pre-alpha-cygwin-xfree.patch.tar.bz2.
>
>I compiled the new XGGI.exe with -DUNIXCONN and according to Sergey and Chris
>Faylor the UNIX Domain connection protocol is not going work. My mistake.
>
>I just tried using the the libX11.dll from the new patch but the XGGI.exe
>from pre-alpha-cygwin-xfree.tar.bz2 (older one which was compiled only with -DTCPCONN flag, I get a different failure error messages 9paster below:
>
>I guess we need to figure out what the configuration problems are;
>
>PGI$ bash xggi.bash
>LibGII: Debugging=255
>LibGGI: Debugging=255
>LibGGI: ggiOpen("127.0.0.1:0") called
>LibGGI: Loading driver 127.0.0.1:0
>LibGGI: _ggiAddDL(0x10071130, "127.0.0.1", "0", 0x1) called
>LibGGI: LibGGI: no config entry for sublib: 127.0.0.1
>LibGGI: ggiOpen: failure
>
>Fatal server error:
>Unable to open LibGGI visual: "127.0.0.1:0"
>
>LibGGI: ggiExit called
>LibGGI: ggiExit: really destroying.
>LibGII: giiExit() called
>LibGII: giiExit: really destroying.
>LibGII: giiExit: done!
>LibGGI: ggiExit: done!
>PGI$ XIO: fatal IO error 104 (Connection reset by peer) on X server "127.0.0.1:
>0.0"
> after 0 requests (0 known processed) with 0 events remaining.
>_X11TransSocketINETConnect: Can't connect: errno = 111
>_X11TransSocketINETConnect: Can't connect: errno = 111
>_X11TransSocketINETConnect: Can't connect: errno = 111
>_X11TransSocketINETConnect: Can't connect: errno = 111
>_X11TransSocketINETConnect: Can't connect: errno = 111
>_X11TransSocketINETConnect: Can't connect: errno = 111
>xmodmap: unable to open display '127.0.0.1:0.0'
- Follow-Ups:
- Re: X-server
- From: "Suhaib M. Siddiqi" <Ssiddiqi@InspirePharm.Com>
- Re: X-server
- From: "Suhaib M. Siddiqi" <Ssiddiqi@InspirePharm.Com>
- References:
- X-server
- From: "Suhaib M. Siddiqi" <ssiddiqi@inspirepharm.com>
- X-server
- From: "Suhaib M. Siddiqi" <ssiddiqi@inspirepharm.com>