This is the mail archive of the
mailing list for the Cygwin project.
Re: HEADSUP: cygserver now has MSG, SEM and SHM support
- From: Harold L Hunt II <huntharo at msu dot edu>
- To: cygwin-apps at cygwin dot com
- Date: Wed, 26 Nov 2003 19:40:25 -0500
- Subject: Re: HEADSUP: cygserver now has MSG, SEM and SHM support
- References: <20031126111058.GE21540@cygbert.vinschen.de>
Corinna Vinschen wrote:
This means, not too far from now, we can drop the cygipc package and
packages like postgresql can switch to using Cygserver.
Additionally, most XFree86-* packages and anything that depends upon
XFree86-bin or XFree86-base (cgoban, emacs-X11, ghostscript-x11, grace,
gv, and tetex-x11).
In future, Cygwin releases will be build with Cygserver support switched
on. Clients, which want to access the Cygserver capabilities, have to
run with the environment variable CYGWIN set so that it contains the
word "server". I guess this will be the default at some later point.
So, there is no "cygserver" package... it will just be part of
cygwin1.dll? Is that correct? Excuse me for not following development
until now... it really hasn't affected me until today.
The cygserver directory also contains a README file which describes
Where is this cygserver directory? Are you referring to the CVS tree
However, I'd like to ask maintainers of affected packages to give
Cygserver a try. You will have to rebuild your packages and you
should make sure that the Cygwin header files sys/ipc.h, sys/msg.h,
sys/sem.h and sys/shm.h overwrote the cygipc files before building
your package(s). And don't link against libcygipc ;-)
Sounds like we are going to have to have a flag day for Cygwin/X and all
related packages to remove the link to cygipc and use the built-in SHM
support provided by cygserver. That is not really a problem for me, and
I know more about package maintanence now so it should be easier this