Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-Id: <199911091904.OAA15801@dagda.sunflower.com> From: "Doug Wyatt" To: "'Cygwin mailing list'" Date: Tue, 9 Nov 1999 14:05:48 -0600 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Building cygwin32_ipc-1.03 for v1.0 - questions about v1 Reply-to: dwyatt AT sunflower DOT com X-mailer: Pegasus Mail for Win32 (v3.12a) Hi, I just built the Cygwin IPC package under the v1.0 release. In the process I found it required wintypes.h, which was not included in the v1 CD pkg. I extracted the file from the tgz of my former b20.1 setup and with that the build was able to complete. Why is the v1 release so divergent from b20.1 development - e.g. - different set of includes, fairly non-standard directory structure, etc., Are there any plans for formal patches, updates or new releases following up on v1.0? Even under some kind of paid support plan? Can the use of the registry be modified to allow coexistence of v1.0 and a development (b20.1 - b21) installation at the same time? It seems at the moment you can only have one or the other operational at one time by reconfiguring the (single) registry mount table. A "[/whatever]/etc/fstab" file might be a good thing to tie the registry entries to. Oh, and one other thing - why no man2 entries? Questions, questions, so full of questions ... it's been a long morning. Regards, Doug Wyatt ========================================================== Doug Wyatt E-Mail: dwyatt AT sunflower DOT com Sys Admin Phone: 785-843-4099 Kohlman Systems Research, Inc. Fax: 785-843-6459 319 Perry St., Lawrence, KS 66044 USA -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com