From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27499 invoked by alias); 10 Jan 2012 21:23:58 -0000 Received: (qmail 27488 invoked by uid 22791); 10 Jan 2012 21:23:55 -0000 X-SWARE-Spam-Status: No, hits=-3.2 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,RCVD_IN_DNSWL_LOW,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail-vw0-f41.google.com (HELO mail-vw0-f41.google.com) (209.85.212.41) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 10 Jan 2012 21:23:42 +0000 Received: by vbbfn1 with SMTP id fn1so28695vbb.0 for ; Tue, 10 Jan 2012 13:23:42 -0800 (PST) Received: by 10.52.90.71 with SMTP id bu7mr6324624vdb.63.1326230622053; Tue, 10 Jan 2012 13:23:42 -0800 (PST) MIME-Version: 1.0 Received: by 10.52.90.71 with SMTP id bu7mr6324616vdb.63.1326230621956; Tue, 10 Jan 2012 13:23:41 -0800 (PST) Received: by 10.220.229.1 with HTTP; Tue, 10 Jan 2012 13:23:41 -0800 (PST) In-Reply-To: <838vlfe0k9.fsf@gnu.org> References: <83hb03e9sx.fsf@gnu.org> <838vlfe0k9.fsf@gnu.org> Date: Tue, 10 Jan 2012 21:26:00 -0000 Message-ID: Subject: Re: Building GDB 7.3.92 with MinGW From: Doug Evans To: Eli Zaretskii Cc: ams@gnu.org, gdb-patches@sourceware.org X-System-Of-Record: true Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2012-01/txt/msg00318.txt.bz2 On Tue, Jan 10, 2012 at 12:59 PM, Eli Zaretskii wrote: >> Date: Tue, 10 Jan 2012 14:25:11 -0500 >> From: ams@gnu.org (Alfred M. Szmidt) >> CC: gdb-patches@sourceware.org >> >> `make install' is generally the way one should install GNU projects on >> a end-user system, since that makes it possible to debug things (hence >> why CFLAGS contains -g by default); install-strip is really for people >> with little disk space. > > Well, an unstripped GDB weighs in at some 47MB, which is just too > much. > > And you can't usefully debug it outside of the source tree anyway. Well, having the sources is useful of course :-), but for reference sake there is value in debugging gdb outside of the *build* tree. i.e. debugging the installed copy. gdb is now more dependent on ancillary files (python, etc.) and it's useful to run gdb the way users run it. For one, remembering to pass -data-directory is a pain. :-)