X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: =?ISO-8859-1?Q?Ren=E9_Berber?= Subject: Re: Nominally, how long to build cygwin/bash debug versions? Date: Wed, 22 Feb 2006 10:44:08 -0600 Lines: 30 Message-ID: References: <43FC3052 DOT 2090509 AT serv DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) In-Reply-To: <43FC3052.2090509@serv.net> OpenPGP: url=ldap://keyserver.pgp.com X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: 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 L Anderson wrote: > I'm trying to build debug versions of cygwin1 and bash in an attempt to > isolate a problem I'm having. My first attempt with cygwin seemed to > grind and grind with nothing being produced--not even errors. After > considerable time I killed the process. Realizing that maybe I was just > impatient, I have a question I hope someone can answer. >=20 > Counting only computer time and assuming everything works perfectly, > nominally, how long might I expect it to take to build a cygwin debug > version? A bash debug version? (10min?, 30min?, 2hrs?, ...?) You don't need to build a cygwin1.dll debug version, just download a snapsh= ot with its corresponding .dbg file, plus the sources if you want to get gdb i= nto cygwin1 (the sources have to be installed in the same place as the debug in= fo was created with, you'll see the path when gdb complains about not finding = the source). And to answer your question, on a P4 AT 2 DOT 8GHz it takes less than 10 minutes. HTH --=20 Ren=E9 Berber -- 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/