This is the mail archive of the
cygwin-xfree@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: X-server
- To: Chris Faylor <cgf@cygnus.com>
- Subject: Re: X-server
- From: "Suhaib M. Siddiqi" <Ssiddiqi@InspirePharm.Com>
- Date: Mon, 14 Jun 1999 21:15:12 -0400 (EDT)
- Cc: cygwin-xfree@sourceware.cygnus.com
- Organization: Inspire Pharmaceuticals, Inc
- Reply-To: Ssiddiqi@InspirePharm.Com
>>
>>supposed to be (as on Linux)
>>LibGGI has X Display on 127.0.0.1:0.0
>>libGGI X Screen open on 127.0.0.1:0.0
>
> I dunno. This sounds like the X server is not properly connecting
> before libGGI gets to it. That doesn't sound like a libGGI problem.
>
> -chris
You could be right. John Fortin is building a debug version and I also doing
the same. I am hopefull; we will fix the problem.
Oh, one question, what is the difference between sys/socket.h and
cygwin/socket.h?
In xc/programs/Xserver/os/connection.c we have
#ifndef WIN32
#include <sys/socket.h>
When I changed it to
#include <cygwin/socket.h>
I get 100s of errors.
The header file in cygwin/socket.h looks more like the one on Linux
therefore I changed it back to <sys/socket.h>
and added an extra line
#ifdef __CYGWIN__
#include <cygwin/socket.h>
Doing that compilation of OS dependent libos.a went smooth.
Does it matter if sys/socket.h and cygwin/socket.h both as used as I did?
Suhaib