Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/libcap: needs headers >= 3.0
Date: Sun, 16 Nov 2014 23:11:09 +0100	[thread overview]
Message-ID: <87tx1ydcea.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1416135887-27267-1-git-send-email-yann.morin.1998@free.fr> (Yann E. MORIN's message of "Sun, 16 Nov 2014 12:04:47 +0100")

>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:

 > libcap requires XATTR_NAME_CAPS, which was introduced in Linux 2.6.24.
 > However, we have some toolchains, liek the CodeSourcery PowerPC 2011.03,
 > that is missing those defines, even though it uses headers from Linux
 > 2.6.38.

 > Since there is no perfect way to avoid the situation, just require
 > headers >= 3.0 to build libcap.

 > Propagate the new dependency to packages that select libcap.

 > Fixes a lot of build failures, of which:
 >     http://autobuild.buildroot.net/results/e90/e909ca48ad2d1c85b19258f65e0c89a2813ac45e/
 >     http://autobuild.buildroot.net/results/23a/23aac9bb1cc48e5974bcf50256a16c67318f9ba2/
 >     http://autobuild.buildroot.net/results/597/597da58cb2fccb92d7883802c60b31264cacad08/
 >     http://autobuild.buildroot.net/results/538/538b23417c68f6c8c0c8c92dfc0e8ed314bac01b/
 >     ...

 > Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
 > Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
 > Cc: Gustavo Zacarias <gustavo@zacarias.com.ar>
 > Cc: Bernd Kuhls <bernd.kuhls@t-online.de>

Committed, thanks.

-- 
Bye, Peter Korsgaard

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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-16 11:04 [Buildroot] [PATCH] package/libcap: needs headers >= 3.0 Yann E. MORIN
2014-11-16 22:11 ` Peter Korsgaard [this message]

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=87tx1ydcea.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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