X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org From: "Dave Korn" To: References: <20080804233810.GA13054@ednor.casa.cgf.cx> Subject: RE: Does anyone use insight on cygwin? Date: Wed, 6 Aug 2008 19:04:28 +0100 Message-ID: <001a01c8f7ee$de8feaf0$9601a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Brian Keener wrote on 06 August 2008 18:42: > Let me change my previous response please The moving hand writes, and having writ moves on .... ;-) > version would be great - if possible. Especially now that I found my > issue - my debug version of Cygwin1.dll (self compiled) apparently > broke Insight and/or Tcl/Tk because as soon as I changed back to a > released Cygwin1.dll - Insight started working again from bash. Are you /entirely/ sure you didn't accidentally leave a service running or a shell or something or somehow end up with two clashing DLLs at the same time? Unless you've been making changes to the source code, any self-build DLL ought to be just as good as one from upstream. cheers, DaveK -- Can't think of a witty .sigline today.... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/