From: Tom Rini <tom_rini@mentor.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: [PATCH 1/2] micro-uclibc: add xattr to distro features to fix build failure of libcap2
Date: Sat, 26 Feb 2011 15:26:36 -0700 [thread overview]
Message-ID: <4D697E1C.3060708@mentor.com> (raw)
In-Reply-To: <1298748041.3818.10.camel@lenovo.internal.reciva.com>
On 02/26/2011 12:20 PM, Phil Blundell wrote:
> On Sat, 2011-02-26 at 19:59 +0100, Petr Štetiar wrote:
>> Phil Blundell<philb@gnu.org> [2011-02-26 18:39:38]:
>>
>>> On Sat, 2011-02-26 at 18:44 +0100, Petr Štetiar wrote:
>>>> cap_file.c:8:23: fatal error: sys/xattr.h: No such file or directory
>>>
>>> Are you really using POSIX.1e caps on micro? If yes then I guess this
>>> is fine, though it would be interesting to know what the code size
>>> impact is.
>>
>> I don't use micro at all, I've just added it as another test target for
>> 2011.03 release and the build of console-image failed on libcap2 so I've tried
>> to fix it. That's all behind it.
>
> Which package in console-image depends on libcap2? It might be worth
> exploring whether there is a way to avoid that dependency.
avahi brings in libcap2 now. I suppose it's possible to make that xattr
DISTRO_FEATURE spell that part out and update all of the distros. But
maybe that can wait until post release?
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2011-02-26 22:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-26 17:44 [PATCH 1/2] micro-uclibc: add xattr to distro features to fix build failure of libcap2 Petr Štetiar
2011-02-26 17:44 ` [PATCH] minimal-uclibc: " Petr Štetiar
2011-02-26 17:46 ` Petr Štetiar
2011-02-26 17:44 ` [PATCH 2/2] " Petr Štetiar
2011-02-26 18:07 ` Khem Raj
2011-02-26 18:06 ` [PATCH 1/2] micro-uclibc: " Khem Raj
2011-02-26 18:39 ` Petr Štetiar
2011-02-26 18:39 ` Phil Blundell
2011-02-26 18:59 ` Petr Štetiar
2011-02-26 19:20 ` Phil Blundell
2011-02-26 21:48 ` Petr Štetiar
2011-02-26 22:26 ` Tom Rini [this message]
2011-02-28 18:23 ` Phil Blundell
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=4D697E1C.3060708@mentor.com \
--to=tom_rini@mentor.com \
--cc=openembedded-devel@lists.openembedded.org \
/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