X-Spam-Check-By: sourceware.org
From: "Dave Korn" <dave DOT korn AT artimi DOT com>
To: <cygwin AT cygwin DOT com>
Subject: RE: DLL problems on fresh install
Date: Wed, 22 Nov 2006 16:46:54 -0000
Message-ID: <029101c70e55$d13d6820$a501a8c0@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: <20061122163753.GF3952@tiny.vermontel.net>
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

On 22 November 2006 16:38, Scott Hepler wrote:

> On Wed, Nov 22, 2006 at 03:23:41PM -0000, Dave Korn wrote:
>> On 22 November 2006 14:28, Scott Hepler wrote:
>> 
>>> On Wed, Nov 22, 2006 at 01:15:44PM -0000, Dave Korn wrote:
>> 
>>>>   Or in other words....
>>>> 
>>>>> Problem reports:       http://cygwin.com/problems.html
>>>> 
>>>> ... get busy with the cygcheck attachment, dude!
>>> 
>>> Heh, cygcheck didn't work either, of course.
>> 
>>   That's wrong, or if it is correct, it is unrelated.  Personally, I think
>> you just don't want to admit you didn't even try it.  If you did, perhaps
>> you could describe the error that occurred....?
> 
> You might indeed be right -- I certainly can't argue.  I tried a lot of
> things which gave negative error indications.  Sorry to bug you.
> 
> -s.

  Heh, sorry for being so surreptitious about my meaning.

  The point is: cygcheck is *not* a cygwin program, it is a win32 native
program (compiled using -mno-cygwin) for *exactly* this reason: so that if
everything else is broken, you can still run cygcheck to try and find out what
the matter is.  The "of course" at the end of your mention of it made me think
you were suggesting it had produced the same clashing dlls error.

  While it /can/ produce this error, as it tries to invoke 'id' as a
subprogram to get the user/group numbers, and 'id' *is* a cygwin executable,
then even though 'id' fails, the rest of cygcheck runs fine and produces lots
of useful output.

    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/