Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/libseccomp: needs headers >= 3.12
Date: Tue, 31 Mar 2015 23:33:39 +0200	[thread overview]
Message-ID: <20150331233339.437d96f8@free-electrons.com> (raw)
In-Reply-To: <20150331171143.GQ12479@tarshish>

Dear Baruch Siach,

On Tue, 31 Mar 2015 20:11:43 +0300, Baruch Siach wrote:

> 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.

Agreed, this would allow to remove the dependency of libseccomp on >=
3.12. Though I personally don't mind that much, since libseccomp does
not have any reverse dependencies, except systemd (for which it is an
optional dependency), and systemd itself already depends on having a
fairly recent set of kernel headers.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-03-31 21:33 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
2015-03-31 21:33       ` Thomas Petazzoni [this message]
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=20150331233339.437d96f8@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --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