From: Matt Rice <ratmice@gmail.com>
To: Project Archer <archer@sourceware.org>
Subject: Added branch for compiling with c++-compat
Date: Sat, 12 Jun 2010 01:52:00 -0000 [thread overview]
Message-ID: <AANLkTinVgh7r6gO06HHxolxZ6p_y-YB1tqzS3loiJ0nd@mail.gmail.com> (raw)
Hi all, I added a branch for compiling gdb with c++-compat
named: archer-ratmice-compile-Wc++-compat
I've been doing:
CFLAGS="-Wc++-compat" ./configure --disable-werror
and then tackling things one type of warning at a time.
in hopes that this will make the patches more easily reviewable.
The downside to this I suppose is that I may temporarily introduce a
warning and then
subsequently miss it in the deluge... If this happens i'll fix these
as I notice.
I guess a balance between number of patches and patch length will be
somewhat important....
I've just been commiting about at the point that I get the urge to
hold down the space bar
and see how much longer the dang patch is.
so far everything has been fairly mechanical, there is one ada macro
which looks like it may be remotely interesting.
next reply other threads:[~2010-06-12 1:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-12 1:52 Matt Rice [this message]
2010-09-16 21:18 ` Matt Rice
2010-09-16 21:39 ` Keith Seitz
2010-09-16 21:43 ` Matt Rice
2010-09-16 22:49 ` Keith Seitz
2010-09-16 23:43 ` Matt Rice
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=AANLkTinVgh7r6gO06HHxolxZ6p_y-YB1tqzS3loiJ0nd@mail.gmail.com \
--to=ratmice@gmail.com \
--cc=archer@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).