From: Peter Maydell <peter.maydell@linaro.org>
To: Helge Deller <deller@gmx.de>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Richard Henderson <richard.henderson@linaro.org>,
Eduardo Habkost <ehabkost@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] configure: Relax check for libseccomp
Date: Wed, 3 Apr 2019 22:17:01 +0700 [thread overview]
Message-ID: <CAFEAcA91KBoxtAdjpsVZ3wE_9YaaeMHYEy=VHPNAKspjjH7UDQ@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA8qyunxOtqrWLPsr34fUt5t2kCrXa8hOMti0bYYbZDpyA@mail.gmail.com>
On Wed, 3 Apr 2019 at 22:16, Peter Maydell <peter.maydell@linaro.org> wrote:
>
> On Wed, 3 Apr 2019 at 19:51, Helge Deller <deller@gmx.de> wrote:
>
> [cc'ing Eduardo as the seccomp submaintainer]
>
> > On a non-release architecture, the configure program aborts if the
> > --enable-seccomp flag was given (with no way to work around it on the
> > command line):
> >
> > ERROR: User requested feature libseccomp
> > configure was not able to find it.
> > libseccomp is not supported for host cpu parisc64
> What particular host arch are you using?
Doh, just noticed that the error message has the answer to this!
thanks
- PMM
next prev parent reply other threads:[~2019-04-03 15:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 12:49 [Qemu-devel] [PATCH] configure: Relax check for libseccomp Helge Deller
2019-04-03 15:16 ` Peter Maydell
2019-04-03 15:17 ` Peter Maydell [this message]
2019-04-03 15:55 ` Helge Deller
2019-04-03 21:04 ` Eduardo Habkost
2019-04-04 1:44 ` Peter Maydell
2019-04-03 16:17 ` Daniel P. Berrangé
2019-04-04 1:53 ` Peter Maydell
2019-04-04 6:59 ` Thomas Huth
2019-04-04 8:56 ` Daniel P. Berrangé
2019-04-04 18:39 ` [Qemu-devel] [PATCH v2] " Helge Deller
2019-04-04 20:01 ` Thomas Huth
2019-04-05 9:01 ` Eduardo Otubo
2019-04-05 9:01 ` Eduardo Otubo
2019-04-05 7:34 ` Daniel P. Berrangé
2019-04-05 7:34 ` Daniel P. Berrangé
2019-04-05 8:50 ` Philippe Mathieu-Daudé
2019-04-05 8:50 ` Philippe Mathieu-Daudé
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='CAFEAcA91KBoxtAdjpsVZ3wE_9YaaeMHYEy=VHPNAKspjjH7UDQ@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=deller@gmx.de \
--cc=ehabkost@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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;
as well as URLs for NNTP newsgroup(s).