From: Andreas Schwab <schwab@suse.de>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Don't include gdbarch.h from defs.h
Date: Thu, 01 Aug 2019 12:21:00 -0000 [thread overview]
Message-ID: <mvmftml6pq9.fsf@suse.de> (raw)
In-Reply-To: <87ftmmhz7m.fsf@tromey.com> (Tom Tromey's message of "Wed, 31 Jul 2019 11:48:45 -0600")
On Jul 31 2019, Tom Tromey <tom@tromey.com> wrote:
>>>>>> "Andreas" == Andreas Schwab <schwab@suse.de> writes:
>
> Andreas> In file included from ../../gdb/ia64-tdep.h:25:0,
> Andreas> from ../../gdb/ia64-linux-tdep.c:21:
> Andreas> ../../gdb/ia64-libunwind-tdep.h:74:11: error: âreadable_regcacheâ has not been declared
> Andreas> readable_regcache *regcache,
>
> I don't have libunwind-ia64.h, so I couldn't reproduce this locally.
>
> Anyway, please try the appended. Maybe it will work.
This fixes the errors.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
prev parent reply other threads:[~2019-08-01 12:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 21:10 Tom Tromey
2019-07-10 18:40 ` Tom Tromey
2019-07-10 19:12 ` Simon Marchi
2019-07-10 20:57 ` Tom Tromey
[not found] ` <mvmy30e71pj.fsf@suse.de>
2019-07-31 17:48 ` Tom Tromey
2019-08-01 12:21 ` Andreas Schwab [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=mvmftml6pq9.fsf@suse.de \
--to=schwab@suse.de \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.com \
/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