All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Moore <pmoore@redhat.com>
To: Eduardo Otubo <eduardo.otubo@profitbricks.com>
Cc: peter.maydell@linaro.org, qemu-devel@nongnu.org,
	philipp.gesang@intra2net.com
Subject: Re: [Qemu-devel] [PATCH] seccomp: change configure to avoid arm 32 to break
Date: Thu, 06 Nov 2014 11:22:16 -0500	[thread overview]
Message-ID: <2160380.fdzADCfzWy@sifl> (raw)
In-Reply-To: <1415285358-7446-1-git-send-email-eduardo.otubo@profitbricks.com>

On Thursday, November 06, 2014 03:49:18 PM Eduardo Otubo wrote:
> Right now seccomp is breaking the compilation of Qemu on armv7l due
> to libsecomp current lack of support for this arch. This problem is
> already fixed on libseccomp upstream but no release date for that is
> scheduled to far. This patch disables support for seccomp on armv7l
> temporarily until libseccomp does a new release. Then I'll remove the
> hack and update libseccomp dependency on configure script.
> 
> Related bug: https://bugs.launchpad.net/qemu/+bug/1363641
> 
> Signed-off-by: Eduardo Otubo <eduardo.otubo@profitbricks.com>
> ---
>  configure | 20 +++++++++++---------
>  1 file changed, 11 insertions(+), 9 deletions(-)
> 
> diff --git a/configure b/configure
> index 2f17bf3..16fd7f5 100755
> --- a/configure
> +++ b/configure
> @@ -1823,15 +1823,17 @@ fi
>  # libseccomp check
> 
>  if test "$seccomp" != "no" ; then
> -    if $pkg_config --atleast-version=2.1.0 libseccomp; then
> -        libs_softmmu="$libs_softmmu `$pkg_config --libs libseccomp`"
> -        QEMU_CFLAGS="$QEMU_CFLAGS `$pkg_config --cflags libseccomp`"
> -	seccomp="yes"
> -    else
> -	if test "$seccomp" = "yes"; then
> -            feature_not_found "libseccomp" "Install libseccomp devel >=
> 2.1.0" -	fi
> -	seccomp="no"
> +    if test "$cpu" = "i386" || test "$cpu" = "x86_64"; then
> +        if $pkg_config --atleast-version=2.1.0 libseccomp; then
> +            libs_softmmu="$libs_softmmu `$pkg_config --libs libseccomp`"
> +            QEMU_CFLAGS="$QEMU_CFLAGS `$pkg_config --cflags libseccomp`"
> +            seccomp="yes"
> +        else
> +            if test "$seccomp" = "yes"; then
> +                feature_not_found "libseccomp" "Install libseccomp devel >=
> 2.1.0" +            fi
> +            seccomp="no"
> +        fi
>      fi
>  fi
>  ##########################################

Also, note the current release of libseccomp is v2.1.1 which has a number of 
bug fixes on top of v2.1.0.

-- 
paul moore
security and virtualization @ redhat

  parent reply	other threads:[~2014-11-06 16:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-06 14:49 [Qemu-devel] [PATCH] seccomp: change configure to avoid arm 32 to break Eduardo Otubo
2014-11-06 15:49 ` Peter Maydell
2014-11-06 16:22   ` Eduardo Otubo
2014-11-06 16:22 ` Paul Moore [this message]
2014-11-06 16:36   ` Eduardo Otubo
2014-11-06 16:54     ` Paul Moore
  -- strict thread matches above, loose matches on Subject: below --
2014-11-05 16:47 Eduardo Otubo
2014-11-05 17:08 ` Peter Maydell
2014-11-05 19:46   ` Paul Moore
2014-11-05 20:08     ` Peter Maydell
2014-11-05 20:35       ` Paul Moore
2014-11-06  9:24         ` Eduardo Otubo
2014-11-06 16:37           ` Paul Moore

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=2160380.fdzADCfzWy@sifl \
    --to=pmoore@redhat.com \
    --cc=eduardo.otubo@profitbricks.com \
    --cc=peter.maydell@linaro.org \
    --cc=philipp.gesang@intra2net.com \
    --cc=qemu-devel@nongnu.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.