qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Thomas Huth <thuth@redhat.com>, qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org
Subject: Re: [Qemu-devel] [PATCH qemu] configure: Allow capstone=git only if git update is not disabled
Date: Mon, 29 Jan 2018 17:44:51 +1100	[thread overview]
Message-ID: <4482df3b-8700-9b5f-43f4-08d5fe31d42a@ozlabs.ru> (raw)
In-Reply-To: <7b942fc7-a061-789a-4223-030d234602ca@redhat.com>

On 15/01/18 17:48, Thomas Huth wrote:
> On 15.01.2018 03:35, Alexey Kardashevskiy wrote:
>> Even with --disable-git-update, ./configure tries updating the capstone
>> submodule instead of marking it "no"; this disables capstone submodule
>> if git update is disabled.
>>
>> Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
>> ---
>>  configure | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/configure b/configure
>> index 89bd662..92c21b3 100755
>> --- a/configure
>> +++ b/configure
>> @@ -4502,7 +4502,7 @@ case "$capstone" in
>>    "" | yes)
>>      if $pkg_config capstone; then
>>        capstone=system
>> -    elif test -e "${source_path}/.git" ; then
>> +    elif test -e "${source_path}/.git" -a $git_update = 'yes' ; then
>>        capstone=git
>>      elif test -e "${source_path}/capstone/Makefile" ; then
>>        capstone=internal
>>
> 
> Reviewed-by: Thomas Huth <thuth@redhat.com>


Thanks mate. What's next? :)


-- 
Alexey

  reply	other threads:[~2018-01-29  6:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-15  2:35 [Qemu-devel] [PATCH qemu] configure: Allow capstone=git only if git update is not disabled Alexey Kardashevskiy
2018-01-15  6:48 ` Thomas Huth
2018-01-29  6:44   ` Alexey Kardashevskiy [this message]
2018-01-29  6:59     ` Thomas Huth
2018-02-10  7:13 ` Michael Tokarev

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=4482df3b-8700-9b5f-43f4-08d5fe31d42a@ozlabs.ru \
    --to=aik@ozlabs.ru \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=thuth@redhat.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;
as well as URLs for NNTP newsgroup(s).