X-Spam-Check-By: sourceware.org
Message-ID: <439B0E6A.2AF737C9@dessent.net>
Date: Sat, 10 Dec 2005 09:20:42 -0800
From: Brian Dessent <brian AT dessent DOT net>
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: 1.5.18-1: issue with cygwin1.dll: "system shared memory version      mismatch detected"
References: <20051210165211 DOT 53675 DOT qmail AT web86809 DOT mail DOT ukl DOT yahoo DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

JeDi wrote:

> Sure Brian, but bash.exe is present nowhere but in my
> cygwin\bin directory, and bash doesn't work. I agree
> with you that my computer is kind of a mess but I
> don't think this is the root cause. Actually, i've set
> up my environment variable with cygwin\bin in the
> first position of my path and it doesn't change
> anything.

It's irrelevent what the name of the .exe is.  As Igor already said,
even if a third party packages a cygwin1.dll that has simply been
renamed, it will still have the same shared memory name, so that if the
two DLLs are ever loaded at the same time they will clash.  This is
exactly what the error message you're getting indicates -- that you have
two incompatible Cygwin libraries on your system somewhere, even if one
of them has been renamed to something you don't recognise.

Brian

--
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/