Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Thu, 27 Feb 2003 23:06:24 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Dumper.exe problems Message-ID: <20030228040624.GA23158@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <004301c2ded3$72ae81a0$0200000a AT agamemnon> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.1i On Thu, Feb 27, 2003 at 10:52:56PM -0500, Igor Pechtchanski wrote: >"dumper.exe" is part of the "cygwin" package: > > >There were some problems in the past with rebuilding from source tarballs >(you'll need at least the w32api source package). You might want to >search the list for build instructions. Alternatively, you could build >from CVS and save yourself the headache (at the risk of getting a whole >different one, of course)... ;-) The FAQ has build instructions. I recently removed the absolute w32api-must-be-in-winsup requirement but there is still no guarantee that the cygwin DLL will build without the latest w32api. >OTOH, dumper.exe should not have too many dependences outside of its >directory, so this may be simpler than rebuilding the whole cygwin source >tree. Dumper.exe is probably the only utility in winsup to have dependencies outside of its directory. It relies on binutils, too. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/