From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Do not accidentally include in-tree readline headers
Date: Sun, 07 Oct 2018 04:46:00 -0000 [thread overview]
Message-ID: <877eiue53m.fsf@tromey.com> (raw)
In-Reply-To: <20180926125834.8845-1-tom@tromey.com> (Tom Tromey's message of "Wed, 26 Sep 2018 06:58:34 -0600")
Tom> gdb/ChangeLog
Tom> 2018-09-26 Tom Tromey <tom@tromey.com>
Tom> PR build/17077:
Tom> * Makefile.in (OPCODES_CFLAGS): Remove "-I$(OPCODES_SRC)/..".
Tom> * gdb/aarch64-tdep.c, gdb/amd64-tdep.c, gdb/arc-tdep.c,
Tom> gdb/cris-tdep.c, gdb/csky-tdep.c, gdb/frv-tdep.c, gdb/ft32-tdep.c,
Tom> gdb/i386-tdep.c, gdb/lm32-tdep.c, gdb/m68hc11-tdep.c,
Tom> gdb/mep-tdep.c, gdb/microblaze-tdep.c, gdb/mips-tdep.c,
Tom> gdb/msp430-tdep.c, gdb/nds32-tdep.c, gdb/nios2-tdep.h,
Tom> gdb/or1k-tdep.h, gdb/riscv-tdep.c, gdb/riscv-tdep.h,
Tom> gdb/rl78-tdep.c, gdb/rx-tdep.c, gdb/tilegx-tdep.c: Use ../opcode,
Tom> not opcode, in #include.
I'm checking this in now.
Tom
prev parent reply other threads:[~2018-10-07 4:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-26 12:59 Tom Tromey
2018-09-26 13:12 ` Andreas Schwab
2018-09-26 13:57 ` Tom Tromey
2018-09-26 16:47 ` Andrew Burgess
2018-09-26 20:19 ` Tom Tromey
2018-10-07 4:46 ` Tom Tromey [this message]
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=877eiue53m.fsf@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).