X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 	tests=AWL,BAYES_00,SPF_PASS
X-Spam-Check-By: sourceware.org
Message-ID: <4B28E7E9.1080505@gmail.com>
Date: Wed, 16 Dec 2009 14:00:09 +0000
From: Dave Korn <dave DOT korn DOT cygwin AT googlemail DOT com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: gcc-3 won't compile after cygwin upgrade (cygwin1.dll hiding)
References: <90871a3a0912160507m4811f152v9a6b5d3e505ef0b1 AT mail DOT gmail DOT com>
In-Reply-To: <90871a3a0912160507m4811f152v9a6b5d3e505ef0b1@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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

David Nelson wrote:
> There is no question; only a report.

  It's well-known that you can't have multiple versions of the cygwin DLL
hanging around at the same time or you may get problems.  You seem to have had
both /bin dirs in your PATH at the same time; that's asking for trouble.

> Searching the web and the Cygwin archvies turned up:
>  cygcheck -svrh gcc-3 [thank you!]
> which reported that f:/cygwin/bin/cygwin1.dll was hiding c:\windows\cygwin1.dll.
> 
> "Good," I thought "new should hide old."
> 
> However, renaming /bin/cygwin1.dll to /bin/cygwin1.dll_ to unhide the
> older version resulted in gcc-3 succeeding.

  Right.  We should probably change the cygcheck output to not say that for
DLLs, only EXEs.  An exe earlier in the PATH hides an EXE later, but a DLL
earlier in the PATH won't necessarily get loaded ahead of one earlier in the
PATH, because the search-order rules for DLLs aren't exactly the same as for
EXEs; in particular, the first place of all it looks for DLLs is in the same
dir alongside the exe that is being started, even if that dir is way down the
PATH and there were other dirs first containing the same-named DLL.


    cheers,
      DaveK

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