From: Doug Evans <dje@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: ams@gnu.org, gdb-patches@sourceware.org
Subject: Re: Building GDB 7.3.92 with MinGW
Date: Tue, 10 Jan 2012 21:26:00 -0000 [thread overview]
Message-ID: <CADPb22RFWe+F_3SfZo7k=eJg5TBJSRrZgLRL=NS6jhhd5RYLjQ@mail.gmail.com> (raw)
In-Reply-To: <838vlfe0k9.fsf@gnu.org>
On Tue, Jan 10, 2012 at 12:59 PM, Eli Zaretskii <eliz@gnu.org> 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. :-)
next prev parent reply other threads:[~2012-01-10 21:23 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-10 18:46 Eli Zaretskii
2012-01-10 18:59 ` Doug Evans
2012-01-10 20:56 ` Eli Zaretskii
2012-01-13 11:28 ` Eli Zaretskii
2012-01-10 19:25 ` Tom Tromey
2012-01-10 20:55 ` Joseph S. Myers
2012-01-10 20:58 ` Eli Zaretskii
2012-01-10 21:00 ` Eli Zaretskii
2012-01-10 19:31 ` Alfred M. Szmidt
2012-01-10 21:01 ` Eli Zaretskii
2012-01-10 21:26 ` Doug Evans [this message]
2012-01-11 0:37 ` asmwarrior
2012-01-11 4:08 ` Eli Zaretskii
2012-01-11 4:54 ` asmwarrior
2012-01-11 17:54 ` Doug Evans
2012-01-12 0:17 ` asmwarrior
2012-01-12 6:47 ` Eli Zaretskii
2012-01-12 8:07 ` Joel Brobecker
2012-01-12 11:54 ` Eli Zaretskii
2012-01-12 12:35 ` Joel Brobecker
2012-01-12 16:59 ` Eli Zaretskii
2012-01-13 14:29 ` asmwarrior
2012-01-13 16:55 ` Eli Zaretskii
2012-01-14 13:53 ` asmwarrior
[not found] ` <4F117B33.8080906@gmail.com>
2012-01-14 18:15 ` Eli Zaretskii
2012-01-15 3:33 ` Pierre Muller
[not found] ` <18546.4176851839$1326580387@news.gmane.org>
2012-01-15 3:54 ` asmwarrior
[not found] ` <000001ccd30c$5ce854e0$16b8fea0$%muller@ics-cnrs.unistra.fr>
2012-01-15 13:35 ` Eli Zaretskii
2012-01-15 17:01 ` Joel Brobecker
2012-01-15 18:55 ` Eli Zaretskii
2012-01-15 18:01 ` Pierre Muller
[not found] ` <000301ccd3a7$3db8c460$b92a4d20$%muller@ics-cnrs.unistra.fr>
2012-01-15 18:55 ` Eli Zaretskii
2012-01-16 3:08 ` Pierre Muller
2012-01-10 21:33 ` Tom Tromey
2012-01-11 1:31 ` asmwarrior
2012-01-11 4:30 ` Eli Zaretskii
2012-01-11 4:30 ` asmwarrior
2012-01-11 3:32 ` Joel Brobecker
2012-01-13 11:06 ` Eli Zaretskii
2012-01-13 12:39 ` Joel Brobecker
2012-01-13 13:56 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADPb22RFWe+F_3SfZo7k=eJg5TBJSRrZgLRL=NS6jhhd5RYLjQ@mail.gmail.com' \
--to=dje@google.com \
--cc=ams@gnu.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox