From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Juan Quintela <quintela@redhat.com>
Subject: Re: "Unknown option --exist" message when building qemu
Date: Tue, 10 Mar 2020 18:32:16 +0000 [thread overview]
Message-ID: <20200310183216.GE3304@work-vm> (raw)
In-Reply-To: <66841404-892f-edef-eb1a-37ed2e2e08ee@roeck-us.net>
* Guenter Roeck (linux@roeck-us.net) wrote:
> Hi,
>
> when building qemu, I keep seeing the following message.
>
> Unknown option --exist
>
> This was introduced with commit 3a67848134d0 ("configure: Enable test and libs for zstd").
> If I replace "--exist" with "--exists", on a system with libzstd-dev installed, I get
> a number of error messages.
>
> migration/multifd-zstd.c:125:9: error: unknown type name ‘ZSTD_EndDirective’; did you mean ‘ZSTD_DDict’?
> migration/multifd-zstd.c:125:35: error: ‘ZSTD_e_continue’ undeclared
> migration/multifd-zstd.c:128:21: error: ‘ZSTD_e_flush’ undeclared
> migration/multifd-zstd.c:143:19: error: implicit declaration of function ‘ZSTD_compressStream2’
> migration/multifd-zstd.c:143:19: error: nested extern declaration of ‘ZSTD_compressStream2’
>
> Any idea, anyone, what might be wrong ?
Yep, Juan's just trying to fix it.
Dave
> Thanks,
> Guenter
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2020-03-10 18:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 18:27 "Unknown option --exist" message when building qemu Guenter Roeck
2020-03-10 18:32 ` Dr. David Alan Gilbert [this message]
2020-03-10 18:45 ` Juan Quintela
2020-03-10 20:23 ` Guenter Roeck
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=20200310183216.GE3304@work-vm \
--to=dgilbert@redhat.com \
--cc=linux@roeck-us.net \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.