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 20:11:43 +0300	[thread overview]
Message-ID: <20150331171143.GQ12479@tarshish> (raw)
In-Reply-To: <XnsA46EC1420D725berndkuhlsPkbjNfxxIA@bernd-kuhls.de>

Hi Bernd,

On Tue, Mar 31, 2015 at 06:59:53PM +0200, Bernd Kuhls wrote:
> Baruch Siach <baruch@tkos.co.il> wrote in 
> news:20150331165723.GP12479 at tarshish:
> 
> > Can't we limit the 3.12 headers dependency to BR2_aarch64?
> 
> no, the build errors are not limited to aarch64: 
> http://autobuild.buildroot.net/?reason=libseccomp-v2.2.0

Now I see. It is kernel commit 909e3ee41 that adds both EM_ARM and EM_AARCH64 
to a generic header. In this case maybe patching the code is preferable. 
Something like:

#ifndef EM_ARM
#define EM_ARM 40
#endif

#ifndef EM_AARCH64
#define EM_AARCH64 183
#endif

Something like that should be acceptable upstream.

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 17:11 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
2015-03-31 16:59   ` Bernd Kuhls
2015-03-31 17:11     ` Baruch Siach [this message]
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=20150331171143.GQ12479@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