From: Tom Tromey <tom@tromey.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/3] some minor Makefile improvements
Date: Mon, 24 Dec 2018 21:09:00 -0000 [thread overview]
Message-ID: <20181224210927.16741-1-tom@tromey.com> (raw)
This short series makes a few minor improvements to the gdb Makefile.
I think each patch is self-explanatory.
I tested this on x86-64 Fedora 28 by doing various rebuilds, and also
running some tests to ensure that the first patch doesn't affect
correctness.
However, I wasn't able to test this on the buildbot -- the Fedora
buildbot has stopped working entirely for me, and "pip" couldn't
install one, either :-( So, the last patch in particular requires some
extra scrutiny.
Tom
next reply other threads:[~2018-12-24 21:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-24 21:09 Tom Tromey [this message]
2018-12-24 21:09 ` [PATCH 3/3] Build gdb "nat" files in subdirectory Tom Tromey
2018-12-27 4:29 ` Simon Marchi
2018-12-27 20:03 ` Tom Tromey
2018-12-24 21:10 ` [PATCH 1/3] Remove gdbtypes special case from init.c rule Tom Tromey
2018-12-24 21:10 ` [PATCH 2/3] Make init.c depend on source files Tom Tromey
2018-12-27 4:02 ` Simon Marchi
2018-12-27 4:21 ` Tom Tromey
2018-12-27 4:23 ` Simon Marchi
2018-12-27 4:24 ` Simon Marchi
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=20181224210927.16741-1-tom@tromey.com \
--to=tom@tromey.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