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: Fri, 02 Aug 2002 23:50:55 -0500 (Central Daylight Time) From: Michael Hoffman Subject: Re: Performance of New Installation In-reply-to: <002901c23a3a$c153bd40$286581c2@webtec.co.uk> X-X-Sender: grouse AT mail DOT utexas DOT edu To: cygwin AT cygwin DOT com Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII On Fri, 2 Aug 2002, Alex Hole wrote: > My problem is that in trying to compile gdb for a cross platform target, > the configure script took more that 2 hours to run. [This is mostly a repeat of a message I wrote last week] Nothing is free. The extra layer of portability Cygwin provides costs something in performance even if it is gratis. Anything that is file-intensive or runs lots of other processes (e.g. configure; make) will have performance problems. Some suggestions for speedups despite this: 1) I find automated virus checkers slow Cygwin's performance A LOT 2) make your PATH as short as possible (your path is way longer than it needs to be to do this build) 3) make sure it doesn't include network shares or double slashes at the beginning which will cause it to try to access a network share (I know you did this already; just a reminder) 4) use mount --executable to speed up checking for executables -- Michael Hoffman The University of Texas at Austin -- 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/