X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=pXJQQ2ZWqzgPzpbUHsIKIO7OBaaN3i3j/xmL00HVR9KNhgopcFFiJ
	Xd0Mao55H+LSIUQRrOlRNGP6K4Et03m1yhJyF+uaQ/1TZL9Z42MTc9agTle1KQ6m
	sF49E7d5M3NO157jR+NTOZMI7t72+TjGzCkBIFbaJ8v/FysK6qbRYs=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	bh=yLZ8Uyt7L0qa/LKFUqRwma6DRmk=; b=Jtfu1PP7/djQ6F664IgfBAMC8EFj
	sUhEc/r3YOkoyMzEjnOkitr9169LPsGu4+zPFV7inBLP8eG0cC1bpkBvCn56fKjp
	OKE8ht0CkYXXpRBojth+orzLRP0Xj1xbjYTsgJJPiHckgjGogNNNOEwCEhOdtJEP
	66iTi5C/iB0KbrU=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
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
X-Spam-SWARE-Status:	No, score=-0.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE,RCVD_IN_SEMBACKSCATTER,TW_YG autolearn=no version=3.3.1
X-Mail-Handler:	Dyn Standard SMTP by Dyn
X-Report-Abuse-To:	abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User:	U2FsdGVkX1+AgWo8sW15W929k7uefRK9
Date:	Tue, 30 Apr 2013 21:10:57 -0400
From:	Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: cygwin install failed, need help troubleshooting
Message-ID:	<20130501011057.GF3781@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<CACr88HM7G2kEN0QOJnBThBkcn4cqtb8SROvhQaiEp8c+U-nULA AT mail DOT gmail DOT com> <20130501005817 DOT GE3781 AT ednor DOT casa DOT cgf DOT cx>
MIME-Version:	1.0
In-Reply-To:	<20130501005817.GE3781@ednor.casa.cgf.cx>
User-Agent:	Mutt/1.5.20 (2009-06-14)

On Tue, Apr 30, 2013 at 08:58:17PM -0400, Christopher Faylor wrote:
>On Tue, Apr 30, 2013 at 05:46:08PM -0700, John Guad wrote:
>>I googled that message about base mismash and all the evidence points
>>to cygwin1.dll being the issue but there's nothing useful about fixing
>>it.  The only instance of that dll on this machine is the one
>>downloaded and installed by the setup.exe program, so it doesn't make
>>sense to think it's a bad version.
>
>People often say that but most of the time they find that there is
>another version of the dll lurking somewhere on the system, like in
>c:\windows\system32 .

I forgot to mention:
                        VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV
>Problem reports:       http://cygwin.com/problems.html

You should be able to run the cygcheck program from a windows command
shell without causing the kind of problem that you're reporting.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -