From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Cc: Andrew Burgess <aburgess@redhat.com>
Subject: [PATCHv2 1/3] gdb/Makefile.in: remove SOURCES variable
Date: Wed, 23 Mar 2022 10:50:24 +0000 [thread overview]
Message-ID: <59f3f486c3decdfcad98f3065ae35ae51bb030b2.1648032382.git.aburgess@redhat.com> (raw)
In-Reply-To: <cover.1648032382.git.aburgess@redhat.com>
The SOURCES variable was added to gdb/Makefile.in as part of commit:
commit fb40c20903110ed8af9701ce7c2635abd3770d52
Date: Wed Feb 23 00:25:43 2000 +0000
Add mi/ and testsuite/gdb.mi/ subdirectories.
But as far as I can tell was not used at the time it was added, and is
not used today.
Lets remove it.
---
gdb/Makefile.in | 1 -
1 file changed, 1 deletion(-)
diff --git a/gdb/Makefile.in b/gdb/Makefile.in
index aecab41eeb8..009b733092d 100644
--- a/gdb/Makefile.in
+++ b/gdb/Makefile.in
@@ -1590,7 +1590,6 @@ HFILES_WITH_SRCDIR = \
DEPFILES = $(TARGET_OBS) $(SER_HARDWIRE) $(NATDEPFILES) $(SIM_OBS)
-SOURCES = $(SFILES) $(ALLDEPFILES) $(YYFILES) $(CONFIG_SRCS)
# Don't include YYFILES (*.c) because we already include *.y in SFILES,
# and it's more useful to see it in the .y file.
TAGFILES_NO_SRCDIR = $(SFILES) $(HFILES_NO_SRCDIR) $(ALLDEPFILES) \
--
2.25.4
next prev parent reply other threads:[~2022-03-23 10:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-02 12:16 A couple of trivial fixes Reuben Thomas
2021-01-04 19:33 ` Tom Tromey
2021-01-06 21:46 ` Reuben Thomas
2022-03-22 22:10 ` Reuben Thomas
2022-03-23 10:50 ` [PATCHv2 0/3] Fix for 'make tags' build rule Andrew Burgess
2022-03-23 10:50 ` Andrew Burgess [this message]
2022-03-23 10:50 ` [PATCHv2 2/3] gdb/Makefile.in: fix 'make tags' build target Andrew Burgess
2022-03-23 10:50 ` [PATCHv2 3/3] gdb/Makefile.in: move ALLDEPFILES earlier in Makefile.in Andrew Burgess
2022-04-03 14:50 ` [PATCHv2 0/3] Fix for 'make tags' build rule Andrew Burgess
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=59f3f486c3decdfcad98f3065ae35ae51bb030b2.1648032382.git.aburgess@redhat.com \
--to=aburgess@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).