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 From: "Dave Korn" To: Subject: RE: Inconsistent behavior for Win32 executable: starting from bashvs. starting from cmd.exe Date: Mon, 11 Jul 2005 18:16:17 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit In-Reply-To: Message-ID: ----Original Message---- >From: Ljubomir Milanovic >Sent: 11 July 2005 17:20 > address error was result (surprise, surprise :). After few trial/error > cycles the fix was to add ClearCase bin directory to the PATH under > cygwin !!! Don't ask me why. Because ClearCase carries its own version of cygwin1.dll with it (http://cygwin.com/acronyms#3PP) and it is interfering with your cygwin installation in some as-yet-unclear fashion to do with mixing incompatible versions of the dll and the tools, most likely. > My PATH under windows is huge, and I redefined windows PATH in > cygwin to avoid too long "search" times, e.g. if pressing TAB at empty > line and similar. You can interrupt the tab-completion if you accidentally press it on an empty line by Ctrl-C. > However, as my problem shows, this praxis has some risks. Yes, but you still haven't yet got the correct solution. If adding clearcase into your path makes things work again, it would suggest you were using the clearcase version of cygwin dll instead of the one in your cygwin dir all along. Of course, if you'd followed the instructions at http://cygwin.com/problems.html, we would probably have been able to tell you this straight away.... 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/