Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sourceware.cygnus.com
Delivered-To: mailing list cygwin@sourceware.cygnus.com
Date: Tue, 13 Apr 1999 17:33:23 -0400
Message-Id: <199904132133.RAA02628@envy.delorie.com>
From: DJ Delorie <dj@delorie.com>
To: J.J.vanderHeijden@student.utwente.nl
CC: cygwin@sourceware.cygnus.com
In-reply-to: 
	<Pine.LNX.4.10.9904132312010.2205-100000@wit381304.student.utwente.nl>
	(message from Jan-Jaap van der Heijden on Tue, 13 Apr 1999 23:16:15
	+0100 (WEST))
Subject: Re: MAKE and MinGW32 problems.
References:  <Pine.LNX.4.10.9904132312010.2205-100000@wit381304.student.utwente.nl>


> I think "objdump -p your.exe" is a more civilized way to do that.

Or even "cygcheck your.exe" which does nothing but list dll
inter-dependencies (at least, without switches to cygcheck it does
that), including indirect dependencies.

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com