All of lore.kernel.org
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: qemu-devel@nongnu.org
Cc: Richard Henderson <richard.henderson@linaro.org>
Subject: [Qemu-devel] [PATCH] configure: Relax check for libseccomp
Date: Wed, 3 Apr 2019 14:49:48 +0200	[thread overview]
Message-ID: <20190403124948.GA14129@ls3530.dellerweb.de> (raw)

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

Instead of aborting, fall back to require libseccomp version 2.2.0
(or any higher version currently installed) which should be OK for
non-release architectures.

Signed-off-by: Helge Deller <deller@gmx.de>

diff --git a/configure b/configure
index 1c563a7027..8632267049 100755
--- a/configure
+++ b/configure
@@ -2389,7 +2389,6 @@ if test "$seccomp" != "no" ; then
         libseccomp_minver="2.3.0"
         ;;
     *)
-        libseccomp_minver=""
         ;;
     esac

             reply	other threads:[~2019-04-03 12:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-03 12:49 Helge Deller [this message]
2019-04-03 15:16 ` [Qemu-devel] [PATCH] configure: Relax check for libseccomp Peter Maydell
2019-04-03 15:17   ` Peter Maydell
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é

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=20190403124948.GA14129@ls3530.dellerweb.de \
    --to=deller@gmx.de \
    --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 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.