From: dje@google.com (Doug Evans)
To: gdb-patches@sourceware.org
Subject: [RFA] gdbserver/Makefile.in cleanup
Date: Mon, 24 Nov 2008 23:08:00 -0000 [thread overview]
Message-ID: <20081124200206.111311C79A2@localhost> (raw)
Ok to check in?
I could instead just delete VERSION,DIST.
For LINT,LINTFLAGS perhaps the thing to do is add a lint rule akin
to gdb/Makefile.in, except I wonder how often it gets used and gcc
is much better at warnings these days.
2008-11-24 Doug Evans <dje@google.com>
* Makefile.in (VERSION,DIST,LINT,LINTFLAGS): Delete, unused.
Index: Makefile.in
===================================================================
RCS file: /cvs/src/src/gdb/gdbserver/Makefile.in,v
retrieving revision 1.66
diff -u -p -r1.66 Makefile.in
--- Makefile.in 18 Nov 2008 21:48:48 -0000 1.66
+++ Makefile.in 24 Nov 2008 19:57:28 -0000
@@ -96,13 +96,6 @@ INTERNAL_CFLAGS = $(WARN_CFLAGS) ${CFLA
LDFLAGS = @LDFLAGS@
INTERNAL_LDFLAGS = $(LDFLAGS) @RDYNAMIC@
-# Perhaps should come from parent Makefile
-VERSION = gdbserver-4.12.3
-DIST=gdb
-
-LINT=/usr/5bin/lint
-LINTFLAGS=
-
# All source files that go into linking GDB remote server.
SFILES= $(srcdir)/gdbreplay.c $(srcdir)/inferiors.c \
next reply other threads:[~2008-11-24 20:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-24 23:08 Doug Evans [this message]
2008-11-25 1:12 ` Daniel Jacobowitz
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=20081124200206.111311C79A2@localhost \
--to=dje@google.com \
--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