From: Tom Tromey <tom@tromey.com>
To: Gdb Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Include s12z-opc.h using ..
Date: Fri, 02 Aug 2019 18:22:00 -0000 [thread overview]
Message-ID: <87pnlne8ef.fsf@tromey.com> (raw)
In-Reply-To: <20190801170141.198456-1-cbiesinger@google.com> (Christian Biesinger via gdb-patches's message of "Thu, 1 Aug 2019 12:01:41 -0500")
>>>>> "Christian" == Christian Biesinger via gdb-patches <gdb-patches@sourceware.org> writes:
Christian> I must be missing something; I don't see how this can compile?
Christian> This file exists in binutils-gdb/opcodes, and as far as I can tell
Christian> nothing in Makefile.in adds this to the include path. This patch
Christian> makes my compile work (when using --enable-targets=all).
This patch made me realize that moving gdbsupport to top-level is going
to run into this same issue. I hadn't considered the
--with-system-readline case here :-(
I thought of 3 options:
1. Move all the gdbsupport headers into a subdirectory, either of
gdbsupport or include.
2. Add a -I for gdbsupport and change how the #includes are written --
dropping the "gdbsupport/" part.
3. Make a new "readline/readline" directory and move the contents there,
similar to what is done for gnulib.
On the whole I lean toward plan 3, because it would also let us handle
opcodes includes in a less ugly way.
Tom
prev parent reply other threads:[~2019-08-02 18:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190801170141.198456-1-cbiesinger@google.com>
2019-08-01 17:26 ` [PATCH] Include s12z-opc.h using ../opcodes Christian Biesinger via gdb-patches
2019-08-01 17:30 ` Simon Marchi
2019-08-01 17:46 ` Christian Biesinger via gdb-patches
2019-08-02 18:22 ` 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=87pnlne8ef.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