This is the mail archive of the
mailing list for the Cygwin project.
Re: cygipc packaging was Updated setup.ini with descriptions, categories, and dependencies
- To: Ralf Habacker <Ralf dot Habacker at freenet dot de>
- Subject: Re: cygipc packaging was Updated setup.ini with descriptions, categories, and dependencies
- From: Charles Wilson <cwilson at ece dot gatech dot edu>
- Date: Mon, 03 Sep 2001 10:50:20 -0400
- CC: Cygwin-Apps <cygwin-apps at cygwin dot com>
- References: <001501c13484$968c9e90$651c440a@BRAMSCHE>
Ralf Habacker wrote:
>>You also need some "system calls". In linux, these are handled by the
>>kernel. In cygipc, these are split between ipc-daemon (which implements
>>some stuff itself, or calls on the Win32 low-level IPC stuff), and the
>>client library libcygipc.a.
> You write about Win32 low-level IPC: Could this not be used for creating an ipc
> deamon ?
Right -- and they are used in ipc-daemon and libcygipc. However, as
usual, Microsoft did not follow the POSIX standard interface for IPC
stuff. They windows-ized everything. We have to write wrappers around
the low-level Win32 calls so that they look POSIX. (Worse, it's not
really a one-to-one mapping. There's other weirdness).
>>aside; yeah, I've been desperately trying to contact Paul but he's not
>>returning my email. There's a BIG bug in binutils that I can't fix, in
>>ADDITION to the memory leak that's causing you <ralf> so much trouble.
> He don't answer any mail I have send too although he ask me to help him to get
> this feature running two month ago.
Paul "reappeared" in early August, but he's dropped out of sight again.
He wrote on the mingw-dvpr mailing list on August, 4 2001:
"I would like to greet you after more or less sizable break. since the
beginning of summer, I stayed in the other city, studying and being on
vacation. I've got a short recess for reading backlog of email before
leaving for another academic course. I'm going to pursue that kind of
activity - academic and job - also for the near future."
I think we need to consider Paul MIA. Somebody's going to have to
REALLY dig in to the autoimport code and lick this bug -- it ain't gonna
>> So, IF (and it's a big if) we decide to
>>incorporate cygipc as a official-but-separate package(*), I will help
>>someone else get started, and then *that* person may contribute it.
>>(*) e.g. a cygipc package, distributed on the cygwin mirror system,
>>installable by setup.exe -- but not part of cygwin1.dll itself.
> So when nobody is found, the package stay as it is, and this means that it would
> not be integrated into cygwin. Is that right ?