Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/libseccomp: needs headers >= 3.12
Date: Tue, 31 Mar 2015 19:57:23 +0300	[thread overview]
Message-ID: <20150331165723.GP12479@tarshish> (raw)
In-Reply-To: <1427819637-2471-1-git-send-email-bernd.kuhls@t-online.de>

Hi Bernd,

On Tue, Mar 31, 2015 at 06:33:57PM +0200, Bernd Kuhls wrote:
> EM_AARCH64 was added to linux kernel with version 3.12:
> https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/log/include/uapi/linux/elf-em.h?h=linux-3.12.y
> 
> Fixes
> http://autobuild.buildroot.net/results/4cd/4cd6aaccde9fb0f80e49133b477f330b601f4a63/
> http://autobuild.buildroot.net/results/bd1/bd105e821de583e582199aae31fab13ef17e67a0/
> http://autobuild.buildroot.net/results/092/092143df2b91d50850067274da531c713f2ccb72/
> http://autobuild.buildroot.net/results/814/8149cf0c3ef3ef8d91b5891591a71691dc3d7427/
> 
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
>  package/libseccomp/Config.in |    6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/package/libseccomp/Config.in b/package/libseccomp/Config.in
> index 4e893c8..153e14a 100644
> --- a/package/libseccomp/Config.in
> +++ b/package/libseccomp/Config.in
> @@ -2,6 +2,7 @@ config BR2_PACKAGE_LIBSECCOMP
>  	bool "libseccomp"
>  	depends on BR2_aarch64 || BR2_mips || BR2_mipsel || BR2_mips64 || \
>  		BR2_mips64el || BR2_i386 || BR2_x86_64
> +	depends on BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_12

Can't we limit the 3.12 headers dependency to BR2_aarch64?

Something like (untested):

	depends on BR2_mips || BR2_mipsel || BR2_mips64 || \
		BR2_mips64el || BR2_i386 || BR2_x86_64 \
		|| (BR2_aarch64 && BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_12)

>  	help
>  	  High level interface to the Linux Kernel's seccomp filter
>  
> @@ -13,3 +14,8 @@ config BR2_PACKAGE_LIBSECCOMP
>  	  and easily adopted by application developers.
>  
>  	  https://github.com/seccomp/libseccomp
> +
> +comment "libseccomp needs headers >= 3.12"
> +	depends on BR2_aarch64 || BR2_mips || BR2_mipsel || BR2_mips64 || \
> +		BR2_mips64el || BR2_i386 || BR2_x86_64
> +	depends on !BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_12

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

  reply	other threads:[~2015-03-31 16:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-31 16:33 [Buildroot] [PATCH 1/1] package/libseccomp: needs headers >= 3.12 Bernd Kuhls
2015-03-31 16:57 ` Baruch Siach [this message]
2015-03-31 16:59   ` Bernd Kuhls
2015-03-31 17:11     ` Baruch Siach
2015-03-31 21:33       ` Thomas Petazzoni
2015-03-31 21:46 ` Thomas Petazzoni

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=20150331165723.GP12479@tarshish \
    --to=baruch@tkos.co.il \
    --cc=buildroot@busybox.net \
    /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