From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-11-15
Date: Sun, 16 Nov 2014 12:18:59 +0100 [thread overview]
Message-ID: <20141116121859.3e6d8eaf@free-electrons.com> (raw)
In-Reply-To: <20141116105222.GC3965@free.fr>
Dear Yann E. MORIN,
On Sun, 16 Nov 2014 11:52:22 +0100, Yann E. MORIN wrote:
> That's weird:
>
> cap_file.c: In function 'cap_get_fd':
> cap_file.c:190:33: error: 'XATTR_NAME_CAPS' undeclared (first use in this function)
>
> XATTR_NAME_CAPS was introduced in Linux 2.6.24, and the toolchain is
> from CodeSourcery, and uses headers from Linux 2.6.38. So
> XATTR_NAME_CAPS ought to be present. But it is not:
>
> $ grep -r XATTR_NAME_CAPS freescale-2011.03
> [--nothing, zilch, nada, keudale--]
>
> Grr... :-(
>
> So, I would be inclined on making libcap require headers >= 3.0 anyway.
> But that has to be propagated to a few packages:
>
> cdrkit, lxc, ofono, squid (and systemd, but it already requires
> headers >=3.7 anyway)
>
> Thoughts?
We anyway don't have any options today to distinguish between things
added within different versions of the 2.6.x kernels. We have such
options for each individual 3.x kernel, but we handle all 2.6.x kernels
as just one case. Considering this, even though the CodeSourcery
toolchain is indeed broken, I believe depending on >= 3.0 is the right
course of action.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-11-16 11:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-16 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-11-15 Thomas Petazzoni
2014-11-16 10:52 ` Yann E. MORIN
2014-11-16 11:18 ` Thomas Petazzoni [this message]
2014-11-16 21:43 ` Peter Korsgaard
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=20141116121859.3e6d8eaf@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