Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <3D23C4F5.7010403@ece.gatech.edu> Date: Wed, 03 Jul 2002 23:45:57 -0400 From: Charles Wilson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2 X-Accept-Language: en-us MIME-Version: 1.0 CC: cygwin AT cygwin DOT com Subject: [ANN] cygipc-1.12 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Given the changes in key_t's definition as of cygwin-1.3.11, I've relased a new version of cygipc, with some major changes. Because of the key_t change, one can no longer compile IPC programs if both cygipc-1.11 or older is installed, AND cygwin-1.3.11 or newer is installed -- they are incompatible. (However, programs that were PREVIOUSLY compiled, against cygwin-1.3.10 or older and the old cygipc's will continue to work properly even with new cygwin kernels). The daemon is now called ipc-daemon2.exe, so that it can coexist with the older cygipc daemon. The new daemon uses *different* files in /tmp. Old programs (that is, previously compiled) will continue to work -- but will use ipc-daemon.exe. Newly compiled programs will use ipc-daemon2.exe -- but you must compile with cygwin kernel 1.3.11 or newer. The point: old programs use ipc-daemon. new programs use ipc-daemon2. Both will RUN under any cygwin kernel (within reason) -- but if you're compiling, you must make sure your kernel and cygipc "match" -- old kernel, old cygipc; new kernel, new cygipc. See http://www.neuro.gatech.edu/users/cwilson/cygutils/cygipc/ --Chuck -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/