From: Richard Henderson <richard.henderson@linaro.org>
To: Stephen Checkoway <stephen.checkoway@oberlin.edu>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] capstone: Support capstone/capstone.h
Date: Tue, 2 Apr 2019 08:28:10 +0700 [thread overview]
Message-ID: <af4fdce2-10f2-de5d-d2b9-93b86e9443a6@linaro.org> (raw)
In-Reply-To: <20190401220752.22577-1-stephen.checkoway@oberlin.edu>
On 4/2/19 5:07 AM, Stephen Checkoway wrote:
> Starting with version 4 of capstone, the header files live in the
> `$prefix/include/capstone` directory.
>
> This modifies the configure script to check for <capstone/capstone.h> if
> <capstone.h> cannot be found.
>
> Signed-off-by: Stephen Checkoway <stephen.checkoway@oberlin.edu>
> ---
> configure | 9 +++++++++
> include/disas/capstone.h | 4 ++++
> 2 files changed, 13 insertions(+)
Thanks. We should probably update our submodule to the v4 release as well.
r~
next prev parent reply other threads:[~2019-04-02 1:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 22:07 [Qemu-devel] [PATCH] capstone: Support capstone/capstone.h Stephen Checkoway
2019-04-02 1:28 ` Richard Henderson [this message]
2019-04-02 4:52 ` Stephen Checkoway
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=af4fdce2-10f2-de5d-d2b9-93b86e9443a6@linaro.org \
--to=richard.henderson@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stephen.checkoway@oberlin.edu \
/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 NNTP newsgroup(s).